Re: guile-2.0.0 fails to build without threads

[Marijn <hkBst@gentoo.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 05/05/11 14:08, Ludovic Courtès wrote:
> Hello!
> 
> Marijn <hkBst@gentoo.org> writes:
> 
>> (gdb) p &scm_protects
>> $1 = (SCM *) 0x7ffff7bc45a8
> 
> [...]
> 
>> ***Static roots:
>> From 0x601000 to 0x6010c0 (temporary)
>> From 0x7ffff7ddb000 to 0x7ffff7ddd5c8 (temporary)
>> From 0x7ffff7b9e000 to 0x7ffff7bcabb8 (temporary) ;; <- here
> 
> Hmm so GC_is_visible (&scm_protects) should definitely succeed.
> 
>>> How was libgc compiled?  Does its ‘make check’ pass?
>>
>> libgc was compiled from a gentoo ebuild and its sanity tests pass.
> 
> Which configure flags, make flags, patches, etc.?

./configure --prefix=/usr --build=x86_64-pc-linux-gnu
- --host=x86_64-pc-linux-gnu --mandir=/usr/share/man
- --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
- --localstatedir=/var/lib --libdir=/usr/lib64 --with-libatomic-ops=yes
- --enable-cplusplus --disable-threads

no make flags AFAICS, just ordinary make/make install, no patches.

> Could you try a different version of libgc?

I can try other versions, but perhaps someone on your side should
attempt to reproduce by recompiling their boehm-gc with
- --disable-threads. This bug has existed for quite some time and for
multiple guile and I assume boehm-gc versions.

>>> Can you try this program with the same libgc:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> #include <gc/gc.h>
>>>
>>> int foo[123];
>>>
>>> int
>>> main (int argc, char *argv[])
>>> {
>>>   GC_INIT ();
>>>   GC_is_visible (&foo);
>>>   return 0;
>>> }
>>> --8<---------------cut here---------------end--------------->8---
>>
>> compiled and ran your program:
>>   gcc -I/usr/include -lgc testgc.c -o testgc && ./testgc
>> there was no output.
> 
> OK.  This all sounds really fishy, and I’m pretty much clueless.
> 
> Maybe you should summarize the situation on the GC list and see whether
> we’re missing something obvious?

Please try to reproduce and then maybe we can do that.

Marijn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk3CrSYACgkQp/VmCx0OL2zo8wCgrDbFr8/wT2RlNScw3zGSPMFT
wSMAmwWP8+F7zmF2LEYorKn11Kpk8Isj
=UpZk
-----END PGP SIGNATURE-----