unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: steven mestdagh <steven.mestdagh@esat.kuleuven.be>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: undefined reference to `scm_init_guile'
Date: Sat, 11 Mar 2006 20:02:47 +0100	[thread overview]
Message-ID: <20060311190247.GA21246@esat.kuleuven.be> (raw)
In-Reply-To: <87r758rfei.fsf@ossau.uklinux.net>

Neil Jerram [2006-03-11, 18:43:17]:
> steven mestdagh <steven.mestdagh@esat.kuleuven.be> writes:
> 
> > Neil Jerram [2006-03-10, 22:41:16]:
> >> 
> >> 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.
> >
> > indeed this is a function we do not have.
> 
> Would you mind trying the program below on your system?  It may be
> that on OpenBSD the pthread approach works for the main thread, and so
> HAVE_LIBC_STACK_END isn't needed anyway.

$ cc -pthread -o pthrt pthrt.c -lpthread 
/tmp//ccd14895.o(.text+0x2c): In function `main':
: undefined reference to `pthread_getattr_np'

I don't really know much about threaded stuff, but you might want to
check the man pages for OpenBSD's pthreads library:
http://www.openbsd.org/cgi-bin/man.cgi?query=pthreads

> 
> (And interestingly, this program says that __libc_stack_end isn't
> needed on my Debian GNU/Linux, despite the comment in threads.c
> suggesting that it _is_ needed on Linux.)
> 
> Thanks,
>         Neil
> 
> 
> #include <pthread.h>
> 
> int main ()
> {
>   pthread_attr_t attr;
>   void *start, *end;
>   size_t size;
> 
>   pthread_getattr_np (pthread_self (), &attr);
>   pthread_attr_getstack (&attr, &start, &size);
>   end = (char *)start + size;
> 
>   printf("start = %p, &attr = %p, end = %p\n", start, &attr, end);
> 
>   if ((void *)&attr < start || (void *)&attr >= end)
>     printf("__libc_stack_end is needed\n");
>   else
>     printf("__libc_stack_end is NOT needed\n");
> 
>   exit (0);
> }
> 
> /* compile-command: cc -o pthrt pthrt.c -lpthread */

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm



_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2006-03-11 19:02 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
2006-03-10 23:01         ` steven mestdagh
2006-03-11 18:43           ` Neil Jerram
2006-03-11 19:02             ` steven mestdagh [this message]
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=20060311190247.GA21246@esat.kuleuven.be \
    --to=steven.mestdagh@esat.kuleuven.be \
    --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).