From: Kevin Ryde <user42@zip.com.au>
Subject: Re: configure CC_FOR_BUILD
Date: Fri, 16 May 2003 10:00:37 +1000 [thread overview]
Message-ID: <87r86zg3q2.fsf@zip.com.au> (raw)
In-Reply-To: 87he8092h7.fsf@raven.i.defaultvalue.org
[-- 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
next prev parent reply other threads:[~2003-05-16 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 23:11 configure CC_FOR_BUILD Kevin Ryde
2003-05-12 5:08 ` Rob Browning
2003-05-16 0:00 ` Kevin Ryde [this message]
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=87r86zg3q2.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).