all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org
Subject: Re: libc upgrade vs. incompatible locales
Date: Mon, 31 Aug 2015 13:49:10 +0200	[thread overview]
Message-ID: <87a8t7brux.fsf@gnu.org> (raw)
In-Reply-To: <87egijx352.fsf@igalia.com> (Andy Wingo's message of "Mon, 31 Aug 2015 10:39:53 +0200")

Andy Wingo <wingo@igalia.com> skribis:

> On Sun 30 Aug 2015 21:46, ludo@gnu.org (Ludovic Courtès) writes:
>
>> The binary format for locales is dependent on the libc version.  Over
>> the last few releases, it turned out to be compatible, but that of 2.22
>> differs from that of 2.21 (a new element was added to locale categories,
>> according to ChangeLog.)
>
> Does this amount to a binary-incompatible change to libc?  I guess not
> if you make sure that if you had a statically linked binary, that you
> set LOCPATH appropriately....
>
> What if we built bootstrap binaries to statically link their LOCPATH ?
> Is that even possible?

I don’t think locale data can be embedded in binaries.  Also, it’s a
good strategy to avoid rebuilding the bootstrap binaries as much as
possible, as it intuitively suggests that a Thompson attack is unlikely.

Ludo’.

  reply	other threads:[~2015-08-31 11:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 15:05 Why does glibc provide bash? Andy Wingo
2015-08-11  4:23 ` Mark H Weaver
2015-08-11  8:21   ` Andy Wingo
2015-08-18 16:44     ` Ludovic Courtès
2015-08-19 22:33       ` Ludovic Courtès
2015-08-29 17:56         ` Ludovic Courtès
2015-08-30 19:46         ` libc upgrade vs. incompatible locales Ludovic Courtès
2015-08-31  8:39           ` Andy Wingo
2015-08-31 11:49             ` Ludovic Courtès [this message]
2015-08-31 13:09               ` Andy Wingo
2015-09-02 12:29                 ` 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=87a8t7brux.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.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.