This is OT now for this list, but I'll another thing about the rpath issue. The way it (libtool) changes the development cycle is not so terrible, you just have to deal, but it can bite you sometimes and is certainly something else. More importantly, little thought seems to have gone into packaging. Packages should generally be install-time relocatable (certainly that is what I aim for when building Solaris packages), but how can one do this with libtool? The answer to that is complicated right now. Nico On Wed, May 30, 2001 at 01:20:50PM +0200, Ingo Luetkebohle wrote: > Another problem with libtool, related to the above, is the handling of > RPATH (needed when libraries are installed in non-standard > places). Current versions of libtool incorrectly propagate the -R or > -rpath options of ld into the RPATH ELF header, resulting in a library > that -- while it has the correct NEEDED entries to refer to other > libraries -- can't find them at runtime. > > Since Linux-PAM's modules directory typically is not the in the > system-wide search path of the dynamic linker, this might affect us, > too. > > -- > Ingo Luetkebohle / ingo@blank.pages.de / 95428014 > / > | Student of Computational Linguistics & Computer Science; > | Fargonauten.DE sysadmin; Gimp Registry maintainer; > | FP: 3187 4DEC 47E6 1B1E 6F4F 57D4 CD90 C164 34AD CE5B --
