From: Dave Love <fx@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 27848@debbugs.gnu.org
Subject: [bug#27848] guix: build-system: gnu: Avoid warnings from "libtool finish"
Date: Mon, 31 Jul 2017 19:17:48 +0100 [thread overview]
Message-ID: <87k22obhdf.fsf@i-ulialbion.it.manchester.ac.uk> (raw)
In-Reply-To: <87k22o39s8.fsf@gnu.org> ("Ludovic \=\?iso-8859-1\?Q\?Court\=E8s\?\= \=\?iso-8859-1\?Q\?\=22's\?\= message of "Mon, 31 Jul 2017 17:28:55 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
> I’m not too keen on this approach, in large part because I’ve got used
> to the “ldconfig not found” messages,
It's OK if you know, but I assume it's common for newbies to see it and
waste time, as at least two of us did.
> but also because a simple change
> like this can create more problems than what it solves: packages where
> the “libtool” script lives in a different directory, packages where
> “libtool” is a different thing, packages where it’s read-only or where
> it’s a directory, etc.
OK, but I thought the common case of it at top level was worth fixing.
I guess you could check it's really a libtool script before editing it.
However, is there a good reason not to provide a dummy ldconfig which
does nothing, or prints a message about not doing anything?
next prev parent reply other threads:[~2017-07-31 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 14:40 [bug#27848] guix: build-system: gnu: Avoid warnings from "libtool finish" Dave Love
2017-07-31 15:28 ` Ludovic Courtès
2017-07-31 18:17 ` Dave Love [this message]
2017-07-31 19:26 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k22obhdf.fsf@i-ulialbion.it.manchester.ac.uk \
--to=fx@gnu.org \
--cc=27848@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).