GNU bug report logs - #9631
path in .la start with '='

Previous Next

To reply to this bug, email your comments to 9631 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Peter Kruse <pjodrr <at> gmail.com>
To: bug-libtool <at> gnu.org
Subject: path in .la start with '='
Date: Thu, 29 Sep 2011 13:03:48 +0200

Hello,

The recently[1] added function `func_replace_sysroot' adds an '=' to a
given path.
But this path is then added to $dependency_libs in the .la file like this:

dependency_libs=' -L=/usr/lib'

resulting in errors like:

libtool: link: warning: cannot determine absolute directory name of `=/usr/lib'

what is the reasoning for this equal sign?  I have configured some
recent versions
of some software packages that use this libtool (pcre, glib) with
--with-sysroot and my PATH indeed starts with that directory.

regards,

  Peter

[1] http://permalink.gmane.org/gmane.comp.gnu.libtool.patches/10141

ps: I'm not subscribed to this list, it would be nice if you could cc
me on replies

Message #8 received at 9631 <at> debbugs.gnu.org (full text, mbox):

From: Vincent Lefevre <vincent <at> vinc17.net>
To: Peter Kruse <pjodrr <at> gmail.com>
Cc: 9631 <at> debbugs.gnu.org
Subject: Re: path in .la start with '='
Date: Wed, 7 Mar 2012 14:17:28 +0100

Hi,

On 2011-09-29 13:03:48 +0200, Peter Kruse wrote:
> Hello,
> 
> The recently[1] added function `func_replace_sysroot' adds an '=' to a
> given path.
> But this path is then added to $dependency_libs in the .la file like this:
> 
> dependency_libs=' -L=/usr/lib'
> 
> resulting in errors like:
> 
> libtool: link: warning: cannot determine absolute directory name of `=/usr/lib'
> 
> what is the reasoning for this equal sign?  I have configured some
> recent versions
> of some software packages that use this libtool (pcre, glib) with
> --with-sysroot and my PATH indeed starts with that directory.

Some user ran into the same problem with MPFR, but it doesn't seem to
be a bug, so that I think this bug should be closed. You need a more
recent Libtool (2.4+) to link.

The Libtool 2.4+ NEWS file says:

New in 2.4 2010-09-22: git version 2.2.11a, Libtool team:

* New features:

  - Sysroot support.  This allows you to build cross-compiled packages
    with the same prefix that will be used on the destination machine,
    and still find dependent libraries under the compiler's "sysroot".
    Without sysroot support, paths internal to the build system may leak
    into the product of the build.

    Sysroot support is disabled unless the --with-sysroot configure
    option is passed to configure, because .la files generated with
    sysroot support will _not_ be usable in general with older Libtools.

There is technical information here:

  http://permalink.gmane.org/gmane.comp.gnu.libtool.patches/10111

-- 
Vincent Lefèvre <vincent <at> vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Message #11 received at 9631 <at> debbugs.gnu.org (full text, mbox):

From: Vincent Lefevre <vincent <at> vinc17.net>
To: Peter Kruse <pjodrr <at> gmail.com>
Cc: 9631 <at> debbugs.gnu.org
Subject: Re: path in .la start with '='
Date: Wed, 7 Mar 2012 14:35:12 +0100

On 2012-03-07 14:17:28 +0100, Vincent Lefevre wrote:
> Some user ran into the same problem with MPFR, but it doesn't seem to
> be a bug, so that I think this bug should be closed. You need a more
> recent Libtool (2.4+) to link.
> 
> The Libtool 2.4+ NEWS file says:
> 
> New in 2.4 2010-09-22: git version 2.2.11a, Libtool team:
> 
> * New features:
> 
>   - Sysroot support.  This allows you to build cross-compiled packages
>     with the same prefix that will be used on the destination machine,
>     and still find dependent libraries under the compiler's "sysroot".
>     Without sysroot support, paths internal to the build system may leak
>     into the product of the build.
> 
>     Sysroot support is disabled unless the --with-sysroot configure
>     option is passed to configure, because .la files generated with
>     sysroot support will _not_ be usable in general with older Libtools.

However the user who sees this --with-sysroot option in some library
may not have this information if Libtool 2.4+ is not installed.

"./configure --help" says:

  --with-sysroot=DIR Search for dependent libraries within DIR
                        (or the compiler's sysroot if not specified).

This comes from:

# _LT_WITH_SYSROOT
# ----------------
AC_DEFUN([_LT_WITH_SYSROOT],
[AC_MSG_CHECKING([for sysroot])
AC_ARG_WITH([sysroot],
[  --with-sysroot[=DIR] Search for dependent libraries within DIR
                        (or the compiler's sysroot if not specified).],
[], [with_sysroot=no])

...

in libtool.m4. How about mentioning the compatibility problem here
for the "./configure --help" output?

-- 
Vincent Lefèvre <vincent <at> vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.