unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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 18:36:47 +0100	[thread overview]
Message-ID: <87ppcfdtn4.fsf@gnu.org> (raw)
In-Reply-To: <20141122165959.GA4878@intra> (John Darrington's message of "Sat, 22 Nov 2014 18:00:00 +0100")

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.

(And if it’s really needed, it’s easy to add that symlink.)

> I think the symlink is wrong anyway, since in the build environment the symlink target 
> will not exist.

Of course it exists!

--8<---------------cut here---------------start------------->8---
$ guix build "/gnu/store/y634jqapqxs6ajzifx0shd8w7iaf9yrc-pkg-config-mips64el-linux-gnu-0.27.1.drv"
The following file will be downloaded:
   /gnu/store/9ycjrm4n6w4ar740vsxlacbd2x5s3khr-pkg-config-mips64el-linux-gnu-0.27.1
@ substituter-started /gnu/store/9ycjrm4n6w4ar740vsxlacbd2x5s3khr-pkg-config-mips64el-linux-gnu-0.27.1 /gnu/store/fkq63515pz3l8bdyi6qhchb9pida7pzp-guix-0.8.47739f5/libexec/guix/substitute-binary
found valid signature for '/gnu/store/9ycjrm4n6w4ar740vsxlacbd2x5s3khr-pkg-config-mips64el-linux-gnu-0.27.1', from 'http://hydra.gnu.org/nar/9ycjrm4n6w4ar740vsxlacbd2x5s3khr-pkg-config-mips64el-linux-gnu-0.27.1'
downloading `/gnu/store/9ycjrm4n6w4ar740vsxlacbd2x5s3khr-pkg-config-mips64el-linux-gnu-0.27.1' (0.0 MiB installed)...
http://hydra.gnu.org/nar/9ycjrm4n6w4ar740vsxlacbd2x5s3khr-pkg-config-mips64el-linux-gnu-0.27.1	   0.2 KiB transferred@ substituter-succeeded /gnu/store/9ycjrm4n6w4ar740vsxlacbd2x5s3khr-pkg-config-mips64el-linux-gnu-0.27.1
/gnu/store/9ycjrm4n6w4ar740vsxlacbd2x5s3khr-pkg-config-mips64el-linux-gnu-0.27.1

$ ls -l /gnu/store/9ycjrm4n6w4ar740vsxlacbd2x5s3khr-pkg-config-mips64el-linux-gnu-0.27.1/bin/
total 4
lrwxrwxrwx 2 root root 76  1 janv.  1970 mips64el-linux-gnu-pkg-config -> /gnu/store/s432k19icqqjchfp83klghv3p07q5hdd-pkg-config-0.27.1/bin/pkg-config

$ guix gc --references /gnu/store/9ycjrm4n6w4ar740vsxlacbd2x5s3khr-pkg-config-mips64el-linux-gnu-0.27.1
/gnu/store/s432k19icqqjchfp83klghv3p07q5hdd-pkg-config-0.27.1
--8<---------------cut here---------------end--------------->8---

Thanks,
Ludo’.

  reply	other threads:[~2014-11-22 17:36 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 [this message]
2014-11-22 18:03     ` John Darrington
2014-11-22 20:22       ` Ludovic Courtès
  -- 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

  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=87ppcfdtn4.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 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).