Pike itself doesn't need libzip, but some libjvm/libjava implementations require that you link with it explicitly. Maybe such implementations can be considered obsolete by now, I haven't checked all recent implementations to see how they behave in this respect.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2004-06-15 01:00: Subject: Re: checking if the JVM really works...
In the last episode (Jun 15), David Gourdelier said:
gcc did; the runtime linker couldn't. They why the compile worked but ./conftest failed. On Solaris, the java libraries have an embedded $ORIGIN in the rpath so they know where their dependencies are. Tru64 puts symlinks to the java libs in /usr/shlib. AIX's java libs don't seem to have dependencies. On FreeBSD and Debian, it looks like there is a java wrapper script that sets LD_LIBRARY_PATH dynamically, depending on which jvm you want to run.
So what would you suggest for this problem ? Setting LD_LIBRARY_PATH manually?
Until I can find some other java-using program that does otherwise as a counterexample, yeah. The mozilla plugin doesn't count since it only links to libjvm.so (pike apparently needs libzip.so also)
-- Dan Nelson dnelson@allantgroup.com
/ Brevbäraren