From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Libpng missing a link dependency in 2017-08?
Date: Mon, 30 Oct 2017 11:36:51 +0100 [thread overview]
Message-ID: <20171030113651.6b4bfc82@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?
Could you provide a minimal .config that exhibits the problem you're
seeing ?
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-30 10:36 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 [this message]
2017-10-31 1:53 ` Steve Kenton
2017-10-31 20:42 ` Thomas Petazzoni
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=20171030113651.6b4bfc82@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