unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Problems with handicapped 'bash' from glibc package
Date: Wed, 12 Feb 2014 14:14:00 +0100	[thread overview]
Message-ID: <87ob2c1njb.fsf@gnu.org> (raw)
In-Reply-To: <871tz8oldk.fsf@netris.org> (Mark H. Weaver's message of "Wed, 12 Feb 2014 02:12:07 -0500")

Mark H Weaver <mhw@netris.org> skribis:

> The 'bash' in the glibc package is handicapped in at least two ways:
>
> * It can't set the locale, because it looks for locales in
>   /nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-glibc-intermediate-2.18-locales
>
> * It can't look up anything from NSS, such as passwd data, because it
>   tries to load the modules from
>   /nix/store/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee-glibc-intermediate-2.18
>
> There are two problems that need to be addressed, I think:
>
> * Users could easily end up with this handicapped 'bash' as their
>   primary bash, if they installed (or upgraded?) 'glibc' since the last
>   time I installed 'bash'.  This happened to me, for example.
>
> * Some (most?) programs in Guix that launch subprocesses with the shell
>   use this handicapped one.  For example, every time I run 'w3m', it
>   prints two warnings about 'sh' being unable to set the locale.
>
> Any suggestions about how we should address these problems?

Indeed, that’s a problem.

For the record, the handicaped bash comes from the removal of /bin/sh
[0].  It is used by ‘system’ and ‘popen’.

Looks like solving this would require either rewriting glibc references
in the static bash binary (tricky, especially since the glibc directory
names have different lengths currently), or building Bash directly in
the glibc-final derivation so that it refers to the right libc with all
its bells and whistles.

The latter sounds best, but it would require to sort of duplicate the
build recipe of Bash internally.

Another option would be to apply glibc-bootstrap-system.patch
unconditionally, but I’m not sure if it’s a good idea.

Thoughts?

Ludo’.

[0] http://lists.gnu.org/archive/html/bug-guix/2013-01/msg00041.html

  reply	other threads:[~2014-02-12 13:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  7:12 Problems with handicapped 'bash' from glibc package Mark H Weaver
2014-02-12 13:14 ` Ludovic Courtès [this message]
2014-02-12 17:39   ` Mark H Weaver
2014-02-12 19:31     ` Andreas Enge
2014-02-12 20:33       ` Ludovic Courtès
2014-02-12 21:33         ` Mark H Weaver
2014-02-13  9:14           ` Andreas Enge
2014-03-23 16:19 ` Ludovic Courtès
2014-03-23 20:19   ` Mark H Weaver
2014-03-23 20:27     ` Ludovic Courtès
2014-03-24  3:31       ` Mark H Weaver
2014-03-28 13:48         ` Ludovic Courtès
2014-03-24  3:55       ` Optimizing union.scm Mark H Weaver
2014-03-24 13:45         ` Ludovic Courtès
2014-03-25  7:04           ` Mark H Weaver
2014-03-25 17:18             ` Ludovic Courtès
2014-03-25 22:30               ` Mark H Weaver
2014-03-25 22:58                 ` Ludovic Courtès
2014-03-27  7:09                   ` Mark H Weaver
2014-03-27  9:57                     ` Ludovic Courtès
2014-04-02 14:14             ` Optimizing ‘guix package’ Ludovic Courtès
2014-04-02 16:58               ` Mark H Weaver
2014-03-26 23:29   ` Problems with handicapped 'bash' from glibc package 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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87ob2c1njb.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).