From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: Guix-devel <Guix-devel@gnu.org>,
bug-hurd@gnu.org, Samuel Thibault <samuel.thibault@gnu.org>,
Manolis Ragkousis <manolis837@gmail.com>
Subject: Re: GSoC: Porting Guix to Hurd week 3+4 report.
Date: Mon, 08 Jun 2015 14:59:33 +0200 [thread overview]
Message-ID: <87lhfuuzii.fsf@gnu.org> (raw)
In-Reply-To: <873823i6gl.fsf@kepler.schwinge.homeip.net> (Thomas Schwinge's message of "Sun, 7 Jun 2015 22:55:38 +0200")
Thomas Schwinge <thomas@codesourcery.com> skribis:
> On Thu, 04 Jun 2015 22:48:48 +0200, ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) wrote:
>> Manolis Ragkousis <manolis837@gmail.com> skribis:
[...]
>> autoreconf && ./configure --localstatedir=/var \
>> --with-libgcrypt-prefix=/gnu/store/... && make
>
> (Not relevant right now, but why is the libgcrypt path not communicated
> via the environment variables set up with guix environment? Is that just
> because there are no appropriate environment variables, or something
> else?) Also, I wanted to note that I, very guixy, computed that path
> using:
>
> $ guix build libgcrypt
> warning: failed to install locale: Invalid argument
> /gnu/store/r16v30hlw2d6n232rm37p53qy8rpr7f2-libgcrypt-1.6.3
> /gnu/store/42ls5n7k6lai1k6xfa8v8wks7nn9g3gn-libgcrypt-1.6.3-debug
Yes, that’s fine.
> Next, I ran:
>
> $ ./pre-inst-env guix build --target=i686-pc-gnu gcc-4.7 -K -c 8
>
>> > After it fails
>
> ..., and eventually reproduced the problem. However, that took a series
> of steps that was much longer that I had anticipated:
It turns out that hydra.gnu.org is not (yet) serving pre-built binaries
for this branch, so you ended up rebuilding the world, including doing a
complete bootstrap of the distro (info "(guix) Bootstrapping").
I realize this is terribly inconvenient, so apologies for that!
I hope we can soon merge the changes to the “core” packages in the
‘core-updates’ branch, and have ‘wip-hurd’ contain only very specific
patches. That way, most of the things will have pre-built binaries
available on hydra.gnu.org.
> Assuming I need to patch the GCC sources, do I just do that in
> /tmp/nix-build-gcc-4.7.4.drv-0/gcc-4.7.4/, and then, to continue the
> build, just run the same guix build command again? (I guess I'll also
> have to preserve my changes elsewhere, as that temporary working tree
> will be removed upon a successful build?)
The simplest way is to use the --with-source option of ‘guix build’,
which allows you to specify an alternate source tarball (info "(guix)
Invoking guix build").
Now, from a discussion we had on IRC, I think the problem reported at
the beginning of this thread is fixed. Manolis, can you confirm?
Also, I think the target should be 4.9 or 4.8, but definitely not 4.7.
See also
<http://lists.gnu.org/archive/html/guix-devel/2015-06/msg00052.html>.
Thank you!
Ludo’.
next prev parent reply other threads:[~2015-06-08 12:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 8:13 GSoC: Porting Guix to Hurd week 3+4 report Manolis Ragkousis
2015-05-31 20:22 ` Ludovic Courtès
2015-06-02 14:06 ` Manolis Ragkousis
2015-06-02 15:55 ` Thomas Schwinge
2015-06-03 21:25 ` Manolis Ragkousis
2015-06-04 20:48 ` Ludovic Courtès
2015-06-07 20:55 ` Thomas Schwinge
2015-06-08 11:43 ` Manolis Ragkousis
2015-06-08 12:59 ` Ludovic Courtès [this message]
2015-06-08 13:12 ` Manolis Ragkousis
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=87lhfuuzii.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=Guix-devel@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=manolis837@gmail.com \
--cc=samuel.thibault@gnu.org \
--cc=thomas@codesourcery.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).