On Saturday 01 June 2013 19:27:46 Kip Warner wrote: > On Fri, 2013-05-31 at 08:31 -0500, Robert Boehne wrote: > > I don't quite understand why you think you need the rest linked > > statically, > > Libraries like the following may not be present on the end user's system > already: be aware that what ever version of glibc & gcc you use to build, the end user cannot have a version older than that or it'll fail to start > NEEDED libgio-2.0.so.0 > NEEDED libgobject-2.0.so.0 > NEEDED libzzip-0.so.13 > NEEDED libpng12.so.0 you could use -rpath,$ORIGIN and then ship those libs in the same dir (and if people want to use the system copy, they can just rm the bundled ones). this is frequently what games do that ship their own libs (or they have a hacky shell script to set LD_LIBRARY_PATH). i don't want to encourage what it is you're trying to do at all, buuuut the lddtree.py tool might be helpful. on the downside, it'll bundle *all* shared libs your app uses (including glibc ones). on the upside, it should make your package dependent only upon the kernel version (whatever your glibc is compiled to support minimally), the ABIs that your code is compiled for ([colloquially] 32bit/64bit/etc...), and it would automate the whole process (so you don't have to manually copy files around yourself). http://sources.gentoo.org/gentoo-projects/pax-utils/lddtree.py -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
