From: Sergei Trofimovich <slyfox@inbox.ru>
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add LDFLAGS=-lpthread to configure-flags where needed.
Date: Tue, 21 Mar 2017 09:09:28 +0000 [thread overview]
Message-ID: <20170321090928.02b12da9@sf> (raw)
In-Reply-To: <1490059331-32049-2-git-send-email-john@darrington.wattle.id.au>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
On Tue, 21 Mar 2017 02:22:11 +0100
John Darrington <john@darrington.wattle.id.au> wrote:
> --- a/gnu/packages/image.scm
> +++ b/gnu/packages/image.scm
> @@ -80,6 +80,8 @@
> (sha256
> (base32 "0ylgyx93hnk38haqrh8prd3ax5ngzwvjqw5cxw7p9nxmwsfyrlyq"))))
> (build-system gnu-build-system)
> + (arguments
> + `(#:configure-flags '("LDFLAGS=-lpthread")))
That's libpng-1.6.28, right? I've tried to reproduce the failure on current
'core-updates' master (x86_64-linux). It builds just fine:
$ git describe
v0.12.0-2306-gf826c8c7e
$ ./pre-inst-env guix build libpng --check --no-grafts -K
/gnu/store/vis7x2j2lsmwbl5m5w794c23ysqah8xh-libpng-1.6.28
At a glance source code of libpng and it's tests does not contain any pthread calls.
Do you have a build log with the failure? I wonder where missing symbols come from.
--
Sergei
[-- Attachment #2: Цифровая подпись OpenPGP --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2017-03-21 9:09 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170321090928.02b12da9@sf \
--to=slyfox@inbox.ru \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.