[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[xml] RE: libxml2-2.5.11 build issue on Win2000



Goutham,

I don't have a copy of 2.5.11 at hand, but I seem to recall that one of the releases around that time had a problem with a couple of missing "#ifdef LIBMXL_HTTP_ENABLED" /"#endif" directive pairs. The various xmlIOHTTP* functions should have been inside LIBXML_HTTP_ENABLED blocks in libxml2.def.src. You could either
try fixing this, or compiling with HTTP support enabled (which should pull in the "missing" functions).

Eric Zurcher
CSIRO Livestock Industries
Canberra, Australia
Eric Zurcher csiro au

> Message: 3
> Date: Tue, 23 Mar 2004 05:03:41 -0800 (PST)
> From: Goutham S Mohan <goutham_s1 yahoo com>
> To: xml gnome org
> Subject: [xml] libxml2-2.5.11 build issue on Win2000
> 
> --0-677061086-1080047021=:27474
> Content-Type: text/plain; charset=us-ascii
> 
> Hi,
>  
> I am trying to build libxml2-2.5.11 on Win 2000. The build 
> errors out with some linker errors for unresolved symbols. It 
> errors out as below when building the libxml2.dll
>  
> link.exe /nologo /VERSION:2.5 /LIBPATH:binaries 
> /LIBPATH:D:/build/gouthams/Itanium/libxml/exports\lib 
> /OPT:NOWIN98 /DLL /DEF:libxml2.int\libxml2.def  
> /IMPLIB:binaries\libxml2.lib /OUT:binaries\libxml2.dll 
> libxml2.int\c14n.obj libxml2.int\catalog.obj 
> libxml2.int\debugXML.obj libxml2.int\DOCBparser.obj 
> libxml2.int\encoding.obj libxml2.int\entities.obj 
> libxml2.int\error.obj libxml2.int\globals.obj 
> libxml2.int\hash.obj libxml2.int\HTMLparser.obj 
> libxml2.int\HTMLtree.obj libxml2.int\list.obj 
> libxml2.int\nanoftp.obj libxml2.int\nanohttp.obj 
> libxml2.int\parser.obj libxml2.int\parserInternals.obj 
> libxml2.int\relaxng.obj libxml2.int\SAX.obj 
> libxml2.int\threads.obj libxml2.int\tree.obj 
> libxml2.int\uri.obj libxml2.int\valid.obj 
> libxml2.int\xinclude.obj libxml2.int\xlink.obj 
> libxml2.int\xmlIO.obj libxml2.int\xmlmemory.obj 
> libxml2.int\xmlreader.obj libxml2.int\xmlregexp.obj 
> libxml2.int\xmlschemas.obj libxml2.int\xmlschemastypes.obj 
> libxml2.int\xmlunicode.obj libxml2.int\xpath.obj 
> libxml2.int\xpointer.obj 
> 
> libxml2.def : error LNK2001: unresolved external symbol xmlIOHTTPClose
> libxml2.def : error LNK2001: unresolved external symbol xmlIOHTTPMatch
> libxml2.def : error LNK2001: unresolved external symbol xmlIOHTTPOpen
> libxml2.def : error LNK2001: unresolved external symbol xmlIOHTTPOpenW
> libxml2.def : error LNK2001: unresolved external symbol xmlIOHTTPRead
> libxml2.def : error LNK2001: unresolved external symbol 
> xmlRegisterHTTPPostCallbacks
> binaries\libxml2.lib : fatal error LNK1120: 6 unresolved externals
>  
>  
> I compared the build logs with the libxml2-2.5.6 build logs 
> and found that there are a few new defines like 
> xmlIOHTTPClose, xmlIOHTTPOpen, xmlIOHTTPRead etc., in 
> <libxml_source>/win32/libxml2.int/libxml2.def file in the new 
> release i.e. libxml2-2.5.11. These are causing the problems. 
>  
> Has anybody come across a similar problem? Or do I need to do 
> anything specific for moving from libxml2-2.5.6 build to 
> libxml2-2.5.11.
>  
> XML processor configuration
> ---------------------------
>      Trio: no
>      Thread safety: native
>      FTP client: no
>      HTTP client: no
>      HTML processor: yes
>      C14N support: yes
>      Catalog support: yes
>      DocBook support: yes
>      XPath support: yes
>      XPointer support: yes
>      XInclude support: yes
>      iconv support: no
>      iso8859x support: no
>      zlib support: no
>      Debugging module: yes
>      Memory debugging: no
>      Regexp support: yes
>      XML Schema support: yes
>      Python bindings: no
>  
> Regards,
> Goutham S Mohan
> 



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]