[repost][filesystem][system] Linking errors with C++0X options on intel C++ 11.0
Sorry to repost, but I am at a loss and was hoping I have missed something. I am on Intel C++ 11.0 on windows. I built boost::filesystem and boost::system as static libraries with the following line in my userconfig.jam using intel-win : 11.0 : : <cxxflags>/Qstd:c++0x ; I am then compiling a project (that works with non-C++0x just fine) with /Qstd:c++0x in the command line. But when I try to link it with my calls to boost::filesystem header functions, I get the following link errors (it must be using auto linking) 1>etk_template.obj : error LNK2019: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::get_system_category(void)" (?get_system_category@system@boost@@YAABVerror_category@12@XZ) referenced in function _main 1>etk_template2.obj : error LNK2001: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::get_system_category(void)" (?get_system_category@system@boost@@YAABVerror_category@12@XZ) 1>etk_template.obj : error LNK2019: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::get_generic_category(void)" (?get_generic_category@system@boost@@YAABVerror_category@12@XZ) referenced in function _main 1>etk_template2.obj : error LNK2001: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system::get_generic_category(void)" (?get_generic_category@system@boost@@YAABVerror_category@12@XZ) I am not changing any pre-compiler definitions for boost when I use /Qstd:c++0x. Should I be changing anything there? Am I out of luck? -Jesse
I am then compiling a project (that works with non-C++0x just fine) with /Qstd:c++0x in the command line. But when I try to link it with my calls to boost::filesystem header functions, I get the following link errors (it must be using auto linking)
1>etk_template.obj : error LNK2019: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system:: get_system_category(void)" (? get_system_category@system@boost@@YAABVerror_category@12@XZ) referenced in function _main 1>etk_template2.obj : error LNK2001: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system:: get_system_category(void)" (? get_system_category@system@boost@@YAABVerror_category@12@XZ) 1>etk_template.obj : error LNK2019: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system:: get_generic_category(void)" (? get_generic_category@system@boost@@YAABVerror_category@12@XZ) referenced in function _main 1>etk_template2.obj : error LNK2001: unresolved external symbol "class boost::system::error_category const & __cdecl boost::system:: get_generic_category(void)" (? get_generic_category@system@boost@@YAABVerror_category@12@XZ)
It seems your "auto linking" option is not linking with the boost_system library. Try to add it manually. F. Bron Avis : Ce message et toute pièce jointe sont la propriété d'Alcan et sont destinés seulement aux personnes ou à l'entité à qui le message est adressé. Si vous avez reçu ce message par erreur, veuillez le détruire et en aviser l'expéditeur par courriel. Si vous n'êtes pas le destinataire du message, vous n'êtes pas autorisé à utiliser, à copier ou à divulguer le contenu du message ou ses pièces jointes en tout ou en partie. Notice: This message and any attachments are the property of Alcan and are intended solely for the named recipients or entity to whom this message is addressed. If you have received this message in error please inform the sender via e-mail and destroy the message. If you are not the intended recipient you are not allowed to use, copy or disclose the contents or attachments in whole or in part.
On Thu, Apr 2, 2009 at 12:37 AM, <frederic.bron@alcan.com> wrote:
It seems your "auto linking" option is not linking with the boost_system library. Try to add it manually. F. Bron
Thanks for the response. Sadly, I had tried that and no luck. The problem seems to be the difference in standard libraries providing these functions, which isn't surprising since the transition to C++0X standard errors seems to be a key goal of boost::system. I tracked down the usage of these two functions to error_code.hpp. I modifed error_code to remove the calls to those functions and things worked for some cases, but other operations in boost::filesystem require these functions as well. I was able to get a lot of stuff to work. However: boost::test, boost::filesystem, boost::mpi all seem incompatible with C++0X builds in intel. So I am forced to go live without "auto" for now. Is using boost with /Qstd:c++0x on the horizon anytime soon? It sure would make life easier for generic programmers. -Jesse
On Thu, Apr 2, 2009 at 12:37 AM, <frederic.bron@alcan.com> wrote:
It seems your "auto linking" option is not linking with the boost_system library. Try to add it manually. F. Bron
Thanks for the response. Sadly, I had tried that and no luck. The problem seems to be the difference in standard libraries providing these functions, which isn't surprising since the transition to C+ +0X standard errors seems to be a key goal of boost::system.
I tracked down the usage of these two functions to error_code.hpp. I modifed error_code to remove the calls to those functions and things worked for some cases, but other operations in boost::filesystem require these functions as well. I was able to get a lot of stuff to work. However: boost::test, boost::filesystem, boost::mpi all seem incompatible with C++0X builds in intel. So I am forced to go live without "auto" for now.
Is using boost with /Qstd:c++0x on the horizon anytime soon? It sure would make life easier for generic programmers.
-Jesse _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users Hello, I have the same problem on a PowerPC. The work around was to add - lboost_system to the library path. Frank J. R. Hanstick
On Apr 2, 2009, at 4:13 PM, Jesse Perla wrote: trog24@comcast.net
participants (4)
-
Frank J. R. Hanstick -
frederic.bron＠alcan.com -
Jesse Perla -
jesseperla＠gmail.com