From: Kevin Ryde <user42@zip.com.au>
Subject: configure --with-guile-for-build
Date: Mon, 03 Nov 2003 10:33:40 +1000 [thread overview]
Message-ID: <87n0bemgt7.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
Below would be my suggestion to just have GUILE_FOR_BUILD for
specifying the build system guile.
In particular note that the gnu standards advise against using --with
to specify filenames, it's meant to specify an external package the
build should utilize.
Hopefully few people will need to override the default
GUILE_FOR_BUILD, and those smart enough to know what to do should be
happy with an AC_ARG_VAR variable. Some advice could be put in the
manual if there might be any remaining doubts.
* configure.in (--with-guile-for-build): Remove this option, it's not
normal style for --with.
(GUILE_FOR_BUILD): Use AC_ARG_VAR.
[-- Attachment #2: configure.in.guile-for-build.diff --]
[-- Type: text/plain, Size: 690 bytes --]
--- configure.in.~1.225.~ 1970-01-01 10:00:01.000000000 +1000
+++ configure.in 2003-11-03 10:27:47.000000000 +1000
@@ -968,15 +968,13 @@
else
GUILE_FOR_BUILD='$(preinstguile)'
fi
-AC_ARG_WITH(guile-for-build,
- [ --with-guile-for-build=guile native guile executable, to be used during build])
-test -n "$with_guile_for_build" && GUILE_FOR_BUILD="$with_guile_for_build"
## AC_MSG_CHECKING("if we are cross compiling")
## AC_MSG_RESULT($cross_compiling)
if test "$cross_compiling" = "yes"; then
AC_MSG_RESULT($GUILE_FOR_BUILD)
fi
+AC_ARG_VAR(GUILE_FOR_BUILD,[guile for build system])
AC_SUBST(GUILE_FOR_BUILD)
## If we're using GCC, ask for aggressive warnings.
[-- 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-11-03 0:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 0:33 Kevin Ryde [this message]
2003-11-13 19:15 ` configure --with-guile-for-build Marius Vollmer
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=87n0bemgt7.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).