From: ludo@gnu.org (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: 27848@debbugs.gnu.org
Subject: [bug#27848] guix: build-system: gnu: Avoid warnings from "libtool finish"
Date: Mon, 31 Jul 2017 17:28:55 +0200 [thread overview]
Message-ID: <87k22o39s8.fsf@gnu.org> (raw)
In-Reply-To: <874ltyhrj2.fsf@i-ulialbion.it.manchester.ac.uk> (Dave Love's message of "Thu, 27 Jul 2017 15:40:33 +0100")
Dave Love <fx@gnu.org> skribis:
> --- a/guix/build/gnu-build-system.scm
> +++ b/guix/build/gnu-build-system.scm
> @@ -271,9 +271,15 @@ makefiles."
> ;; Call `configure' with a relative path. Otherwise, GCC's build system
> ;; (for instance) records absolute source file names, which typically
> ;; contain the hash part of the `.drv' file, leading to a reference leak.
> - (zero? (apply system* bash
> - (string-append srcdir "/configure")
> - flags))))
> + (and (zero? (apply system* bash
> + (string-append srcdir "/configure")
> + flags))
> + ;; Avoid warnings about from "libtool finish" about not finding
> + ;; ldconfig.
> + (if (file-exists? "libtool")
> + (begin (substitute* "libtool" (("ldconfig") ":"))
> + #t)
> + #t))))
>
I’m not too keen on this approach, in large part because I’ve got used
to the “ldconfig not found” messages, 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.
Since this is a rebuild-the-world change, we have to make sure it’s
really worth it.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-07-31 15:30 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 [this message]
2017-07-31 18:17 ` Dave Love
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=87k22o39s8.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27848@debbugs.gnu.org \
--cc=fx@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).