Le lundi 12 juin 2006 à 18:37 +0200, Øystein Gisnås a écrit : > The symptoms can be seen when building something that depends on > evolution, for example evolution-exchange. Compile and linking succeed, > but the binaries that linked > against /usr/lib/evolution/2.6/libeutil.so.0.0.0 > and /usr/lib/evolution/2.6/libevolution-addressbook-a11y.so.0.0.0 cannot > resolve those libraries, because RPATH is missing (can be seen with > objdump -p evolution-exchange-storage). > > I have two questions. First, is it OK that another package links against > a library that is not in /usr/lib?
I don't think it's a good idea, no. > Second, if the location of the libs > is OK, how can I make libtool put RPATH into evolution-exchange-storage > and other binaries linked against the two troublesome libraries? Is it a > bug in libtool, or must one set a flag to force RPATH in Makefile.am or > something? Another option is to put the libraries in /usr/lib and to use libtool's -release flag, so that they are called libeutil-2.6.so.0.0.0 and so on. Then, it makes sense to put them in a separate library package (like libevolution-2.6-0). -- .''`. Josselin Mouette /\./\ : :' : [EMAIL PROTECTED] `. `' [EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
