From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: core-updates is back
Date: Sat, 22 Nov 2014 21:22:41 +0100 [thread overview]
Message-ID: <87sihbastq.fsf@gnu.org> (raw)
In-Reply-To: <20141122180329.GA5003@intra> (John Darrington's message of "Sat, 22 Nov 2014 19:03:29 +0100")
John Darrington <john@darrington.wattle.id.au> skribis:
> On Sat, Nov 22, 2014 at 06:36:47PM +0100, Ludovic Courtès wrote:
> John Darrington <john@darrington.wattle.id.au> skribis:
>
> > There is some oddness in cross-pkg-config: It creates a symlink to the real pkg-config,
> > But does not do so for the pkg.m4 file.
>
> Why would the missing pkg.m4 be a problem? It’s only used when
> bootstrapping Autoconf-based packages.
>
> Right. If you want to bootstrap an autoconf based package (for example, guix-devel from package-management.scm),
> then it will fail.
Oh right, this one is a good example. I’ll add the symlink.
> (And if it’s really needed, it’s easy to add that symlink.)
>
>
> Of course it exists!
>
> I thought that whilst bulding things were in a chroot jail where only those things explicitly declared as inputs
> actually existed.
More precisely, the inputs *and* their run-time dependencies are
available.
For instance, if a package has Coreutils as an input, then its build
process gets both Coreutils and libc in its chroot (otherwise the
Coreutils programs would be unusable.)
Ludo’.
next prev parent reply other threads:[~2014-11-22 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 12:01 core-updates is back Ludovic Courtès
2014-11-22 17:00 ` John Darrington
2014-11-22 17:36 ` Ludovic Courtès
2014-11-22 18:03 ` John Darrington
2014-11-22 20:22 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-14 6:51 Ludovic Courtès
2014-06-06 13:33 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sihbastq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.