From: ludo@gnu.org (Ludovic Courtès)
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: bug-guix@gnu.org
Subject: Re: FTBFS on GNU/Hurd
Date: Tue, 02 Jul 2013 23:13:27 +0200 [thread overview]
Message-ID: <87ehbgekco.fsf@gnu.org> (raw)
In-Reply-To: <51D321A0.3090804@gmail.com> (Cyril Roelandt's message of "Tue, 02 Jul 2013 20:53:20 +0200")
Oops, just saw you had already replied.
Cyril Roelandt <tipecaml@gmail.com> skribis:
> In /usr/include/errno.h:
>
> /* The Hurd <bits/errno.h> defines `error_t' as an enumerated type so
> that printing `error_t' values in the debugger shows the names. We
> might need this definition sometimes even if this file was included
> before. */
>
> Which explains your issue. I think this is more of a Nix or GNU
> bug.
guix-daemon.cc is from Guix, not from Nix.
> According to the GNU documentation
> (http://www.gnu.org/software/libc/manual/html_node/Argp-Parser-Functions.html#Argp-Parser-Functions),
> the parse_opt function is fine. Should we ask the Hurd people how they
> handle this ?
Yes, I think this is a bug in libc on GNU/Hurd because our parse_opt
function is perfectly valid per the libc manual. Would you like to ping
bug-hurd@gnu.org? :-)
Ludo’.
next prev parent reply other threads:[~2013-07-02 21:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 15:06 FTBFS on GNU/Hurd Matthew Lien
2013-07-02 18:53 ` Cyril Roelandt
2013-07-02 21:13 ` Ludovic Courtès [this message]
2013-07-03 7:42 ` Matthew Lien
2013-07-02 21:09 ` Ludovic Courtès
2013-07-03 7:46 ` Matthew Lien
2013-07-03 9:38 ` Ludovic Courtès
2013-07-03 15:58 ` Matthew Lien
2013-07-04 11:46 ` Ludovic Courtès
2013-07-04 14:00 ` Matthew Lien
2013-07-04 14:23 ` Ludovic Courtès
2013-07-04 15:40 ` Matthew Lien
2013-07-04 20:42 ` Ludovic Courtès
2013-07-05 9:05 ` BlueT - Matthew Lien - 練喆明
2013-07-05 9:55 ` Ludovic Courtès
2013-07-05 11:16 ` BlueT - Matthew Lien - 練喆明
2013-07-05 11:47 ` Ludovic Courtès
2013-07-04 20:54 ` Ludovic Courtès
2013-07-05 9:30 ` BlueT - Matthew Lien - 練喆明
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=87ehbgekco.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=tipecaml@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.