guile-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Incorrect guile pkg-config --libs and --cflags


From: Mark H Weaver
Subject: Re: Incorrect guile pkg-config --libs and --cflags
Date: Wed, 24 Apr 2013 03:21:49 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

Daniel Hartwig <address@hidden> writes:

> On 15 April 2013 19:58, Daniel Hartwig <address@hidden> wrote:
>> or peculiar to the linker, libguile on your system, other?
>
> I see that this is related to the linker in fedora, which debian seems
> also in the process of supporting.  Indirect linkage like this is out
> (apparently), and LIBS should properly include -pthread option.
>
> <https://fedoraproject.org/wiki/UnderstandingDSOLinkChange>
> <http://wiki.debian.org/ToolChain/DSOLinking#Not_resolving_symbols_in_indirect_dependent_shared_libraries>

FWIW, I've observed that on my Debian Wheezy system, almost all of the
*.pc files that include "-pthread" in Cflags also include it in Libs.

In the relevant bug report
<https://bugzilla.redhat.com/show_bug.cgi?id=951781>, Sebastian Freundt
claims that linking "any trivial test file test.c" against libguile
(1.8) fails on Fedora 18 unless -pthread is used during linking.

Apparently this is the case even if the main program does not directly
use the pthread API.  I confess that I don't understand the reason for
this, but if it's true, I'm inclined to believe that either we should
add -pthread to the pkg-config Libs, or that perhaps this is a bug in
the toolchain.  One way or another, $(pkg-config --libs guile-*) should
provide what is needed to link a minimal test program with guile.

I've taken the liberty of adding Sebastian to the CC list, since he
already expressed an interest in raising this issue with upstream.
Perhaps he can shed some light on this issue.

     Regards,
       Mark



reply via email to

[Prev in Thread] Current Thread [Next in Thread]