GNOME Bugzilla – Bug 119343
configure.js and build problem in libxml2-2.5.8
Last modified: 2009-08-15 18:40:50 UTC
Hello all, Any help on this problem would be greatly appreciated. I had a problem using libxml2 w/ xmlNodeDump in 2.5.7, so I thought I would go forward to the new 2.5.8 release, and came up with these 2 problems: 1) In Win32 the cscript configure.js help fails - cscript has a parse failure on line 202, so I comented the lines out as in: /* } else if (compiler == "bcb") { vf.WriteLine("INCLUDE=" + buildInclude); vf.WriteLine("LIB=" + buildLib); } */ because I know my compiler is NOT "bcb" 2) After this the configure runs okay, and when I run nmake and all source code compiles successfully I get: (MY configure script cscript configure.js prefix=c:\libxml2 include=c:\libxml2\include lib=c:\libxml2\lib iconv=no ftp=no http=no html=no catalog=no c14n=no docb=no xml_debug=yes static=yes) DURING LINAKGE: \Generating Code... link.exe /nologo /VERSION:2.5 /LIBPATH:binaries /LIBPATH:c:\libxml2 \lib /OPT:NOWIN98 /DLL /DEF:libxml2.int\libxml2.def /IMPLIB:binaries\libx ml2.lib /OUT:binaries\libxml2.dll libxml2.int\c14n.obj libxml2.int\catalog.obj libxml2.int\debugXML.o libxml2.def : error LNK2001: unresolved external symbol docbCreateFileParserCtxt libxml2.def : error LNK2001: unresolved external symbol docbCreatePushParserCtxt libxml2.def : error LNK2001: unresolved external symbol docbEncodeEntities libxml2.def : error LNK2001: unresolved external symbol docbFreeParserCtxt libxml2.def : error LNK2001: unresolved external symbol docbParseChunk libxml2.def : error LNK2001: unresolved external symbol docbParseDoc libxml2.def : error LNK2001: unresolved external symbol docbParseDocument libxml2.def : error LNK2001: unresolved external symbol docbParseFile libxml2.def : error LNK2001: unresolved external symbol docbSAXParseDoc libxml2.def : error LNK2001: unresolved external symbol docbSAXParseFile libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPAuthHeader libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPCleanup libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPClose libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPFetch libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPInit libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPMethod libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPMethodRedir libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPOpen libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPOpenRedir libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPRead libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPReturnCode libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPSave libxml2.def : error LNK2001: unresolved external symbol xmlNanoHTTPScanProxy binaries\libxml2.lib : fatal error LNK1120: 23 unresolved externals LINK : fatal error LNK1141: failure during build of exports file NMAKE : fatal error U1077: 'link.exe' : return code '0x475' Stop. Thanks in advance for any help. Yours, Rusty
The problem with "configure.js help" was fixed in CVS in early July. For the linker errors, there was a problem with the generation of the libxml2.def.src file. I have corrected that and committed the results to CVS. Please give it a try.
This should be closed by release of libxml2-2.5.9, thanks, Daniel