all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Braun <rbraun@sceen.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, rennes@openmailbox.org, 25463@debbugs.gnu.org
Subject: Re: bug#25463: guile-2.0.13 Check errors
Date: Mon, 13 Feb 2017 10:47:51 +0100	[thread overview]
Message-ID: <20170213094751.GA29250@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

  reply	other threads:[~2017-02-13  9:48 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
2017-02-12  8:37   ` rennes
2017-02-12 13:44     ` Manolis Ragkousis
2017-02-12 21:18       ` Ludovic Courtès
2017-02-13  9:47         ` Richard Braun [this message]
2017-02-19 15:53   ` Manolis Ragkousis
2017-03-06 16:00     ` Ludovic Courtès
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170213094751.GA29250@shattrath \
    --to=rbraun@sceen.net \
    --cc=25463@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --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.
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.