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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Karl Berry <karl <at> freefriends.org>
Subject: bug#71595: closed (Re: bug#71595: error message improvement:
 "only absolute run-paths are allowed")
Date: Wed, 03 Jul 2024 14:02:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#71595: error message improvement: "only absolute run-paths are allowed"

which was filed against the libtool package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 71595 <at> debbugs.gnu.org.

-- 
71595: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=71595
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
To: 71595-done <at> debbugs.gnu.org, Karl Berry <karl <at> freefriends.org>
Subject: Re: bug#71595: error message improvement: "only absolute run-paths
 are allowed"
Date: Wed, 3 Jul 2024 17:00:15 +0300

[Message part 3 (text/plain, inline)]

On 03/07/2024 01:24, Karl Berry wrote:
>      attached patch with a rework of the wording for the second case.
> 
> Looks perfect to me.

I am glad! I have applied it to development:

https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=f5a7acee1db1b785ec2506e89026fb46ebd518a8

>      Here is the relevant commit for why the spacing was added:
>      ...
>      https://github.com/gnulib-modules/bootstrap/issues/33
> 
> I can see the point, and no improvement is apparent. It still seems an
> unfortunate outcome, but certainly not worth any of us spending more
> time on it :).
> 
> Thanks Ileana! So glad you've started looking after libtool. --best, karl.

Thank you for your bug reports! I am happy to help and continue to learn
more from experienced hackers :)

-- 
Ileana Dumitrescu

GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354

[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

[Message part 6 (message/rfc822, inline)]

From: Karl Berry <karl <at> freefriends.org>
To: bug-libtool <at> gnu.org
Subject: 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.

Previous Next

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