annoying libtool warnings about moved libraries
raoul
these:
libtool: link: warning:
`/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../..//libgal-2.2.la' seems to
be moved
libtool: link: warning:
`/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../..//libgthread-2.0.la' seems
to be moved
libtool: link: warning:
`/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/../../..//libgal-2.2.la' seems to
be moved
I can't figure out how to let libtool know the correct location of these
libraries (/usr/lib).
A google and google-groups search found other people with the same
problem, but no resolution that I could find.
This person had the same problem and describes it much more precisely than
I can:
http://lists.gnu.org/archive/html/bug-libtool/2004-07/msg00024.html .
I'd appreciate any help. As the guy in the link above said, this isn't a
showstopper, but it's a timewaster and a big annoyance.
jayjwa
Yeah, I got alot of these yesterday building Imagemagick. It happens due to
stuff like symlinks, the biggest culprit on my machine was /usr/X11R6/lib and
it's symlink, /usr/X11/lib.
To libtool, those are two different library paths, and thus it goes thru all
the libs it's working on at the time that reference that directory and gives
the warnings. Probably not a big deal in this case, but stuff like that drives
me insane. /usr/X11/lib had to go.
For your example, have a look in the files it's talking about, for example
libgthread-2.0.la and see what it says inside. Likely something similar to the
above is happening. If I rember correctly, the upgrade of GCC from current to
the testing current didn't update the paths in libtool, and thus libtool kept
looking for directories that didn't exist. Have a look inside it while you are
looking. Read the info file on libtool if you need to, it's pretty helpful.
Personally, I can't stand all that /..//./../../../usr/lib/././lib stuff in
it either, so I fixed it to a more sane absolute path, like /usr/lib,
/usr/local/lib, /usr/X11R6/lib and so on. The recent libtiff upgrade had
something like this: /usr/lib/./libstdc++
If you have mysql handy, it comes with a program 'replace' which is nice for
fixing badly named directories. For example, this is what I did to clean up my
multiple X11 paths:
fgrep usr/X11/lib /usr/lib/*.la (Look for a bad path, if it's referenced)
replace 'usr/X11/lib' 'usr/X11R6/lib' -- /usr/lib/*.la (and fix it)
fgrep usr/X11/lib /usr/local/lib/*.la (do the same here...)
replace 'usr/X11/lib' 'usr/X11R6/lib' -- /usr/local/lib/*.la (again...)
fgrep usr/X11/lib /usr/X11R6/lib/*.la
replace 'usr/X11/lib' 'usr/X11R6/lib' -- /usr/X11R6/lib/*.la
Be sure you understand what the above is doing before you go mass-changing
libtool archives, because you can really mess up your system if you're not
careful. Also, be aware that any packages you download in the future might
still be doing more of the same things you just fixed. Now that I hear that
every Tom, Dick, and Harry will again be putting together packages, get ready
for alot more of it.
Your path trouble involves possibly the gcc lib paths, and glib, maybe some
gtk since it refers to glib (gmodule stuff).
Another big place of inconsistancies is in the *.pc files in /usr/lib/pkgconfig
Check out those paths too, inside the *.pc files. Also the pkgconfig up in
usr/local/lib, if you have that one.
--
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Peter
I believe this is a fault in either the support libraries' config or
evolution's config. I build the whole mess again on a Gentoo and the
"seems to have moved" warnings appear again.
Not a fatal problem, but sure is annoying!