From: Richard Braun <rbraun@sceen.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, rennes@openmailbox.org,
Manolis Ragkousis <manolis837@gmail.com>,
25463@debbugs.gnu.org
Subject: bug#25463: guile-2.0.13 Check errors
Date: Mon, 13 Feb 2017 10:47:51 +0100 [thread overview]
Message-ID: <20170213094751.GA29250__42599.3470977575$1487003183$gmane$org@shattrath> (raw)
In-Reply-To: <87vasfqfat.fsf@gnu.org>
On Sun, Feb 12, 2017 at 10:18:02PM +0100, Ludovic Courtès wrote:
> Manolis Ragkousis <manolis837@gmail.com> skribis:
>
> > Locally on Hurd I am using this patch
> > http://paste.lisp.org/display/338954 on the glibc/hurd package to work
> > around that test failure. Ideally we need to modify the way guile
> > handles time.[1]
>
> Does ‘glibc/hurd’ have this patch in ‘core-updates’? Should it?
>
> Would it make sense to address this issue in Guile instead of libc,
> Richard? I guess the answer depends on how many programs make this
> assumption besides Guile.
I'd say applications shouldn't be concerned with that, this problem
should remain solved by the system components, and libc (or procfs or
whatever) are the right places to deal with it.
See https://lists.gnu.org/archive/html/bug-hurd/2013-06/msg00089.html.
--
Richard Braun
next prev parent reply other threads:[~2017-02-13 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 1:25 guile-2.0.13 Check errors rennes
2017-02-11 21:03 ` bug#25463: " Ludovic Courtès
[not found] ` <87vasg1luf.fsf@gnu.org>
2017-02-12 8:37 ` rennes
2017-02-12 13:44 ` Manolis Ragkousis
[not found] ` <a5b20e9d-bdb7-83f7-60cf-fffd86015213@gmail.com>
2017-02-12 21:18 ` Ludovic Courtès
[not found] ` <87vasfqfat.fsf@gnu.org>
2017-02-13 9:47 ` Richard Braun [this message]
2017-02-19 15:53 ` Manolis Ragkousis
[not found] ` <675c7503-e8ca-3e6d-b7ff-fe82bbfa0d37@gmail.com>
2017-03-06 16:00 ` Ludovic Courtès
[not found] ` <874lz6s8d1.fsf@gnu.org>
2017-03-06 16:45 ` Manolis Ragkousis
2017-03-06 22:53 ` 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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='20170213094751.GA29250__42599.3470977575$1487003183$gmane$org@shattrath' \
--to=rbraun@sceen.net \
--cc=25463@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=manolis837@gmail.com \
--cc=rennes@openmailbox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).