From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: undefined reference to `scm_init_guile'
Date: Fri, 10 Mar 2006 22:41:16 +0000 [thread overview]
Message-ID: <87k6b1x6r7.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <20060310222332.GA23867@esat.kuleuven.be> (steven mestdagh's message of "Fri, 10 Mar 2006 23:23:32 +0100")
steven mestdagh <steven.mestdagh@esat.kuleuven.be> writes:
> Neil Jerram [2006-03-10, 22:10:39]:
>>
>> Digging a bit further, this looks like it's caused by
>> HAVE_PTHREAD_ATTR_GETSTACK not being defined. Can you confirm that
>> when you run ./configure, it says that pthread_attr_getstack can't be
>> found?
>
> no, this function is found, and HAVE_PTHREAD_ATTR_GETSTACK is defined
> in config.h.
OK, so it's HAVE_LIBC_STACK_END that is not defined, then? When this
is the case, 1.8 leaves scm_init_guile undefined, whereas 1.6 would
use the vast pile of magic in gc_os_dep.c.
Does that sound right? If it is, I wonder why the change was made to
remove the gc_os_dep.c fallback option; I can't see anything obvious
in the ChangeLog. (gc_os_dep.c and the necessary scm_get_stack_base()
definitions are still there in 1.8, they're just not used.)
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-03-10 22:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 22:35 [Neil Jerram] Re: undefined reference to `scm_init_guile' Neil Jerram
2006-03-10 6:41 ` steven mestdagh
2006-03-10 22:10 ` Neil Jerram
2006-03-10 22:23 ` steven mestdagh
2006-03-10 22:41 ` Neil Jerram [this message]
2006-03-10 23:01 ` steven mestdagh
2006-03-11 18:43 ` Neil Jerram
2006-03-11 19:02 ` steven mestdagh
2006-03-11 20:45 ` Neil Jerram
2006-03-25 20:16 ` Marius Vollmer
2006-03-26 0:01 ` Marius Vollmer
2006-03-26 9:20 ` steven mestdagh
2006-03-25 20:11 ` 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=87k6b1x6r7.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.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.
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).