> ----- Original Message ----- > From: "Joe Orton" <[EMAIL PROTECTED]> > To: [email protected] > Subject: Re: Eliminating absolute paths on installation > Date: Wed, 13 Dec 2006 14:33:03 +0000 > > > On Wed, Dec 13, 2006 at 01:16:35PM +0100, Paul Fee wrote: > > The RPATH is slightly different. > > The only way to avoid the RPATH (in general) is to link APR/APR-util > statically; which can only be achieved by not building the shared > libraries. So passing --disable-shared to configure may work, though > this is not a configuration that gets any testing at all AFAIK, so it > may not work but bug reports are welcome. > > Having libtool use $ORIGIN-relative RPATHs would certainly be a neat > hack for platforms which support that; patches would have to go to the > libtool team ;) > > Alternatively, you can get tools which munge ELF binaries post-build - > "chrpath" is the commonly used one IIRC. > > Regards, > > joe
Hi Joe, A problem avoided is a problem solved! My build of httpd has a small number of (non OS supplied) dependencies: libaprutil libexpat libapr Hence rolling these statically into the one httpd executable sounds feasible. I don't have other apps linking the same APR shared objects, hence I won't be losing opportunities to share .so files in memory. Editing an existing RPATH with chrpath sounds interesting, but dangerous. I won't be surprised if had a limitation such as the replacement RPATH can not exceed the original RPATH, but I could cope with that. Also, delving into the subtleties of libtool sounds a bit intimidating. Anyway, you and Jeff have provided useful pointers. Thanks, Paul -- _______________________________________________ Surf the Web in a faster, safer and easier way: Download Opera 9 at http://www.opera.com Powered by Outblaze
