From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 25527@debbugs.gnu.org
Subject: bug#25527: PostgreSQL retains references to ld-wrapper and coreutils
Date: Mon, 07 Dec 2020 22:05:19 +0100 [thread overview]
Message-ID: <87h7oxz5rk.fsf@gnu.org> (raw)
In-Reply-To: <87eelp6vnu.fsf@gmail.com> (zimoun's message of "Fri, 23 Oct 2020 13:15:01 +0200")
Hi,
Sorry for the multi-month delay…
zimoun <zimon.toutoune@gmail.com> skribis:
> The manual says (emphasis by me):
>
> References are a subset of the inputs of the derivation; this
> subset is AUTOMATICALLY COMPUTED by the build daemon by scanning
> all the files in the outputs.
>
> Therefore, how is it computed? Or what is the entry point to understand
> how the build daemon does?
The daemon scans build results, nothing fancy. See ‘scanForReferences’
in the C++ code.
> The output is the folder $(guix build postgresql)/, right? So it means
> one (or more) file refers to ld-wrapper and coreutils. How can I find
> which one? Other said, what are the tools I could use?
I’d do like this:
--8<---------------cut here---------------start------------->8---
$ grep -r $(guix build ld-wrapper) $(guix build postgresql)
/gnu/store/lrll3ibqags97g2hmjv4az9g1xif42g4-postgresql-11.6/lib/pgxs/src/Makefile.global:LD = /gnu/store/mpa04aq8lblbcviyxywxcsb1zbi0mf39-ld-wrapper-0/bin/ld
--8<---------------cut here---------------end--------------->8---
HTH! :-)
Ludo’.
next prev parent reply other threads:[~2020-12-07 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 8:57 bug#25527: PostgreSQL retains references to ld-wrapper and coreutils Ludovic Courtès
2020-10-21 22:13 ` zimoun
2020-10-23 10:05 ` Ludovic Courtès
2020-10-23 11:15 ` zimoun
2020-12-07 21:05 ` Ludovic Courtès [this message]
2020-12-20 17:57 ` Marius Bakke
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=87h7oxz5rk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=25527@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).