From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Libpng missing a link dependency in 2017-08?
Date: Tue, 31 Oct 2017 21:42:49 +0100 [thread overview]
Message-ID: <20171031214249.7db64df4@windsurf> (raw)
In-Reply-To: <afc724e2-a455-82cd-80f8-ee329e2a3e47@ou.edu>
Hello,
On Sun, 29 Oct 2017 15:36:37 -0500, Steve Kenton wrote:
> I recently began evaluating a switch to buildroot-2017.08 and started
> getting the following message (transcribed from a screen shot)
>
> ffprobe: Relink `/usr/lib64/libpng16.so.16' with
> `/lib64/libpthread.so.0' for IFUNC symbol `longjmp'
>
> As far as I can determine it is because libpng 1.6.31 uses longjmp() and
> it needs another link dependency to avoid the runtime fixup above.
>
> I did not see anything on the list about this and buildroot 2017-08.1
> did not switch to libpng 1.6.32 although I'm building it anyway on
> general principles.
>
> So, is this likely a libpng build issue or should I start digging into?
> ffmpeg?
It seems to be a glibc issue. Very similar to the report at
https://sourceware.org/bugzilla/show_bug.cgi?id=21041, which says the
bug is fixed by
https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=fc5ad7024c620cdfe9b76e94638aac83b99c5bf8
in glibc.
However, this patch is only available in glibc's master branch. It has
not been backported to the 2.25 and 2.26 branches apparently.
It would be nice to see if the patch fixes the problem on glibc 2.25
(which Buildroot 2017.08 is using).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-31 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-29 20:36 [Buildroot] Libpng missing a link dependency in 2017-08? Steve Kenton
2017-10-29 22:56 ` Steve Kenton
2017-10-30 10:36 ` Thomas Petazzoni
2017-10-31 1:53 ` Steve Kenton
2017-10-31 20:42 ` Thomas Petazzoni [this message]
2017-10-31 22:22 ` Romain Naour
2017-11-01 1:01 ` Steve Kenton
2017-11-01 9:29 ` Thomas Petazzoni
2017-11-01 13:33 ` Romain Naour
2017-11-01 13:51 ` Steve Kenton
2017-11-01 14:07 ` Thomas Petazzoni
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=20171031214249.7db64df4@windsurf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox