Hi, Trying to build a 64-bit dynamic libxml2-2.7.7 and, during the make stage, I keep getting hammered by:
############################################ *** Warning: linker path does not have real file for library -lz. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have *** because I did check the linker path looking for a file starting *** with libz and none of the candidates passed a file format test *** using a file magic. Last file checked: /usr/local_dyn/lib/libz.dll.a *** Warning: linker path does not have real file for library -lws2_32. *** I have the capability to make that library automatically link in when *** you link to this library. But I can only do this if you have a *** shared version of the library, which you do not appear to have *** because I did check the linker path looking for a file starting *** with libws2_32 and none of the candidates passed a file format test *** using a file magic. Last file checked: /c/Windows/system32/libws2_32.dll *** The inter-library dependencies that have been dropped here will be *** automatically added whenever a program is linked with this library *** or is declared to -dlopen it. *** Since this library must not contain undefined symbols, *** because either the platform does not support them or *** it was explicitly requested with -no-undefined, *** libtool will only create a static version of it. libtool: link: ar cru ........... ############################################ I can build a 32-bit dynamic libxml2-2.7.7 library - same source, same shell, just different compiler. As the 32-bit build needs to find a 32-bit libz, and the 64-bit build needs to find a 64-bit libz, the configure args (namely LDFLAGS and CPPFLAGS) are a little different, and if I use the cross-compiler then I have to provide args for CC etc. /usr/local_dyn/lib/libz.dll.a (referred to in the above excerpt from the 'make' process) is, of course, the 64-bit import lib for the 64-bit zlib dll. As regards the system library (ws2_32) I'm sure that I once got around a similar problem with gdi32.dll by creating a copy of it called libgdi32.dll .... but I can't get the same "fix" to work re ws2_32.dll. Just to re-iterate - if the compiler is 32-bit (be it from mingw.org or from the mingw64 team) there's no problem, but if the compiler is 64-bit (be it one of sezero's builds or the cross-compiler) then there's seemingly no way I can build a dynamic libxml2 library in the msys shell. Does anyone here have a clear understanding of what this arcane procedure is doing, and of how to get it to realize that the dynamic libs are all there ? I did look at instead using the win32/Makefile.mingw that ships with the libxml2 sources, but it contains (in part): #################################### # There should never be a need to modify anything below this line. # ---------------------------------------------------------------- AUTOCONF = .\config.mingw include $(AUTOCONF) #################################### and, of course, config.mingw doesn't even exist afaict. (Maybe I should explore this avenue further instead of trying to get configure to do the job properly.) Cheers, Rob ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
