all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>,
	bug-hurd@gnu.org, Samuel Thibault <samuel.thibault@gnu.org>
Subject: Re: GSoC: Porting Guix to Hurd week 2 report
Date: Sat, 16 May 2015 21:11:54 +0200	[thread overview]
Message-ID: <87r3qgqqv9.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzPsAQpenXKLP2t0zQ_cM9MRJrDkTSw9+2a5JMNyi9KUYQ@mail.gmail.com> (Manolis Ragkousis's message of "Fri, 15 May 2015 22:17:14 +0300")

Hello,

Thanks for the update, it all seems to be on track!

Hopefully the availability of the glibc-hurd tarball allow the code to
be simplified, and the Hurd-specific parts of the glibc recipes to be
reduced.

> I was thinking about following Mark's suggestion of having a generic
> glibc package with all the common
> configure flags and inputs, and the two others inheriting from it,
> defining the specific sources and
> inputs/flags. WDYT?

In an ideal world, the only differences between the two libcs would be
the source (and version) and the inputs.  How far are we from that now?

If we can achieve that, we’ll be able to keep a single glibc recipe.  If
there are other differences, we’ll see.

> Ludovic I don't have anything to report on the binaries actually
> running on hurd right now,
> because I am hoping to test that with the actual bootstrap tarballs.

No problem!

Cheers,
Ludo’.

      parent reply	other threads:[~2015-05-16 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 19:17 GSoC: Porting Guix to Hurd week 2 report Manolis Ragkousis
2015-05-16  7:06 ` Andreas Enge
2015-05-16 19:11 ` Ludovic Courtès [this message]

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=87r3qgqqv9.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 \
    /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.