Closed yihuajack closed 2 years ago
Is libgc
statically linked in this context?
I'm not sure whether it is caused by libgc
... it seems that libgc
is not linked in the Makefile
.
libgc
will get pulled indirectly through libguile
. The symbol GC_thread_key
looks like it'd belong to it and libgc.a
very much looks like it's being linked statically. That won't work for a dynamic library like Guile-GI, but I wonder how you even got Guile to link (doesn't Guile itself already try to build a shared object?).
I see what you mean. I think the possible reason is that to "fix" the broken guile
, I previously use bdwgc
to replace libgc
(maybe libgc
has been corrupted before).
Check whether Guile's pkg-config file correctly pulls in bdwgc
instead of libgc
and that you're using the "fixed" Guile during configure.
Closing for lack of response. Feel free to reopen if you still need help with this.
System: WSL 1 Ubuntu 20.04 LTS
libgc
is manually built from latest source. The output ofsudo make test
:The output of
sudo make
is attached here: guile-gi.txt