Hi!
> Another problem I have is the following: When configuring a source tree
> of unrelated projects, I sometimes want to give configuration options
> for a specific project
Sometimes it helps to look how other people do it. What about this patch:
--snip--
diff -u -r autoconf/acgeneral.m4 autoconf-local/acgeneral.m4
--- autoconf/acgeneral.m4 Mon Aug 7 14:33:18 2000
+++ autoconf-local/acgeneral.m4 Sat Aug 12 12:38:36 2000
@@ -5146,7 +5221,9 @@
esac
# Check for guested configure; otherwise get Cygnus style configure.
- if test -f $ac_sub_srcdir/configure; then
+ if test -f $ac_sub_srcdir/configure.gnu; then
+ ac_sub_configure="$SHELL $ac_sub_srcdir/configure.gnu"
+ elif test -f $ac_sub_srcdir/configure; then
ac_sub_configure="$SHELL $ac_sub_srcdir/configure"
elif test -f $ac_sub_srcdir/configure.in; then
ac_sub_configure=$ac_configure
--snip--
Additionally, I'd like to block out another false install program:
-snip--
diff -u -r autoconf/acspecific.m4 autoconf-local/acspecific.m4
--- autoconf/acspecific.m4 Fri Aug 4 11:21:52 2000
+++ autoconf-local/acspecific.m4 Sat Aug 12 13:17:18 2000
@@ -201,6 +201,7 @@
# SunOS /usr/etc/install
# IRIX /sbin/install
# AIX /bin/install
+# AmigaOS /c/install, which installs bootblocks on floppy discs
# AIX 4 /usr/bin/installbsd, which doesn't work without a -g flag
# AFS /usr/afsws/bin/install, which mishandles nonexistent args
# SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff"
@@ -212,7 +213,7 @@
for ac_dir in $PATH; do
# Account for people who put trailing slashes in PATH elements.
case $ac_dir/ in
- /|./|.//|/etc/*|/usr/sbin/*|/usr/etc/*|/sbin/*|/usr/afsws/bin/*|/usr/ucb/*) ;;
+ /|./|.//|/etc/*|/c/*|/usr/sbin/*|/usr/etc/*|/sbin/*|/usr/afsws/bin/*|/usr/ucb/*)
+;;
*)
# OSF1 and SCO ODT 3.0 have their own names for install.
# Don't use installbsd from OSF since it installs stuff as root
--snip--
Another idea I have would be to mark decisions made because of
cross-compiling by something like "(cross)" or "(cross-default)". Even
better would be if cross-compiling wouldn't make some test fail immediately,
but note down something went wrong and fail at the end.
Yours, Rüdiger.
