From: Andreas Schwab <schwab@suse.de>
Cc: yamaoka@jpl.org, emacs-devel@gnu.org
Subject: Re: configure problem
Date: Tue, 15 Jul 2003 10:09:23 +0200 [thread overview]
Message-ID: <jey8z05hzg.fsf@sykes.suse.de> (raw)
In-Reply-To: <200307150658.PAA14821@etlken.m17n.org> (Kenichi Handa's message of "Tue, 15 Jul 2003 15:58:05 +0900 (JST)")
Kenichi Handa <handa@m17n.org> writes:
|> In article <b9yvfu4z3q4.fsf@jpl.org>, Katsumi Yamaoka <yamaoka@jpl.org> writes:
|> > configure.in:50: error: possibly undefined macro: AC_DEFINE
|> > If this token and others are legitimate, please use m4_pattern_allow.
|> > See the Autoconf documentation.
|>
|> > Here is a patch which has been confirmed by the NetBSD user.
|> > I don't know why the AC_DEFINE macro is not expanded there,
|> > though. :{
|>
|> The reason is described in the comment above this jambo
|> "case" statement as this:
|>
|> dnl This used to use changequote, but, apart from `changequote is evil'
|> dnl per the autoconf manual, we can speed up autoconf somewhat by quoting
|> dnl the great gob of text. Thus it's not processed for possible expansion.
|> dnl Just make sure the brackets remain balanced.
I have now checked in this change:
* configure.in: Temporarily leave quoting for AC_DEFINE.
--- configure.in.~1.343.~ 2003-07-14 13:49:29.000000000 +0200
+++ configure.in 2003-07-15 10:04:52.000000000 +0200
@@ -222,9 +222,9 @@ case "${canonical}" in
## NetBSD ports
*-*-netbsd* )
opsys=netbsd
- if test -f /usr/lib/crti.o; then
+ if test -f /usr/lib/crti.o; then]
AC_DEFINE(HAVE_CRTIN)
- fi
+[ fi
case "${canonical}" in
alpha*-*-netbsd*) machine=alpha ;;
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2003-07-15 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 6:46 configure problem Katsumi Yamaoka
2003-07-15 6:58 ` Kenichi Handa
2003-07-15 7:03 ` Katsumi Yamaoka
2003-07-15 8:09 ` Andreas Schwab [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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jey8z05hzg.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=emacs-devel@gnu.org \
--cc=yamaoka@jpl.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).