unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: configure CC_FOR_BUILD
Date: Mon, 19 May 2003 07:59:31 +1000	[thread overview]
Message-ID: <87smrbykzg.fsf@zip.com.au> (raw)
In-Reply-To: 87r86zg3q2.fsf@zip.com.au

[-- 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

      reply	other threads:[~2003-05-18 21:59 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
2003-05-18 21:59     ` Kevin Ryde [this message]

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=87smrbykzg.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).