all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>,
	bug-hurd@gnu.org, "Samuel Thibault" <samuel.thibault@gnu.org>
Subject: Re: GSoC: Porting Guix to Hurd week 3+4 report.
Date: Tue, 2 Jun 2015 17:55:52 +0200	[thread overview]
Message-ID: <87lhg2je9j.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <CAFtzXzNbu3y_H+_meY+BD2u=BTq7Ju4O7LQ7+BOi3K66GW4Qpw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1883 bytes --]

Hi!

On Tue, 2 Jun 2015 17:06:48 +0300, Manolis Ragkousis <manolis837@gmail.com> wrote:
> > > [GCC build problem]

> I am attaching the complete build
> log and any related log.

Thanks, and I tried, but it's too cumbersome to handle that massive
amount of data in this way.  It'll be much easier if I can reproduce the
problem locally.

Shame on me, but I've never actively used/built Guix before.  I do know
about <https://github.com/Phant0mas/Guix-on-Hurd>, and that there must be
a Guix manual existing -- but can you help me get started, please?
(Pointers to specific parts of documentation are appreciated, of course.)

Is there a way to have the "Guix build process" create a shell script (or
some other "linearized log of command invocations")?  At this point, the
latter would be earier for me to debug (evem reproduce?), compared to
really "learning Guix" -- which I'll be happy to do (and have been
meaning to do for a looong time...), but then it's probably going to take
longer for me to really get started.

Alternatively/additionally, I'd also appreciate a high-level
(coarse-grained) overview about the steps you're executing right now.
(Maybe that already documented somewhere, or is obvious from the "Guix
build description files" -- which I have not yet looked at.)  That is,
something like: 1) install GNU Mach headers: configure [...] && make
install [...], 2) install Hurd headers: [...], 3) build minimal cross-GCC
configured with [...] options: [...], and so on.


> > Thanks for all the uneasy & frustrating work!
> 
> You are welcome, I really enjoy working on it. :-).

Muahahaha!  ;-P The GNU toolchain can be a pain.  (Same for every other
non-trivial piece of software, heh...)  If you suffer through enough of
it, you might, one day, make an honest living out of what you've learned.
;-D


Grüße,
 Thomas

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

  reply	other threads:[~2015-06-02 15:55 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lhg2je9j.fsf@kepler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=Guix-devel@gnu.org \
    --cc=bug-hurd@gnu.org \
    --cc=ludo@gnu.org \
    --cc=manolis837@gmail.com \
    --cc=samuel.thibault@gnu.org \
    /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.