all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Omar Radwan <toxemicsquire4@gmail.com>
To: Manolis Ragkousis <manolis837@gmail.com>, guix-devel@gnu.org
Subject: Re: What's the current state of HURD on Guix?
Date: Thu, 11 Sep 2014 06:04:01 -0700	[thread overview]
Message-ID: <CAMwaQA+qCpxkeMS6pJ7qWGkWPhKkkwqT=jLFn5oPxoMFebHyGw@mail.gmail.com> (raw)
In-Reply-To: <CAFtzXzM80cYyEev-JpMsYXX8zLn=m5nJjAw7WUegUkHJ6jxdeA@mail.gmail.com>

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

Will it be usable by Guix stable?
On Sep 10, 2014 10:37 PM, "Manolis Ragkousis" <manolis837@gmail.com> wrote:

> Hello Omar
>
> I am the one working on that port. We are getting there, just more
> slowly cause I am working on some university projects.
>
> We had some issues with glibc/hurd which refused to build (the
> upstream version could not be built, whether the debian could) but
> thankfully with solved that, with lot's of help from the Hurd guys.
>
> Currently Ludovic uploaded the glibc/hurd related patches on the
> wip-hurd branch. Some small things need to be fixed and then it will
> be merged with master. I will send the related patch probably this
> week.
> Packages already part of guix: gnumach headers, mig, hurd headers.
>
> We are getting there :-)
>
> Thank you for your interest and I hope I answered your question.
> Manolis
>

[-- Attachment #2: Type: text/html, Size: 1163 bytes --]

  reply	other threads:[~2014-09-11 13:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11  4:40 What's the current state of HURD on Guix? Omar Radwan
2014-09-11  5:37 ` Manolis Ragkousis
2014-09-11 13:04   ` Omar Radwan [this message]
2014-09-11 14:17     ` Manolis Ragkousis
2014-09-11 14:19     ` Ludovic Courtès
2014-09-11 14:36       ` Omar Radwan

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='CAMwaQA+qCpxkeMS6pJ7qWGkWPhKkkwqT=jLFn5oPxoMFebHyGw@mail.gmail.com' \
    --to=toxemicsquire4@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=manolis837@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.