| View previous topic :: View next topic |
| Author |
Message |
dcljr
Tux's lil' helper
Joined: 20 Aug 2005
Posts: 92
Location: Austin, TX
|
 Posted: Thu Jun 15, 2006 10:13 am Post subject: why "libtool: link: warning: ... seems to be moved" |
 |
|
I swear I read something in these forums about this (or a problem very much like it) once, but I can't find it again.
First some background: I just upgraded to gcc-3.4.6 from gcc-3.3.6, following the revdep-rebuild option (trying to avoid emerge -e system and emerge -e world if at all possible), and had some issues (like gedit failing on startup) that required me to redo some of the steps and follow some other suggestions I found elsewhere in the forums.
Everything seems to be working now, but the last time I (re)emerged nautilus I noticed the following (non-fatal) warnings:
| Code: | libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libgtk-x11-2.0.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libgdk-x11-2.0.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libatk-1.0.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libgdk_pixbuf-2.0.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libpangocairo-1.0.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libpango-1.0.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libcairo.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libgnomevfs-2.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libbonobo-2.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libgconf-2.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libgobject-2.0.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libbonobo-activation.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libORBit-2.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libgmodule-2.0.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libgthread-2.0.la' seems to be moved
libtool: link: warning: `/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/../../..//libglib-2.0.la' seems to be moved |
Is this something I should worry about? Should I re-emerge the indicated packages? I've already used fix_libtool_files.sh and emerged libstdc++-v3, as recommended.
Note that the emerge didn't fail, but I don't believe that means everything is hunky-dory. Can someone explain to me (or point me to an explanation of) what's going on when you see those warnings?
- dcljr |
|
| Back to top |
|
 |
!equilibrium
Bodhisattva
Joined: 06 Jun 2004
Posts: 2109
Location: MI/BG/LC
|
| Posted: Thu Jun 15, 2006 1:16 pm Post subject: Re: why "libtool: link: warning: ... seems to be moved& |
|
|
| dcljr wrote: | | Note that the emerge didn't fail, but I don't believe that means everything is hunky-dory. Can someone explain to me (or point me to an explanation of) what's going on when you see those warnings? |
you can safely ignore it 
_________________
Arch Tester for Gentoo/FreeBSD
Equilibrium's Universe
all my contents are released under the Creative Commons Licence by-nc-nd 2.5 |
|
| Back to top |
|
|
dcljr
Tux's lil' helper
Joined: 20 Aug 2005
Posts: 92
Location: Austin, TX
|
| Posted: Thu Jul 13, 2006 11:28 pm Post subject: |
|
|
| Quote: | | you can safely ignore it |
Well, that's reassuring, I guess, but I've noticed more and more of these libtoool: warnings as I've been going though the logs of ebuilds since my post above. In fact, when evolution last got emerged, it generated a whopping 2,400 such warnings. And, as I was monitoring the process "live", I noticed that each batch of 20-30 warnings seemed to add a few seconds to the build process. That can add up to several minutes of (I assume) wasted time during an emerge -uDvp world. Even if it's harmless, is there something I can do to prevent it (i.e., fix the problem, not just hide the warnings)?
- dcljr |
|
| Back to top |
|
|
dcljr
Tux's lil' helper
Joined: 20 Aug 2005
Posts: 92
Location: Austin, TX
|
| Posted: Fri Jul 14, 2006 5:46 am Post subject: |
|
|
Let's see if I can answer my own question: Is ldconfig what I'm looking for??
- dcljr |
|
| Back to top |
|
|
!equilibrium
Bodhisattva
Joined: 06 Jun 2004
Posts: 2109
Location: MI/BG/LC
|
| Posted: Fri Jul 14, 2006 9:55 am Post subject: |
|
|
| dcljr wrote: | | Even if it's harmless, is there something I can do to prevent it (i.e., fix the problem, not just hide the warnings)? |
the warning are produced by the gcc, so if you want to fix them, you need to fix the source code:
- found the point where the code produce the warning
- try to understand what is the cause that produce the warning
- fix the code
- do a patch
- collect all the patches and send them to bugs.gentoo.org so the gentoo devels can apply them to the ebuilds and upstream.
_________________
Arch Tester for Gentoo/FreeBSD
Equilibrium's Universe
all my contents are released under the Creative Commons Licence by-nc-nd 2.5 |
|
| Back to top |
|
|
Sbriglie
n00b
Joined: 17 Jun 2004
Posts: 58
|
| Posted: Fri Jul 14, 2006 8:32 pm Post subject: |
|
|
| !equilibrium wrote: | | dcljr wrote: | | Even if it's harmless, is there something I can do to prevent it (i.e., fix the problem, not just hide the warnings)? |
the warning are produced by the gcc, so if you want to fix them, you need to fix the source code:
- found the point where the code produce the warning
- try to understand what is the cause that produce the warning
- fix the code
- do a patch
- collect all the patches and send them to bugs.gentoo.org so the gentoo devels can apply them to the ebuilds and upstream. |
It's not a matter of source code, but of libraries that have effectively changed location, so libtool is right. I looked around and there does not seem to be a solution to this annoying slowdown in compilations |
|
| Back to top |
|
|
!equilibrium
Bodhisattva
Joined: 06 Jun 2004
Posts: 2109
Location: MI/BG/LC
|
| Posted: Sat Jul 15, 2006 12:36 pm Post subject: |
|
|
| Sbriglie wrote: | | It's not a matter of source code, but of libraries that have effectively changed location, so libtool is right. I looked around and there does not seem to be a solution to this annoying slowdown in compilations |
i was not talking about the source code of the software that generate the warnings during compilation time, but about the libtool source code, find the bug into libtool and fix it
apparently the problem seem that the link is correct, but libtool is not able to understand path with '//' (double slashes); in other circustances the path is properly wrong, and the libdb must be updated, but for this situation there is not a real solution.
_________________
Arch Tester for Gentoo/FreeBSD
Equilibrium's Universe
all my contents are released under the Creative Commons Licence by-nc-nd 2.5 |
|
| Back to top |
|
|
Sbriglie
n00b
Joined: 17 Jun 2004
Posts: 58
|
| Posted: Sat Jul 15, 2006 1:42 pm Post subject: |
|
|
| !equilibrium wrote: | | Sbriglie wrote: | | It's not a matter of source code, but of libraries that have effectively changed location, so libtool is right. I looked around and there does not seem to be a solution to this annoying slowdown in compilations |
i was not talking about the source code of the software that generate the warnings during compilation time, but about the libtool source code, find the bug into libtool and fix it
apparently the problem seem that the link is correct, but libtool is not able to understand path with '//' (double slashes); in other circustances the path is properly wrong, and the libdb must be updated, but for this situation there is not a real solution. |
Ok, now I understand what you were saying. Certainly it's not easy to dig into libtool/gcc source code, anyway  |
|
| Back to top |
|
|
dcljr
Tux's lil' helper
Joined: 20 Aug 2005
Posts: 92
Location: Austin, TX
|
| Posted: Sun Jul 16, 2006 9:43 pm Post subject: |
|
|
Oh, so then it's not something I need to change about my system. The warning makes it sound like my system is to blame...
- dcljr |
|
| Back to top |
|
|
episodeiv
n00b
Joined: 19 Oct 2006
Posts: 2
|
| Posted: Thu Oct 19, 2006 12:43 pm Post subject: |
|
|
This seems to be a case of false positives. I found this when looking into this as I had the same problems, especially with evolution.
The patch has obviously not gone into Gentoo's libtool yet so let's just wait and hope  )
Dennis |
|
| Back to top |
|
|
tedj
n00b
Joined: 10 Jul 2003
Posts: 49
|
| Posted: Wed Nov 08, 2006 9:59 pm Post subject: |
|
|
The only place I see that error is in the shell script, ltmain.
| Code: | gentoo-laptop libtool-1.5.22 # find . -print | xargs grep "seems to be moved"
./ltmain.in: $echo "$modename: warning: \`$deplib' seems to be moved" 1>&2
./ltmain.sh: $echo "$modename: warning: \`$deplib' seems to be moved" 1>&2
./libltdl/ltmain.sh: $echo "$modename: warning: \`$deplib' seems to be moved" 1>&2
|
Small section of code around that area...
| Code: | for deplib in $dependency_libs; do
case $deplib in
-L*) path="$deplib" ;;
*.la)
dir=`$echo "X$deplib" | $Xsed -e 's%/[^/]*$%%'`
test "X$dir" = "X$deplib" && dir="."
# We need an absolute path.
case $dir in
[\\/]* | [A-Za-z]:[\\/]*) absdir="$dir" ;;
*)
absdir=`cd "$dir" && pwd`
if test -z "$absdir"; then
$echo "$modename: warning: cannot determine absolute directory name of \`$dir'" 1>&2
absdir="$dir"
fi
;;
esac
if grep "^installed=no" $deplib > /dev/null; then
path="$absdir/$objdir"
else
eval libdir=`${SED} -n -e 's/^libdir=\(.*\)$/\1/p' $deplib`
if test -z "$libdir"; then
$echo "$modename: \`$deplib' is not a valid libtool archive" 1>&2
exit $EXIT_FAILURE
fi
if test "$absdir" != "$libdir"; then
$echo "$modename: warning: \`$deplib' seems to be moved" 1>&2
fi
path="$absdir"
fi |
Seems that a quick fix for removing double slashies from $deplib might work.
I've not looked too deep at this yet. |
|
| Back to top |
|
|
crazy-bee
Apprentice
Joined: 03 Jan 2003
Posts: 170
|
| Posted: Sun Nov 12, 2006 1:21 pm Post subject: |
|
|
| I would love to see that problem fixed, if it is just a libtool problem, it shouldnt be that hard. I am seeing this messages for ages, and I see them alot, and they definitly slow down the building of packages. |
|
| Back to top |
|
|
|
Portage & Programming
