| Re: [cdt-dev] External build tool: Cannot run program "bjam": Unknown reason |
|
Have you tried attaching strace to Eclipse to see what actual system calls are being made and if there are any error messages at that level? strace has pretty
nice filtering features to capture just certain subsets of system calls. (I've never seen the problem either, so I'm shooting in the dark here. :) /Jesper From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Steve Lorimer Hi Jesper Thanks for the input. I'm doubtful that's the case, for 2 reasons. 1. I'm on Linux and am not running a virus scanner 2. I never have this problem running from a terminal, only from Eclipse Thanks Steve On 28 March 2016 at 12:46, Jesper Eskilson <Jesper.Eskilson@xxxxxxx> wrote: This sound suspiciously like a anti-virus scanner holding locks it really shouldn't.
I normally have background-scanning turned off for local drives used for compiling things on, mostly
for performance reasons. /Jesper From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Steve Lorimer I use the boost build build system (http://www.boost.org/build/) As such, I have configured C++ Build / Builder settings to use a custom command. Typically everything works, however, occasionally when I try to build I get back an error "Cannot run program "bjam": Unknown reason"
bjam is a tool on a local disk, is in my path, my source is on a local disk etc. Running bjam from a terminal works fine. If I wait for some time (several minutes), it seems to "find" bjam again, so it will suddenly start working again. However, if I don't want to wait for several minutes for eclipse to sort itself out again, I have to restart eclipse to get it to work again. How can I diagnose what is causing eclipse to lose access to bjam, and how can I prevent this from happening? TIA Steve
|