After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 726780 - ${!GUILE_REQUIRED} is used in configure.ac
${!GUILE_REQUIRED} is used in configure.ac
Status: RESOLVED FIXED
Product: aisleriot
Classification: Other
Component: general
git master
Other FreeBSD
: Normal normal
: ---
Assigned To: aisleriot-maint
aisleriot-maint
Depends on:
Blocks:
 
 
Reported: 2014-03-20 15:08 UTC by Ting-Wei Lan
Modified: 2015-04-13 18:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ting-Wei Lan 2014-03-20 15:08:30 UTC 
The syntax ${!GUILE_REQUIRED} is not defined in POSIX. If /bin/sh is not bash, the configure script will fail.
Comment 1 Robert Ancell 2014-07-18 03:16:37 UTC 
This breaks builds on Debian/Ubuntu.
Comment 2 Ting-Wei Lan 2014-07-18 08:07:17 UTC 
(In reply to comment #1)
> This breaks builds on Debian/Ubuntu.

Is bash not available when building packages on Debian/Ubuntu?
Comment 3 Robert Ancell 2014-07-20 02:34:51 UTC 
It is (In reply to comment #2)
> Is bash not available when building packages on Debian/Ubuntu?

It is but for some reason libtool breaks with this change. I didn't investigate further.
Comment 4 Christian Persch 2014-08-16 16:46:04 UTC 
I really need the exact error here.
Comment 5 Christian Persch 2014-11-03 17:45:26 UTC 
Reverted this since it seems to be causing problems when /bin/sh != bash (e.g. comment 1). So you'll just have to run configure like this: CONFIG_SHELL=/bin/bash ./configure ...
Comment 6 Ting-Wei Lan 2014-11-03 18:24:06 UTC 
Does '#! /usr/bin/env bash' not work?
Comment 7 Christian Persch 2014-11-03 18:54:25 UTC 
Apparently not. Seems it caused configure to generate a non-working libtool.
Comment 8 Ting-Wei Lan 2014-11-03 19:05:40 UTC 
Can we use this instead?

if test -z "$CONFIG_SHELL"; then
  CONFIG_SHELL="`command -v bash`"
  SHELL=${CONFIG_SHELL-/bin/sh}
fi
Comment 9 Christian Persch 2014-11-03 21:04:48 UTC 
No, CONFIG_SHELL needs to be set before AC_INIT which can't be done from within configure.ac.
Comment 10 Ting-Wei Lan 2014-11-04 10:50:44 UTC 
configure and config.status use '#! $SHELL' when creating scripts, so overriding both CONFIG_SHELL and SHELL (which is copied from CONFIG_SHELL) variables works.