unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Philippe SWARTVAGHER <philippe.swartvagher@inria.fr>
Cc: 54557@debbugs.gnu.org
Subject: bug#54557: “fakechroot” execution engine doesn’t work for Bash
Date: Mon, 28 Mar 2022 08:59:07 +0200	[thread overview]
Message-ID: <878rsu5zr8.fsf@gnu.org> (raw)
In-Reply-To: <de5ac5be-d6a2-1c21-4a1f-223281dc0b2c@inria.fr> (Philippe SWARTVAGHER's message of "Fri, 25 Mar 2022 11:16:13 +0100")

Hi,

Philippe SWARTVAGHER <philippe.swartvagher@inria.fr> skribis:

> FTR, the --without-bash-malloc is used in the Debian bash package:
>
> apt source bash
>
> cd bash-5.1/debian
>
> grep -Irn without-bash-malloc
> changelog:145:  * Configure the normal build --without-bash-malloc as well.
> changelog:1125:  * Configure the static build --without-bash-malloc.
> changelog:1462:  * Disable the GNU/kFreeBSD kludge
> (--without-bash-malloc). Closes: #234137.
> changelog:1546:  * Configure --without-bash-malloc on GNU/FreeBSD
> (closes: #194182).
> changelog:1739:  * Configure --without-bash-malloc. At least on hppa,
> this fixes an error,
> rules:79:    --without-bash-malloc
>
>
> This option is also advised in Linux From Scratch:
> https://www.linuxfromscratch.org/lfs/view/stable/chapter08/bash.html

Good to know, thanks for sharing.

I just realized that ‘bash-minimal’ in Guix already uses it, so that’s
another way to work around the ‘guix pack -RR’ issue at hand.

Ludo’.




  reply	other threads:[~2022-03-28  7:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 21:02 bug#54557: “fakechroot” execution engine doesn’t work for Bash Ludovic Courtès
2022-03-25 10:16 ` Philippe SWARTVAGHER
2022-03-28  6:59   ` Ludovic Courtès [this message]
2022-03-26  3:03 ` Maxim Cournoyer
2022-03-28 10:06   ` 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=878rsu5zr8.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=54557@debbugs.gnu.org \
    --cc=philippe.swartvagher@inria.fr \
    /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).