From: ludo@gnu.org (Ludovic Courtès)
To: "Dupéron Georges" <jahvascriptmaniac@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Including sources in guix archive --export
Date: Mon, 24 Sep 2018 17:29:49 +0200 [thread overview]
Message-ID: <87zhw6ud5e.fsf@gnu.org> (raw)
In-Reply-To: <CAKQnwqaAxXE3h-otBw894rDg8y8c6pwDY2j5EgUP0DOAhpdydA@mail.gmail.com> ("Dupéron Georges"'s message of "Thu, 20 Sep 2018 20:50:45 +0200")
Hi Georges,
Dupéron Georges <jahvascriptmaniac@gmail.com> skribis:
> Thanks a lot Ludovic, this really helped :) .
>
> The following command nearly worked:
>
> guix archive --export --recursive hello $(guix build --source
> --sources=transitive hello $MORE_SOURCES)
>
> but I had to explicitly add more sources, namely /gnu/store/*-$i.drv for
> these files:
>
> binutils-2.23.2.tar.xz
> bison-3.0.4.tar.xz
> gc-7.6.4.tar.gz
> gcc-4.8.2.tar.xz
> glibc-2.18.tar.xz
> guile-2.0.9.tar.xz
> gcc-4.9.4.tar.xz
> gettext-0.19.8.1.tar.gz
> gmp-6.1.2.tar.xz
> guile-2.2.3.tar.xz
> libatomic_ops-7.6.4.tar.gz
> libffi-3.2.1.tar.gz
> libtool-2.4.6.tar.xz
> libunistring-0.9.9.tar.xz
> m4-1.4.18.tar.xz
> perl-5.26.1.tar.gz
> pkg-config-0.29.2.tar.gz
> static-binaries.tar.xz
> texinfo-6.5.tar.xz
> zlib-1.2.11.tar.gz
>
> It seems that these are used to bootstrap guile and GCC. Is there a way to
> get this list programmatically, without hardcoding version numbers?
Does “guix build --sources=all hello” help?
HTH,
Ludo’.
next prev parent reply other threads:[~2018-09-24 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 21:12 Including sources in guix archive --export Georges Dupéron
2018-09-14 10:00 ` Ludovic Courtès
2018-09-20 18:50 ` Dupéron Georges
2018-09-24 15:29 ` Ludovic Courtès [this message]
2018-09-24 19:30 ` Dupéron Georges
2018-10-02 9:57 ` Ludovic Courtès
2018-10-02 11:49 ` Georges Dupéron
2018-10-02 12:10 ` 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=87zhw6ud5e.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=jahvascriptmaniac@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 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.