Simon Morlat <[EMAIL PROTECTED]> writes: > Le Thursday 13 December 2007 00:06:13 Francois-Xavier KOWALSKI, writes: >> Why wouldn't the below work? >> >> ./configure --enable-static --disable-shared > It would work if you do it for all dependencies: > libosip, libeXosip, ffmpeg, SDL, readline, gtk, glib, pango, xlib... It's > difficult to have a pure static executable running with just libc as shared > lib dependency.
AFAIR passing one of -all-static, -static, -static-libtool-libs to LDFLAGS should help. maybe: ./configure --disable-shared --enable-static LDFLAGS="-static" Anyway you might end up using the the libtool output for calling the linker as base and then fine tune it ;-) (see compiler and linker man pages, search for -Wl, static, ...) Generally link as much as possible dynamically and use some older system to compile the "semi-static" binary. Talking about Linux systems, you might also wish to take a look at the lsb effort. (On Debian based systems maybe the lsb-build-* packages) Instead of linking statically you may also ship the shared libraries and use a wrapper to run the binary with a modified LD_LIBRARY_PATH. But then again you get very close to questionable practice common on some other systems ;-) Greetings Jens PS: generally this all is quite time consuming and you also have to keep in mind that there are many architectures => its not feasible for smaller projects to provide binaries for all architectures => providing binaries is the job of distributions after all ;-) PPS: you can also use your distributions tools to backport newer versions (f.e. linphone 2.0.1-3 is already in debian/unstable) s.a. http://wiki.debian.org/Backports http://doc.cliss21.com/index.php?title=Backports https://help.ubuntu.com/community/UbuntuBackports _______________________________________________ Linphone-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/linphone-users
