Re: [Boost-build] [System] compile error

From: Jurko Gospodnetiæ (jurko.gospodnetic_at_[hidden])
Date: 2008-08-25 16:25:29

   Hi Paul.

> The output from the -d2 flag, as it relates to the System library is:
> 
[...many lines snipped...]
>  
> "-IC:STLPortSTLport-5.1.5stlport"

   Hmm... this line seems fishy... You sure you have not specified some 
path like this using back-slashes in some Jamfile without duplicating 
them and got them interpreted as escape characters instead of path 
separators?

> compile-c-c++ 
> bin.v2\libs\system\build\msvc-WM5\debug\link-static\runtime-link-static\stdlib-stlport\threading-multi\error_code.obj
> 
>     cl /Zm800 -nologo 
> @"bin.v2\libs\system\build\msvc-WM5\debug\link-static\runtime-link-static\stdlib-stlport\threading-multi\error_code.obj.rsp" 
> 
> 
> error_code.cpp
> Unknown EVC++ compiler version - please run the configure tests and 
> report the results
> libs\system\src\error_code.cpp(83) : error C2039: 'strerror' : is not a 
> member of 'stlpd_std'
> libs\system\src\error_code.cpp(83) : error C3861: 'strerror': identifier 
> not found

   The rest of the messages do not seem to be build system related, but 
do seem clear enough.

   The rest of the post, assumes you are a developer and not someone 
just trying to install the library on the system as some other project's 
requirements. If this is not so - the Boost library users list seems 
like your best bet.

   It should not be too difficult for you to look at these sources, see 
what the identifiers mentioned in the error messages are, google for 
them, see what headers need to be included for them, and see what 
headers are actually included by the compiler. That should get you the 
answer to why this is happening soon enough.

   Could be some configuration error, or could be a bug in Boost with it 
not supporting your exact configuration correctly enough. In case of the 
latter you should be able to come up with a patch. Problems with 
includes are generally not difficult to track down. The only thing 
needed to track them down is access to the environment producing the 
error, which is what you have and most likely the person on the other 
side of the mailing list does not so I think your best bet is to try and 
see if you get lucky on the Boost users mailing list but also go and 
track down the source of the problem yourself.

   Hope this helps.

   Best regards,
     Jurko Gospodnetiæ