GNU bug report logs - #18917
--disable-static breaks unittests (runpath-in-lalib.at & need_lib_prefix.at)

Previous Next

Package: libtool;

Reported by: Mike Frysinger <vapier <at> gentoo.org>

Date: Sat, 1 Nov 2014 02:56:01 UTC

Severity: normal

Full log


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

From: Mike Frysinger <vapier <at> gentoo.org>
To: bug-libtool <at> gnu.org
Subject: --disable-static breaks unittests (runpath-in-lalib.at &
 need_lib_prefix.at)
Date: Fri, 31 Oct 2014 22:54:55 -0400
[Message part 1 (text/plain, inline)]
when you configure libtool with --disable-static, these two unittests fail:
	runpath-in-lalib.at
	need_lib_prefix

if you hack the libtool script to set build_old_libs=yes by default, then the 
unittests pass.  it looks like libtool has flags to enable building of either 
static or shared libs, but there's no way to make it build both (which is the 
default with --enable-{shared,static}).

along those lines, it'd be nice if --disable-static didn't do this to the local 
copy of libtool that gets installed.  i understand the relationship between the 
configure flags and the generated libtool script -- normally you use the local 
libtool build the local libs and then only install those libs.  this is even how 
it's used with libltdl.  but the libtool package itself is a bit special in that 
it also installs the libtool script.

in Gentoo atm, i'm hacking this by setting build_old_libs=yes in the generated 
libtool script before testing/installing.  but ideally it'd be possible to 
install `libtool` with settings based on what the system can do, not how the 
package is building libltdl.{a,so}.
-mike
[signature.asc (application/pgp-signature, inline)]

This bug report was last modified 10 years and 121 days ago.

Previous Next


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