From: Kevin Ryde <user42@zip.com.au>
Subject: configure CC_FOR_BUILD
Date: Mon, 12 May 2003 09:11:11 +1000 [thread overview]
Message-ID: <87wugx5bao.fsf@zip.com.au> (raw)
[-- 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
next reply other threads:[~2003-05-11 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 23:11 Kevin Ryde [this message]
2003-05-12 5:08 ` configure CC_FOR_BUILD Rob Browning
2003-05-16 0:00 ` Kevin Ryde
2003-05-18 21:59 ` Kevin Ryde
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wugx5bao.fsf@zip.com.au \
--to=user42@zip.com.au \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).