From: Andreas Enge <andreas@enge.fr>
To: bug-guix@gnu.org
Subject: Re: GNU Prolog: configure: error: cannot run /bin/sh ./config.sub
Date: Wed, 30 Jan 2013 22:16:27 +0100 [thread overview]
Message-ID: <201301302216.27704.andreas@enge.fr> (raw)
In-Reply-To: <87d2wm9y0u.fsf@karetnikov.org>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
Am Mittwoch, 30. Januar 2013 schrieb Nikita Karetnikov:
> The attached recipe fails with the following error:
>
> patch-shebang: ./src/config.sub: changing `/bin/sh' to
> `/nix/store/4mg8b8vvmava68y64qmm70gqfnhhjzmx-bash-4.2/bin/sh'
>
> [...]
>
> configure: error: cannot run /bin/sh ./config.sub
My suspicion is that the patch-shebang in src/config.sub does not solve the
problem, but that in some Makefile, there is an explicit call "/bin/sh
./config.sub". Maybe you can do a "grep" on the Makefiles to verify.
If this is the problem, you need to pach them out "manually" in your build
recipe (maybe from Makefile after, or Makefile.am before configuring), see,
for instance, icu4c.scm.
Andreas
[-- Attachment #2: Type: text/html, Size: 3398 bytes --]
next prev parent reply other threads:[~2013-01-30 21:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 21:11 GNU Prolog: configure: error: cannot run /bin/sh ./config.sub Nikita Karetnikov
2013-01-30 21:16 ` Andreas Enge [this message]
2013-01-31 5:24 ` [PATCH] gnu: Add GNU Prolog. (was: GNU Prolog: configure: error: cannot run /bin/sh ./config.sub) Nikita Karetnikov
2013-01-31 9:13 ` [PATCH] gnu: Add GNU Prolog Ludovic Courtès
2013-02-01 16:31 ` Nikita Karetnikov
2013-02-01 16:59 ` Ludovic Courtès
2013-01-31 9:22 ` [PATCH] gnu: Add GNU Prolog. (was: GNU Prolog: configure: error: cannot run /bin/sh ./config.sub) Andreas Enge
2013-01-30 22:06 ` GNU Prolog: configure: error: cannot run /bin/sh ./config.sub 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=201301302216.27704.andreas@enge.fr \
--to=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 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.