Hi, > I would prefer to fix the -enable-static, but I don't know anything to > autoconf... > > For now I will just change the src/Makefile.am to work with my paths > in order to have a working binary...
Ok, please don't commit this. This hack is ugly enough now, I would prefer not having ping/pong between two incompatibles ugly hacks. > End, wait just a question the existing -enable-static link to libz.a > but libz isn't under the GPL, so I think that's not allowed. Am I right > ? But a shared library of libz is installed on Mac OS X so I wouldn't > need to statically link it. Well if only I manage to change all this > Makefile thing to statically link against all but not on zlib... I think that if zlib is GPL compatible, that's ok. I don't know wether it is or not. If I'm correct (90% confidence), it is easy to mix static/dynamic libs: If you don't specify -static to ld, then you have dynamic libc and any lib you do not specify by adding a .a to the object list. If you do specify -static to ld, then it will try to link everything in static, and fail otherwise. Steph _______________________________________________ glob2-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/glob2-devel
