From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: Alen Skondro <askondro@gmail.com>, bug-guix@gnu.org
Subject: Re: tests/packages.scm fails with make check
Date: Tue, 22 Jan 2013 00:22:14 +0100 [thread overview]
Message-ID: <8738xu5dg9.fsf@gnu.org> (raw)
In-Reply-To: <87pq0zqzew.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 20 Jan 2013 23:09:59 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> Andreas Enge <andreas@enge.fr> skribis:
>
>> But building the automake package fails with an enormous number of errors
>> in the check phase:
>
> Oh, that's most likely related to the /bin/sh change: I suppose the test
> suite generates a many scripts with #!/bin/sh.
Commit 7cd1d7b fixes Automake’s test suite. If you want to burn CPU
cycles, please test. :-)
This turned out to be trickier than expected, because ‘autoconf’
generates shell scripts, and it’s the shebang of those scripts that
should be patched to refer to our Bash instead of /bin/sh.
Yet, users who install Autoconf must get the real one, which emits
#!/bin/sh.
This commit addresses that by using an ‘autoconf’ wrapper that does the
shebang patching, and is used for the sole purpose of running Automake’s
test suite.
Ludo’.
next prev parent reply other threads:[~2013-01-21 23:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 13:20 tests/packages.scm fails with make check Alen Skondro
2013-01-19 13:56 ` Ludovic Courtès
2013-01-19 14:28 ` Alen Skondro
2013-01-19 22:15 ` Andreas Enge
2013-01-20 14:00 ` Ludovic Courtès
2013-01-20 14:55 ` Andreas Enge
2013-01-20 22:09 ` Ludovic Courtès
2013-01-21 23:22 ` Ludovic Courtès [this message]
2013-01-22 15:03 ` Andreas Enge
2013-01-22 16:58 ` Ludovic Courtès
2013-01-22 20:59 ` Andreas Enge
2013-01-22 21:09 ` Andreas Enge
2013-01-22 22:21 ` 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=8738xu5dg9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=askondro@gmail.com \
--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).