Link error for Intel C++ 11.0 on Windows XP
Chris Hulbert
The error I get is below. wxUSE_STD_IOSTREAMS is on. The link is
successful when built with MS Visual Studio 2003 .NET. Is this an
issue with the Intel compiler, or does MS just seem to support some
extension? If it is an issue with the Intel compiler, is there an easy
way to report it to Intel other than just tell them that I can't build
wxWidgets trunk? In other words, I am not sure what is going wrong so
cannot make a minimal example to demonstrate this. Building without
standard io streams seems to work, so it may not be a big deal.
link /DLL /NOLOGO /OUT:..\..\lib\intel_dll
\wxmsw290_intel_isl_intel.dll /pdb:"..\..\lib\intel_dll
\wxmsw290_intel_isl_intel.pdb" /LIBPATH:..\..\lib\intel_dll @c:\temp
\nm82D.tmp
Creating library ..\..\lib\intel_dll\wxmsw29.lib and object ..\..
\lib\intel_dll\wxmsw29.exp
monodll_string.obj : error LNK2019: unresolved external symbol
"__declspec(dllimport) class std::basic_ostream<char,struct
std::char_traits<char> > & __cdecl std::operator<<(class
std::basic_ostream<char,struct std::char_traits<char> > &,char const
*)" (__imp_??6std@@YAAAV?$basic_ostream@DU?
$char_traits@D@std@@@0@AAV10@PBD@Z) referenced in function "class
std::basic_ostream<char,struct std::char_traits<char> > & __cdecl
operator<<(class std::basic_ostream<char,struct std::char_traits<char>
> &,class wxScopedCharTypeBuffer<char> const &)" (??6@YAAAV?
$basic_ostream@DU?$char_traits@D@std@@@std@@AAV01@ABV?
$wxScopedCharTypeBuffer@D@@@Z)
monodll_variant.obj : error LNK2001: unresolved external symbol
"__declspec(dllimport) class std::basic_ostream<char,struct
std::char_traits<char> > & __cdecl std::operator<<(class
std::basic_ostream<char,struct std::char_traits<char> > &,char const
*)" (__imp_??6std@@YAAAV?$basic_ostream@DU?
$char_traits@D@std@@@0@AAV10@PBD@Z)
..\..\lib\intel_dll\wxmsw290_intel_isl_intel.dll : fatal error
LNK1120: 1 unresolved externals
NMAKE : fatal error U1077: 'link' : return code '0x460'
Stop.
Chris Brulak
Did you build wx with unicode on? I think that may be an issue.
_______________________________________________
wx-users mailing list
wx-u...@lists.wxwidgets.org
http://lists.wxwidgets.org/mailman/listinfo/wx-users
Vadim Zeitlin
CH> I'm trying to build wxWidgets svn trunk with the Intel C++ compiler.
CH> The error I get is below. wxUSE_STD_IOSTREAMS is on. The link is
CH> successful when built with MS Visual Studio 2003 .NET. Is this an
CH> issue with the Intel compiler, or does MS just seem to support some
CH> extension?
It's not really an extension but instantiating templates defined in a DLL
(CRT DLL in this case) is tricky and it appears that icc and cl do it
differently. FWIW I think that using static CRT might solve this problem.
CH> monodll_string.obj : error LNK2019: unresolved external symbol
CH> "__declspec(dllimport) class std::basic_ostream<char,struct
CH> std::char_traits<char> > & __cdecl std::operator<<(class
CH> std::basic_ostream<char,struct std::char_traits<char> > &,char const
CH> *)" (__imp_??6std@@YAAAV?$basic_ostream@DU?
CH> $char_traits@D@std@@@0@AAV10@PBD@Z) referenced in function "class
CH> std::basic_ostream<char,struct std::char_traits<char> > & __cdecl
CH> operator<<(class std::basic_ostream<char,struct std::char_traits<char>
CH> > &,class wxScopedCharTypeBuffer<char> const &)" (??6@YAAAV?
CH> $basic_ostream@DU?$char_traits@D@std@@@std@@AAV01@ABV?
CH> $wxScopedCharTypeBuffer@D@@@Z)
This is strange as the linker points to operator<<(wxScopedCharBuffer)
even though it's not defined anywhere in the first place AFAICS. So another
idea for a solution/workaround would be to define this operator explicitly.
CH> monodll_variant.obj : error LNK2001: unresolved external symbol
CH> "__declspec(dllimport) class std::basic_ostream<char,struct
CH> std::char_traits<char> > & __cdecl std::operator<<(class
CH> std::basic_ostream<char,struct std::char_traits<char> > &,char const
CH> *)"
And this is strange too as operator<<(char const *) should definitely be
defined (otherwise cout << "Hello world!" wouldn't work!). But I have even
less ideas about what's going on here unfortunately.
Regards,
VZ
--
TT-Solutions: wxWidgets consultancy and technical support
http://www.tt-solutions.com/
Chris Hulbert
Apparently, Intel has identified an issue that is also occurring with
their 11.1 compilers. They have submitted it to the engineering
department. Thanks for the help.
Chris
>
> Regards,
> VZ
>
> --
> TT-Solutions: wxWidgets consultancy and technical support
> http://www.tt-solutions.com/
>
> application_pgp-signature_part
> < 1KViewDownload