From: John Darrington <john@darrington.wattle.id.au>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add LDFLAGS=-lpthread to configure-flags where needed.
Date: Tue, 21 Mar 2017 13:15:53 +0100 [thread overview]
Message-ID: <20170321121553.GB13334@jocasta.intra> (raw)
In-Reply-To: <20170321122905.64b408a6@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]
On Tue, Mar 21, 2017 at 12:29:05PM +0100, Danny Milosavljevic wrote:
Hi John,
thanks for looking into the problem.
On Tue, 21 Mar 2017 02:22:11 +0100
John Darrington <john@darrington.wattle.id.au> wrote:
> + (arguments `(#:configure-flags '("LDFLAGS=-lpthread")))
Hmm, that seems to be a very unsafe thing to do.
I was afraid you might say that.
In order to actually use pthread, one has to switch gcc into pthread mode (which influences how it handles variables etc).
But just passing "-lpthread" to the linker does no such things and will only make it link - with the wrong actual instructions in the object files!
It used to work. Only recently has it stopped working.
So that would seem to confirm to me that a version of gcc (or some other part of
the tool chain) recently checked into core-updates might have been misconfigured.
Is it possible that somehow pthread mode has been inadvertently switched on?
It would be better to check out the object files (with objdump -r or objdump -t) and find out where the symbol is listed as undefined ("U"). Then check the associated source file whether it actually intended to use pthread.
I'm not familiar enough with the internals to know exactly which source file
would be involved. But the error message clearly says to relink libpng and libfontconfig
using -lpthread. I just did as told.
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-03-21 12:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 1:22 For core-updates John Darrington
2017-03-21 1:22 ` [PATCH] gnu: Add LDFLAGS=-lpthread to configure-flags where needed John Darrington
2017-03-21 1:37 ` Leo Famulari
2017-03-21 9:09 ` Sergei Trofimovich
2017-03-21 9:17 ` John Darrington
2017-03-21 22:42 ` Sergei Trofimovich
2017-03-21 23:07 ` Sergei Trofimovich
2017-03-21 11:29 ` Danny Milosavljevic
2017-03-21 12:15 ` John Darrington [this message]
2017-03-21 18:52 ` Danny Milosavljevic
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170321121553.GB13334@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=dannym@scratchpost.org \
--cc=guix-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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).