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>
Subject: Re: [PATCH] gnu: base: Add Glibc-Hurd Headers.
Date: Sat, 27 Sep 2014 11:31:53 +0200	[thread overview]
Message-ID: <87y4t5if3q.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzNSie=fQ0ENV7M_LskUc7gA5QdnT5Wpw17Pt5-wYgY4kw@mail.gmail.com> (Manolis Ragkousis's message of "Wed, 24 Sep 2014 16:01:15 +0300")

Manolis Ragkousis <manolis837@gmail.com> skribis:

> Taken care of the FIXME.

Thanks, I’ve merged it with the other commit on wip-hurd, and rebased it
on top of master.

> Just wanted to add that in base.scm, instead of gnu-gettext we needed
> perl. Probably I changed it by mistake while rebasing some local
> commits.

OK.

> And thread_terminate does exist, that's why it's enough for our needs.

You mean ‘thread_terminate_release’?  The comment in
libpthread-glibc-preparation.patch still reads:

--8<---------------cut here---------------start------------->8---
We are using a version of GNU Mach that lacks 'thread_terminate_release'
(not introduced yet).  The 'thread_terminate' RPC call will be enough for
our needs.
See <http://lists.gnu.org/archive/html/bug-hurd/2014-05/msg00127.html>.
--8<---------------cut here---------------end--------------->8---

Ludo’.

  reply	other threads:[~2014-09-27  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 21:16 [PATCH] gnu: base: Add Glibc-Hurd Headers Manolis Ragkousis
2014-08-29 13:48 ` Ludovic Courtès
2014-09-24 13:01   ` Manolis Ragkousis
2014-09-27  9:31     ` Ludovic Courtès [this message]
2014-09-27 13:50       ` Manolis Ragkousis
2014-09-27 17:30         ` Manolis Ragkousis
2014-09-28  9:51           ` 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=87y4t5if3q.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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.