Angus- I had similar problems with bjam under MinGW. By experimentation, I discovered that I could make bjam work under MinGW by moving it from it's previous location at 'c:/msys/1.0/bin' to 'c:/msys/1.0/mingw/bin'. FYI, you can find this thread starting at Boost-users Digest, Vol 250, Issue 1, and ending (successully :) at Boost-users Digest, Vol 253, Issue 1. HTH, Chris Brewer
Brewer, Christopher wrote:
Angus-
I had similar problems with bjam under MinGW. By experimentation, I discovered that I could make bjam work under MinGW by moving it from it's previous location at 'c:/msys/1.0/bin' to 'c:/msys/1.0/mingw/bin'.
It does indeed. Many, many thanks, Chris.
FYI, you can find this thread starting at Boost-users Digest, Vol 250, Issue 1, and ending (successully :) at Boost-users Digest, Vol 253, Issue 1.
Mea culpa. I now see you posted the solution on 16 Jun. Regards, Angus
Brewer, Christopher:
I had similar problems with bjam under MinGW. By experimentation, I discovered that I could make bjam work under MinGW by moving it from it's previous location at 'c:/msys/1.0/bin' to 'c:/msys/1.0/mingw/bin'.
FYI, you can find this thread starting at Boost-users Digest, Vol 250, Issue 1, and ending (successully :) at Boost-users Digest, Vol 253, Issue 1.
Maybe that didn't work because "Msys will convert POSIX paths that are used as arguments to Win32 paths. This is done for any executable not in /bin and /usr/bin." [MSYS readme] -- Daniel Schlyder http://bitblaze.com/
participants (3)
-
Angus Leeming -
Brewer, Christopher -
Daniel Schlyder