From: Andy Wingo <wingo@pobox.com>
To: Marco Maggi <marco.maggi-ipsu@poste.it>
Cc: bug-guile@gnu.org
Subject: Re: guile-2.0.0 fails to build without threads
Date: Wed, 13 Apr 2011 11:55:41 +0200 [thread overview]
Message-ID: <m3zknuh3vm.fsf@unquote.localdomain> (raw)
In-Reply-To: <87y63gj765.fsf@rapitore.luna> (Marco Maggi's message of "Tue, 12 Apr 2011 08:49:22 +0200")
Hi Marco,
On Tue 12 Apr 2011 08:49, Marco Maggi <marco.maggi-ipsu@poste.it> writes:
> I am following up here because I have a problem at the same
> point when building branch stable-2.0; I have just fetched
> from the repository, so I have the commit c89b452993...
Actually, failing at that point is quite common: it's the first time the
newly-built Guile is actually used. It would be more appropriate to
start a new thread, but since we're here...
> scmsigs.c: In function 'signal_delivery_thread':
> scmsigs.c:159:3: warning: implicit declaration of function 'GC_pthread_sigm=
> ask' [-Wimplicit-function-declaration]
This is odd. The configure script should detect the presence of
GC_pthread_sigmask, and only emit references to it if it is found. Can
you grep your config.log for instances of "GC_pthread" ? Also, can you
grep your libguile/scmconfig.h for "PTHREAD" ?
> memoize.c:478:***Mismatching FUNC_NAME. Should be: `#define FUNC_NAME s_"@=
> prompt"'
These are harmless, but thank you for being thorough in the report.
> Throw without catch before boot:
> Throw to key stack-overflow with args (#f "Stack overflow" #f #f)Aborting.
Can you submit a backtrace please? You can do so by running
meta/gdb-uninstalled-guile --no-auto-compile, then "b scm_ithrow",
"run", and then "bt" when the breakpoint hits.
Thanks,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-04-13 9:55 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
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 [this message]
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=m3zknuh3vm.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=marco.maggi-ipsu@poste.it \
/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).