GNU bug report logs - #71595
error message improvement: "only absolute run-paths are allowed"

Previous Next

Package: libtool;

Reported by: Karl Berry <karl <at> freefriends.org>

Date: Sun, 16 Jun 2024 16:07:02 UTC

Severity: normal

Done: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Karl Berry <karl <at> freefriends.org>
To: 71595 <at> debbugs.gnu.org
Subject: bug#71595: error message improvement: "only absolute run-paths are allowed"
Date: Sun, 16 Jun 2024 10:06:16 -0600
With a libtool invocation like this (comes from the Automake test
instdir-ltlib.sh, which is intentionally testing empty directory values):

/bin/sh ./libtool  --tag=CC   --mode=link cc  -g -O2   -o libfoo.la -rpath  libfoo.lo  

libtool reports:

libtool:   error: only absolute run-paths are allowed

I gather the problem is a missing argument to -rpath, which I see
reported in several places over the years.

I suggest that it would be clearer if the error message included the
offending option and argument, as in:

libtool: error: argument to -rpath is not absolute: libfoo.lo

(I also don't understand why there are three spaces
after "libtool:" instead of one, but whatever.) --thanks, karl.




This bug report was last modified 1 year and 40 days ago.

Previous Next


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