From: ludo@gnu.org (Ludovic Courtès)
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Allow disabling of CONFIG_SHELL in the configure phase
Date: Tue, 13 Sep 2016 14:07:29 +0200 [thread overview]
Message-ID: <87fup457ge.fsf@gnu.org> (raw)
In-Reply-To: <cu77fahzk8w.fsf@systemreboot.net> (Arun Isaac's message of "Mon, 12 Sep 2016 12:18:31 +0530")
Arun Isaac <arunisaac@systemreboot.net> skribis:
> I am packaging optipng (http://optipng.sourceforge.net/) with the
> gnu-build-system, and its configure script does not like being passed
> CONFIG_SHELL. It fails with the following error:
>
> ./configure: error: unknown option: CONFIG_SHELL=/gnu/store/ykzwykkvr2c80rw4l1qh3mvfdkl7jibi-bash-4.3.42/bin/bash
>
> Can we allow disabling of CONFIG_SHELL by passing some keyword argument
> to the configure phase? Right now, the CONFIG_SHELL argument is always
> passed to ./configure, and the only way to get around this is to replace
> the configure phase for the optipng package with a specialized function
> that does not pass CONFIG_SHELL. That seems like too much work, and it
> will be nice if we can just disable CONFIG_SHELL with a keyword argument.
I find that it’s not that much work to replace the ‘configure’ phase,
and it’s not too common (Autoconf-generated ‘configure’ scripts all
honor CONFIG_SHELL.)
We could add a Boolean flag for CONFIG_SHELL, but I bet manually written
‘configure’ scripts may need more than just that anyway, so I’m not sure
it would buy us much.
WDYT?
Ludo’.
next prev parent reply other threads:[~2016-09-13 12:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 6:48 Allow disabling of CONFIG_SHELL in the configure phase Arun Isaac
2016-09-13 12:07 ` Ludovic Courtès [this message]
2016-09-13 13:49 ` Arun Isaac
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=87fup457ge.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@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.