libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bogus warning 'seems to be moved'


From: Marco Atzeri
Subject: Re: bogus warning 'seems to be moved'
Date: Thu, 23 Sep 2010 22:25:18 +0000 (GMT)

--- Gio 23/9/10, Dave Korn ha scritto:

> On 22/09/2010 09:49, Marco Atzeri
> wrote:
> 
> > Dear developers,
> > is this bogus warning avoidable in the next release ?
>
> > libtool: link: warning:
> >
> `/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../libfontconfig.la'
> > seems to be moved
> > libtool: link: warning:
> >
> `/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../libexpat.la'
> > seems to be moved
> > ...
>
> > as the files are
>
> > /usr/lib/libfontconfig.la
> > /usr/lib/libexpat.la
> > ..
> > 
> > the *.la files did not moved at all
> 
>   I see this warning re: libintl when I build libgcj.
> 
>   In that case, it happens because for some reason (I
> haven't established yet
> whether this is down to libtool or the libgcj makefile)
> something goes wrong
> with directory search paths, and /lib appears in the list
> ahead of /usr/lib.
> 
>   As a consequence, libtool finds the .la file via
> Cygwin's /lib mountpoint
> rather than the real /usr/lib path, all the relative paths
> are wrong and it
> looks like the control script has been moved.  This
> shows up in the warning it
> issues:
> 
> > libtool: link: warning: `/lib/libiconv.la' seems to be
> moved
> 
>   I wonder if your problem has a similar cause
> underlying in some way?
> 
>     cheers,
>       DaveK
> 

from what I can see the bogus warning is caused by 

test "$absdir" != "$libdir" && \
func_warning "\`$deplib' seems to be moved"

changing the warning in

test "$absdir" != "$libdir" && \
func_warning "\`$absdir' \`$libdir' \`$deplib' seems to be moved"

I found:
libtool: link: warning: `/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../..' `/usr/lib' 
 `/usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../libfftw3.la' seems to be moved

so it seems that absdir is not a real absolute directory.

and this case block seems the culprit

# We need an absolute path.
case $dir in
[\\/]* | [A-Za-z]:[\\/]*) absdir="$dir" ;;
*)
    absdir=`cd "$dir" && pwd`
    if test -z "$absdir"; then
       func_warning "cannot determine absolute directory name of \`$dir'"
       absdir="$dir"
    fi
    ;;
esac



This assignement would be correct, but it is not applied
absdir=`cd "$dir" && pwd`


Marco










reply via email to

[Prev in Thread] Current Thread [Next in Thread]