configure CC_FOR_BUILD

configure CC_FOR_BUILD

[Kevin Ryde]

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

I applied a change

        * configure.in (CC_FOR_BUILD): Use AC_ARG_VAR.

This gets CC_FOR_BUILD described in ./configure --help, and preserves
its value across reconfigures.

Unless anyone is very attached to --with-cc-for-build, I'd suggest
removing that option and just leave the CC_FOR_BUILD variable.  The
latter is moderately standard (eg. config.guess uses it), and an extra
guile specific option won't really add much.


[-- Attachment #2: configure.in.cc-for-build-arg-var.diff --]
[-- Type: text/plain, Size: 353 bytes --]

--- configure.in.~1.215.~	2003-05-12 08:50:01.000000000 +1000
+++ configure.in	2003-05-12 09:05:22.000000000 +1000
@@ -938,7 +938,7 @@
 CCLD_FOR_BUILD="$CC_FOR_BUILD"
 
 AC_SUBST(cross_compiling)
-AC_SUBST(CC_FOR_BUILD)
+AC_ARG_VAR(CC_FOR_BUILD,[build system C compiler])
 AC_SUBST(CCLD_FOR_BUILD)
 	
 ## libtool erroneously calls CC_FOR_BUILD HOST_CC;

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

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

Re: configure CC_FOR_BUILD

[Rob Browning]

Kevin Ryde <user42@zip.com.au> writes:

> Unless anyone is very attached to --with-cc-for-build, I'd suggest
> removing that option and just leave the CC_FOR_BUILD variable.  The
> latter is moderately standard (eg. config.guess uses it), and an extra
> guile specific option won't really add much.

If CC_FOR_BUILD is the "mostly standard" approach, I'd be inclined to
agree...

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


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

Re: configure CC_FOR_BUILD

[Kevin Ryde]

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

Rob Browning <rlb@defaultvalue.org> writes:
>
> If CC_FOR_BUILD is the "mostly standard" approach, I'd be inclined to
> agree...

I removed the option.  (Strictly speaking --with is supposed to be for
specifying other packages and libraries, not build tools.)

        * configure.in (--with-cc-for-build): Remove this option, CC_FOR_BUILD
        variable is more or less standard, and is adequate for the task.


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

--- configure.in.~1.216.~	2003-05-12 09:05:22.000000000 +1000
+++ configure.in	2003-05-16 09:50:07.000000000 +1000
@@ -924,9 +924,6 @@
 else
   CC_FOR_BUILD="${CC_FOR_BUILD-$CC}"
 fi   
-AC_ARG_WITH(cc-for-build,
-  [  --with-cc-for-build=CC  native C compiler, to be used during build])
-test -n "$with_cc_for_build" && CC_FOR_BUILD="$with_cc_for_build"
      
 ## AC_MSG_CHECKING("if we are cross compiling")
 ## AC_MSG_RESULT($cross_compiling)

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

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

Re: configure CC_FOR_BUILD

[Kevin Ryde]

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

I wrote:
>
>        * configure.in (--with-cc-for-build): Remove this option, CC_FOR_BUILD
>        variable is more or less standard, and is adequate for the task.

I also updated the README,

	* README (Cross building Guile): Remove --with-cc-for-build in favour
	of CC_FOR_BUILD.


[-- Attachment #2: README.cc-for-build.diff --]
[-- Type: text/plain, Size: 864 bytes --]

--- README.~1.91.~	2003-03-27 09:31:32.000000000 +1000
+++ README	2003-05-19 07:57:57.000000000 +1000
@@ -216,10 +216,13 @@
 
     ./configure --host=i686-pc-cygwin --disable-shared
 
-Two special options for cross building are available:
+A C compiler for the build system is required.  The default is
+"PATH=/usr/bin:$PATH cc".  If that doesn't suit it can be specified
+with the CC_FOR_BUILD variable in the usual way, for instance
 
---with-cc-for-build      --- native C compiler, to be used during build
-                             defaults to: `PATH=/usr/bin:$PATH cc'
+    ./configure --host=m68k-unknown-linux-gnu CC_FOR_BUILD=/my/local/gcc
+
+A further special option for cross building is available:
 
 --with-guile-for-build   --- native Guile executable, to be used during build
                              defaults to: `guile', assuming you just

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

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