From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2008-04-17 14:02:26
Finally I was able to reproduce Mat's findings and also
found the solution to this problem.
It was just by chance that compiling the thread lib triggered
the problem. Other libs might also be affected, but this depends
on whether they care if it is important to link against
cygwindll or msvc rt.
Since gcc.jam has no means to choose which dll to link against
(not sure if this should or could be handled by <std-lib> feature),
user intervention is necessary.
This can be done by specifying
by having the init rule of gcc add these flags when the host os
is windows _and_ gcc is not mingw but cygwin-gcc that tries to
compile mingw executables.
Mat, so I recommend to put the both options into your user-config.jam.
I still do not recommend to use msvc compiled bjam from bash.
This is mainly because the default setting of the target-os is not
correct, but also because bjam will not try to locate user-config.jam
from your cygwin home directory.
While it _might_ be possible to share the home directory between
windows and cygwin, you are likely to ask for trouble. If you have
found a robust way of doing so, please let me know! I did not
succed since I am using cygwin.
-- _________________________________________ _ _ | Roland Schwarz |_)(_ | aka. speedsnail | \__) | mailto:roland.schwarz_at_[hidden] ________| http://www.blackspace.at
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk