[wave] linking errors for the head revision
Hartmut, applying your patch from the CVS head (which you produced in request to multi-thread safety and conditional preprocessing) results in linking problems. I tried compiling with boost_1_34_0 and boost_1_34_1_RC2. Here are some of the errors which are produced by the linker. The interesting thing is that threading library is compiled fine. instantiate_cpp_exprgrammar.obj : error LNK2001: unresolved external symbol "public: virtual __thiscall boost::lock_error::~lock_error(void)" (??1lock_error@boost@@UAE@XZ) instantiate_cpp_grammar.obj : error LNK2001: unresolved external symbol "public: virtual __thiscall boost::lock_error::~lock_error(void)" (??1lock_error@boost@@UAE@XZ) instantiate_cpp_literalgrs.obj : error LNK2001: unresolved external symbol "public: virtual __thiscall boost::lock_error::~lock_error(void)" (??1lock_error@boost@@UAE@XZ) instantiate_defined_grammar.obj : error LNK2001: unresolved external symbol "public: virtual __thiscall boost::lock_error::~lock_error(void)" (??1lock_error@boost@@UAE@XZ) With Kind Regards, Ovanes Markarian
Hartmut, I'd like to get back to my problem posted before. Is there any chance that these linking errors were introduced by correcting wave's thread safety? MSVC sometimes can't link to functions which were marked inline, but defined in some cpp file. My output, which looks like a similar problem makes me think that there is such a problem. I attached a build.log file. Please take a look at line 933 et seq. Many thanks, Ovanes.
Ovanes,
I'd like to get back to my problem posted before. Is there any chance that these linking errors were introduced by correcting wave's thread safety? MSVC sometimes can't link to functions which were marked inline, but defined in some cpp file. My output, which looks like a similar problem makes me think that there is such a problem. I attached a build.log file. Please take a look at line 933 et seq.
Sorry for not replying earlier, I'm completely swamped these days... I'll try to have a look at your problem over the weekend, ok? Regards Hartmut
Hartmut, many thanks. This is really great! With Kind Regards, Ovanes Markarian On Fri, July 13, 2007 16:31, Hartmut Kaiser wrote:
Ovanes,
I'd like to get back to my problem posted before. Is there any chance that these linking errors were introduced by correcting wave's thread safety? MSVC sometimes can't link to functions which were marked inline, but defined in some cpp file. My output, which looks like a similar problem makes me think that there is such a problem. I attached a build.log file. Please take a look at line 933 et seq.
Sorry for not replying earlier, I'm completely swamped these days... I'll try to have a look at your problem over the weekend, ok?
Regards Hartmut
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Ahh... Yes... I forgot smth... Just in addition to this problem: it is not possible to build wave only. Building wave in the whole context works fine, but calling the bjam command with parameter --with-wave cause the following error E:\libraries\boost_1_34_1>bjam\bjam.exe --build_dir="../boost_build/temp" --toolset=msvc stage --stagedir="../boost_build/stage" --with-wave error: Unable to find file or target named error: '/boost/filesystem//boost_filesystem' error: referred from project at error: 'libs/wave/build' But boost filesystem was definitely built before without errors and exists. Many thanks again, Ovanes On Fri, July 13, 2007 16:34, Ovanes Markarian wrote:
Hartmut,
many thanks. This is really great!
With Kind Regards,
Ovanes Markarian
participants (2)
-
Hartmut Kaiser -
Ovanes Markarian