From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: configure CC_FOR_BUILD
Date: Mon, 12 May 2003 00:08:04 -0500 [thread overview]
Message-ID: <87he8092h7.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87wugx5bao.fsf@zip.com.au> (Kevin Ryde's message of "Mon, 12 May 2003 09:11:11 +1000")
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
next prev parent reply other threads:[~2003-05-12 5:08 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 [this message]
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=87he8092h7.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
/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).