From: Marco Maggi <marco.maggi-ipsu@poste.it>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org
Subject: Re: guile-2.0.0 fails to build without threads
Date: Sat, 21 May 2011 15:51:49 +0200 [thread overview]
Message-ID: <87ipt4f9fu.fsf@rapitore.luna> (raw)
In-Reply-To: <m3d3jctpa9.fsf@unquote.localdomain> (Andy Wingo's message of "Sat, 21 May 2011 10:45:50 +0200")
Andy Wingo wrote:
> On Fri 20 May 2011 20:41, Marco Maggi <marco.maggi-ipsu@poste.it> writes:
>> Andy Wingo wrote:
>>> Thanks. You seem to be running on system in which the
>>> stack grows up. Is that the case? Check
>>> libguile/scmconfig.h and config.log.
>> Yes, I have:
>> #define SCM_STACK_GROWS_UP 1 /* 0 or 1 */
>> in "scmconfig.h"; my system is just a i686-pc-linux-gnu.
> But on those systems, the stack grows down, no?
> I suggest that this is a configuration error somehow. Check your
> config.log.
Someone left ACTION-IF-FALSE empty and also left the test
without "checking" message in this chunk of "configure.ac":
SCM_I_GSC_STACK_GROWS_UP=0
AC_RUN_IFELSE([AC_LANG_SOURCE(
[AC_INCLUDES_DEFAULT
int
find_stack_direction ()
{
static char *addr = 0;
auto char dummy;
if (addr == 0)
{
addr = &dummy;
return find_stack_direction ();
}
else
return (&dummy > addr) ? 1 : -1;
}
int
main ()
{
return find_stack_direction () < 0;
}])],
[SCM_I_GSC_STACK_GROWS_UP=1],
[],
[AC_MSG_WARN(Guessing that stack grows down -- see scmconfig.h)])
so I can only guess that what happens is described by the
following chunk of "config.log":
configure:39214: checking for iconveh_escape_sequence
configure:39232: gcc -o conftest -O3 -march=i686 -mtune=i686 conftest.c -lcrypt -lm >&5
configure:39232: $? = 0
configure:39232: ./conftest
configure:39232: $? = 0
configure:39234: result: 2
configure:39295: gcc -o conftest -O3 -march=i686 -mtune=i686 conftest.c -lcrypt -lm >&5
configure:39295: $? = 0
configure:39295: ./conftest
configure:39295: $? = 0
configure:39310: checking for BDW_GC
the test between "checking for iconveh_escape_sequence" and
"checking for BDW_GC"; the exit status is zero, which causes
the variable to be correctly set to:
SCM_I_GSC_STACK_GROWS_UP='1'
maybe the problem is that GCC 4.6.0 with -O3 optimises the
program in such a way that the test is invalidated.
--
Marco Maggi
next prev parent reply other threads:[~2011-05-21 13:51 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 14:47 guile-2.0.0 fails to build without threads Marijn
2011-04-11 16:19 ` Andy Wingo
2011-04-12 7:26 ` Marijn
2011-04-13 10:05 ` Andy Wingo
2011-04-13 13:44 ` Marijn
2011-04-13 14:09 ` Andy Wingo
2011-04-13 14:27 ` Marijn
2011-04-13 15:22 ` Andy Wingo
2011-04-14 13:25 ` Marijn
2011-04-28 11:17 ` Andy Wingo
2011-04-28 13:08 ` Ludovic Courtès
2011-04-28 13:15 ` Andy Wingo
2011-04-28 15:09 ` Ludovic Courtès
2011-05-03 14:58 ` Marijn
2011-05-04 12:19 ` Ludovic Courtès
2011-05-05 8:04 ` Marijn
2011-05-05 12:08 ` Ludovic Courtès
2011-05-05 13:59 ` Marijn
2011-05-05 14:25 ` Ludovic Courtès
2011-05-06 8:16 ` Marijn
2011-05-06 9:52 ` Ludovic Courtès
2011-05-06 12:49 ` Marijn
2011-05-10 7:43 ` Marijn
2011-05-03 14:55 ` Marijn
2011-04-12 6:49 ` Marco Maggi
2011-04-13 9:04 ` Marco Maggi
2011-04-13 11:42 ` Marco Maggi
2011-04-13 12:26 ` Andy Wingo
2011-04-13 13:56 ` Marco Maggi
2011-04-28 11:21 ` Andy Wingo
2011-05-02 6:20 ` Marco Maggi
2011-05-20 9:37 ` Andy Wingo
2011-05-20 18:41 ` Marco Maggi
2011-05-21 2:23 ` Mark H Weaver
2011-05-21 8:45 ` Andy Wingo
2011-05-21 13:51 ` Marco Maggi [this message]
2011-05-21 14:29 ` Neil Jerram
2011-06-17 10:25 ` Andy Wingo
2011-06-20 8:06 ` Andy Wingo
2011-06-22 21:39 ` Neil Jerram
2011-04-13 9:55 ` Andy Wingo
2011-04-13 14:19 ` Marco Maggi
2011-04-13 21:57 ` Ludovic Courtès
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=87ipt4f9fu.fsf@rapitore.luna \
--to=marco.maggi-ipsu@poste.it \
--cc=bug-guile@gnu.org \
--cc=wingo@pobox.com \
/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).