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: Fri, 24 Sep 2010 06:30:36 +0000 (GMT)

--- Ven 24/9/10, Charles Wilson  ha scritto:

> On 9/24/2010 12:45 AM, Marco Atzeri
> wrote:
> > I am not sure to follow your explanation.
> > 
> > on cygwin
> > 
> > $cd /usr/lib
> 
> I'm cross building, using $build_os=cygwin, but
> $host_os=mingw32, and a
> cross compiler.  I am *not* building natively.
> 
> In this situation, and with the new "sysroot" support in
> libtool, .la
> files will have a magic marker like this: -L=/some/path,
> or
> libdir='=/some/path'.
> 
> The extra '=' symbol is interpreted by (new) libtool, WHEN
> it too is
> told that "sysroots" are active, to mean:
> 
> pretend /some/path is prefixed by whatever the "sysroot" of
> the current
> compiler is; e.g. 'i686-pc-mingw32-gcc -print-sysroot'
> might report:
> /usr/i686-pc-mingw32/sys-root
> 
> So, if the .la file in
> /usr/i686-pc-mingw32/sys-root/mingw/lib/foo.la
> claims that its libdir should be "=/mingw/lib", libtool
> will magically
> prepend the compiler's sysroot, and interpret the libdir
> specification
> AS IF it said
>    libdir='/usr/i686-pc-mingw32/sys-root/mingw/lib'
> and not
>    libdir='=/mingw/lib'
> Since that IS where the .la file is located, all is well
> and no warning
> is printed.  However, WITHOUT sysroot support in
> libtool (or if the .la
> file doesn't have the magic '=' marker) none of this
> occurs, and libtool
> will print the warning.
> 
> But...that's what it is supposed to do in this case.
> 
> Now, I'm talking ONLY about a cross build situation.
> 
> See (latest 2.4 libtool) info.  There's a whole
> section about it.
> 
> --
> Chuck

thanks for the explanation.
I am not cross building, my case is a pure cygwin on cygwin

with
$ libtool --version
libtool (GNU libtool 1.3260 2010-09-02) 2.2.11a

and 
$ gcc --version
gcc (GCC) 4.3.4 20090804 (release) 1


Marco







reply via email to

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