From: Kevin Ryde <user42@zip.com.au>
Subject: configure.in stack growth typo
Date: Mon, 12 May 2003 08:09:38 +1000 [thread overview]
Message-ID: <87u1c187a5.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
I applied a correction,
* configure.in (SCM_I_GSC_STACK_GROWS_UP): Fix missing comma in
AC_TRY_RUN.
This was causing downward stack systems to get the cross-compile
warning, and cross-compile to fail completely.
Incidentally, if this really must be known at configure time then it
might be better for the cross compile to be fatal, to avoid mysterious
problems. It could advise how to force a value with a cache variable
or something.
[-- Attachment #2: configure.in.grow.diff --]
[-- Type: text/plain, Size: 623 bytes --]
Index: configure.in
===================================================================
RCS file: /cvsroot/guile/guile/guile-core/configure.in,v
retrieving revision 1.213
diff -u -u -r1.213 configure.in
--- configure.in 7 Apr 2003 17:31:02 -0000 1.213
+++ configure.in 11 May 2003 22:06:48 -0000
@@ -788,7 +788,7 @@
AC_TRY_RUN(aux (l) unsigned long l;
{ int x; exit (l >= ((unsigned long)&x)); }
main () { int q; aux((unsigned long)&q); },
- SCM_I_GSC_STACK_GROWS_UP=1
+ [SCM_I_GSC_STACK_GROWS_UP=1],
[],
[AC_MSG_WARN(Guessing that stack grows down -- see scmconfig.h)])
[-- 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-11 22:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87u1c187a5.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).