From: Leo Famulari <leo@famulari.name>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 25258@debbugs.gnu.org
Subject: bug#25258: Bashisms when building 0.11.0
Date: Tue, 12 Feb 2019 20:46:30 -0500 [thread overview]
Message-ID: <20190213014630.GA27743@jasmine.lan> (raw)
In-Reply-To: <c3eb8da7-acf5-f661-48d1-fd70d322560d@pelzflorian.de>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
On Sat, Dec 24, 2016 at 08:26:27AM +0100, pelzflorian (Florian Pelz) wrote:
> Guix' testsuite uses the non-POSIX bashism `type -P guile` in
> tests/guix-packages.sh which causes a test failure when using
> Dash to provide /bin/sh instead of Bash. Additionally gnu/local.mk uses
> brace expansion which is not part of POSIX and does not work on Dash.
>
> When building Guix on Parabola GNU/Linux-libre modified to use Dash as
> /bin/sh,[1] this causes the Guix build to fail. For building, the guix
> 0.11.0 package from AUR[2] was used. The attached “patch” allows for a
> successful build but is not what we want.
>
> Guix should probably not use bashisms in its Makefile includes and
> either not use bashisms in its test suite or make sure the test suite is
> executed explicitly with Bash and not /bin/sh.
About two years have passed on this bug report without comment. Is it a
"wontfix"?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-13 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-24 7:26 bug#25258: Bashisms when building 0.11.0 pelzflorian (Florian Pelz)
2019-02-13 1:46 ` Leo Famulari [this message]
2020-03-22 20:28 ` Leo Famulari
2020-05-16 6:33 ` bug#25258: Bashisms in make rules elaexuotee--- via Bug reports for GNU Guix
2020-05-17 16:42 ` Vincent Legoll
2020-05-17 17:34 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=20190213014630.GA27743@jasmine.lan \
--to=leo@famulari.name \
--cc=25258@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).