Re: [Boost-build] odd link problem

From: Marcello Pietrobon (pietrom_at_[hidden])
Date: 2007-07-05 18:47:35

Michael Drumheller wrote:
> I am trying to convert a python-extension-building Jamfile that used
> to work under 1-33-1/V1 to 1-34/V2.  I seem to be getting pretty
> close, but I am running into the link error
> LINK : fatal error LNK1104: cannot open file
> 'libboost_thread-vc80-mt-s-1_33_1.lib'
> which is odd because my Jamfile does not mention 1-33-x anywhere.  The
> link line is below.  I'd be happy to attach the Jamfile itself, but
> thought I'd see first whether the general nature of the error--i.e.,
> the linker is somehow looking for 1-33-1 stuff in an apparently
> all-1-34 setting--rings any bells with anyone, before I send a much
> longer message.
> Thank you very much.
> MD
>
> msvc.link.dll bin\msvc-8.0\debug\Co2api.pyd bin\msvc-8.0\debug\Co2api.lib
>
>         call "c:\Program Files\Microsoft Visual Studio
> 8\VC\vcvarsall.bat" x86 >nul
> link /NOLOGO /INCREMENTAL:NO /DLL /DEBUG /subsystem:console
> /out:"bin\msvc-8.0\debug\Co2api.pyd"
> /IMPLIB:"bin\msvc-8.0\debug\Co2api.lib"
> /LIBPATH:"..\..\..\..\..\BCSLIB"
> /LIBPATH:"..\..\..\..\..\BCSLIB\VF_LIBS\LIB"
> /LIBPATH:"..\..\..\..\..\BCSLIB\spline_toolkit"
> /LIBPATH:"..\..\..\AutoOpt\Dag\Release"
> /LIBPATH:"..\..\..\AutoOpt\Release"
> /LIBPATH:"..\..\..\PythonGILRelease\Release"
> /LIBPATH:"..\..\MSVC\Co2staticlib\Release" /LIBPATH:"C:\Program
> Files\Microsoft Visual Studio 8\VC\PlatformSDK\Lib"
> /LIBPATH:"C:\boost_1_34_0\stage\lib" /LIBPATH:"c:\Python25\libs"
> -FORCE -NODEFAULTLIB:libcmt.lib -NODEFAULTLIB:libc.lib
> @"bin\msvc-8.0\debug\Co2api.pyd.rsp"
>         if %ERRORLEVEL% NEQ 0 EXIT %ERRORLEVEL%
>         if exist "bin\msvc-8.0\debug\Co2api.pyd.manifest" (
>             mt -nologo -manifest
> "bin\msvc-8.0\debug\Co2api.pyd.manifest"
> "-outputresource:bin\msvc-8.0\debug\Co2api.pyd;2"
>         )
>
>
>   
I am writing as I met this kind of error few times.
Another possibile reason I can think of is that you are linking to a 
library that was compiled with 1-33

Sometimes something change and you are convinced to link to a library 
and instead (because of some name changes for example)
you are linking to a different library which is linking to the old library.

Good luck !

Marcello