which toolset for VC8 on XP64

Hello,
With the precompiled boost libs from boost-consulting I get linker errors
error LNK2019: unresolved external symbol "private: void __cdecl boost::detail::tss::init(class boost::function1

Hi Andreas " An'n Donnerstag 21 Februar 2008 hett Andreas Fabri schreven:
I started a shell such that Microsoft Visual Studio 8/VC/BIN/amd64/CL.EXE is the compiler on the $PATH
This should not be necessary and is superseded by bjam.
I then run bjam --toolset=msvc"
but the problem persists. Is there another toolset I have to choose?
I use those addional options
:: Compile 64-Bit libraries :: --without-python disables 32bit-Python (autodetected). :: ------------------------------------------------------------------
set BJAM_64_BIT=--stagedir=stage64 address-model=64 --without-python
but a simple bjam --toolset=msvc address-model=64 should do the trick. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold@ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

Andreas Fabri wrote:
Hello,
With the precompiled boost libs from boost-consulting I get linker errors
error LNK2019: unresolved external symbol "private: void __cdecl boost::detail::tss::init(class boost::function1
*)" (?init@tss@detail@boost@@AEAAXPEAV?$function1@XPEAXV?$allocator@Vfunction_base@boost@@@std@@@3@@Z) referenced in function "public: __cdecl boost::detail::tss::tss(class boost::function1 *)" (??0tss@detail@boost@@QEAA@PEAV?$function1@XPEAXV?$allocator@Vfunction_base@boost@@@std@@@2@@Z) I started a shell such that Microsoft Visual Studio 8/VC/BIN/amd64/CL.EXE is the compiler on the $PATH
I then run bjam --toolset=msvc"
but the problem persists. Is there another toolset I have to choose?
Try start with opening the standard Visual Studio 2005 command prompt, do whatever you need to do to get to the boost source root and issue: bjam msvc address-model=64 It that doesn't help, try out the boost.build mailing list. HTH / Johan

Thanks a lot for the address-model=64 That solved the problem. Is that explained somewhere on the boost web pages, or did I just not find it? andreas Johan Nilsson wrote:
Andreas Fabri wrote:
Hello,
With the precompiled boost libs from boost-consulting I get linker errors
error LNK2019: unresolved external symbol "private: void __cdecl boost::detail::tss::init(class boost::function1
*)" (?init@tss@detail@boost@@AEAAXPEAV?$function1@XPEAXV?$allocator@Vfunction_base@boost@@@std@@@3@@Z) referenced in function "public: __cdecl boost::detail::tss::tss(class boost::function1 *)" (??0tss@detail@boost@@QEAA@PEAV?$function1@XPEAXV?$allocator@Vfunction_base@boost@@@std@@@2@@Z) I started a shell such that Microsoft Visual Studio 8/VC/BIN/amd64/CL.EXE is the compiler on the $PATH
I then run bjam --toolset=msvc"
but the problem persists. Is there another toolset I have to choose?
Try start with opening the standard Visual Studio 2005 command prompt, do whatever you need to do to get to the boost source root and issue:
bjam msvc address-model=64
It that doesn't help, try out the boost.build mailing list.
HTH / Johan
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

Andreas Fabri wrote:
Thanks a lot for the address-model=64 That solved the problem.
Is that explained somewhere on the boost web pages, or did I just not find it?
This is documented on boost.org/boost-build2 It's even in the keyword index: http://boost.org/boost-build2/doc/html/ix01.html - Volodya
participants (4)
-
Andreas Fabri
-
Johan Nilsson
-
Jürgen Hunold
-
Vladimir Prus