unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: Build of attr fails with non-bash shell
Date: Fri, 21 Dec 2012 00:09:02 +0100	[thread overview]
Message-ID: <87ip7wgw35.fsf@gnu.org> (raw)
In-Reply-To: <201212202334.35082.andreas@enge.fr> (Andreas Enge's message of "Thu, 20 Dec 2012 23:34:34 +0100")

Hi,

Andreas Enge <andreas@enge.fr> skribis:

> A web search leads me to
>    http://trac.osgeo.org/gdal/ticket/4102
> It looks as if bash is needed, whereas my /bin/sh is (a symbolic link to)
> dash. And indeed compilation succeeds after replacing it by a symbolic link
> to bash.

Yes, that’s not very surprising.

> Do you see another way of fixing this problem?

For this and related issues, I’m attempting in the ‘core-updates’ branch
to allow builds without /bin/sh in the chroot.  Instead, builds use the
Bash binary that’s explicitly passed as an input.

After some tweaking (more on that later), it can successfully build
everything up to ‘guile-final’.  What remains to be seen is how much
manual tweaking each package will require.  I’m hoping it will be
reasonable, but it doesn’t come for free either, as can be seen from the
commits that adjust packages in ‘core-updates’.

Thanks,
Ludo’.

  reply	other threads:[~2012-12-20 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-20 22:34 Build of attr fails with non-bash shell Andreas Enge
2012-12-20 23:09 ` Ludovic Courtès [this message]
2012-12-21 10:44   ` Andreas Enge
2012-12-21 11:00     ` 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=87ip7wgw35.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=bug-guix@gnu.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).