configure --with-guile-for-build

* configure --with-guile-for-build
@ 2003-11-03  0:33 Kevin Ryde
  2003-11-13 19:15 ` Marius Vollmer
  0 siblings, 1 reply; 2+ messages in thread
From: Kevin Ryde @ 2003-11-03  0:33 UTC (permalink / raw)


[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

Below would be my suggestion to just have GUILE_FOR_BUILD for
specifying the build system guile.

In particular note that the gnu standards advise against using --with
to specify filenames, it's meant to specify an external package the
build should utilize.

Hopefully few people will need to override the default
GUILE_FOR_BUILD, and those smart enough to know what to do should be
happy with an AC_ARG_VAR variable.  Some advice could be put in the
manual if there might be any remaining doubts.

        * configure.in (--with-guile-for-build): Remove this option, it's not
        normal style for --with.
        (GUILE_FOR_BUILD): Use AC_ARG_VAR.


[-- Attachment #2: configure.in.guile-for-build.diff --]
[-- Type: text/plain, Size: 690 bytes --]

--- configure.in.~1.225.~	1970-01-01 10:00:01.000000000 +1000
+++ configure.in	2003-11-03 10:27:47.000000000 +1000
@@ -968,15 +968,13 @@
 else
   GUILE_FOR_BUILD='$(preinstguile)'
 fi   
-AC_ARG_WITH(guile-for-build,
-  [  --with-guile-for-build=guile  native guile executable, to be used during build])
-test -n "$with_guile_for_build" && GUILE_FOR_BUILD="$with_guile_for_build"
 
 ## AC_MSG_CHECKING("if we are cross compiling")
 ## AC_MSG_RESULT($cross_compiling)
 if test "$cross_compiling" = "yes"; then
    AC_MSG_RESULT($GUILE_FOR_BUILD)
 fi
+AC_ARG_VAR(GUILE_FOR_BUILD,[guile for build system])
 AC_SUBST(GUILE_FOR_BUILD)
   			
 ## If we're using GCC, ask for aggressive warnings.

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread