From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] sdl: fix building on powerpc64 and powerpc64le
Date: Sun, 13 Nov 2016 18:13:18 +0100 [thread overview]
Message-ID: <eijmfdxo6o.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20161109043021.GA10982@tungsten.ozlabs.ibm.com
Am Wed, 09 Nov 2016 15:30:21 +1100 schrieb Sam Bobroff:
> How do those options sound? Any other suggestions?
Hi,
while investigating the build errors of the minidlna package
http://autobuild.buildroot.net/?reason=minidlna-1.1.5&arch=powerpc64le
I came across this discussion.
The root cause of the build error is the fact that both libexif (last
release dates 2012-07-12) and libid3tag (last release dates 2004-02-18)
contain a .m4 file which does not detect shared libs support because of
the elf64ppc/elf64lppc problem. Autoreconf'ing libexif has its own
problems wrt $MKINSTALLDIRS so I would like to avoid it.
What about doing something similar Debian did back in 2014?
https://lists.debian.org/debian-powerpc/2014/09/msg00041.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760395
Regards, Bernd
next prev parent reply other threads:[~2016-11-13 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 3:29 [Buildroot] [PATCH 1/1] sdl: fix building on powerpc64 and powerpc64le Sam Bobroff
2016-11-07 21:51 ` Thomas Petazzoni
2016-11-08 1:04 ` Arnout Vandecappelle
2016-11-08 5:10 ` Sam Bobroff
2016-11-08 12:24 ` Arnout Vandecappelle
2016-11-09 4:30 ` Sam Bobroff
2016-11-13 17:13 ` Bernd Kuhls [this message]
2016-11-13 20:18 ` Arnout Vandecappelle
2016-11-16 11:33 ` Thomas Petazzoni
2016-11-16 22:42 ` Arnout Vandecappelle
2016-11-18 0:22 ` Sam Bobroff
2016-11-16 22:49 ` Sam Bobroff
2016-11-16 22:53 ` Thomas Petazzoni
2016-11-08 3:44 ` Sam Bobroff
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=eijmfdxo6o.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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 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.