From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-05
Date: Mon, 7 Nov 2016 09:28:36 +0100 [thread overview]
Message-ID: <20161107092836.17506e71@free-electrons.com> (raw)
In-Reply-To: <20161107041234.GA31219@tungsten.ozlabs.ibm.com>
Hello,
On Mon, 7 Nov 2016 15:12:34 +1100, Sam Bobroff wrote:
> This seems to be similar to some others: a library (libXcursor) is being
> incorrectly built as static, which causes downstream link failures. I
> had a quick look at other X11R7 libraries and they all seem to include
> the same old version of autotools that can't detect dynamic linker
> support on powerpc64le.
>
> Before I go and fix every one manually: is there some better way to
> handle this across many packages, or even just many X11R7 packages?
>
> Should I prepare one big patch that fixes them all?
What is the fix that needs to be done exactly?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-07 8:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-05 Thomas Petazzoni
2016-11-06 13:39 ` Yegor Yefremov
2016-11-06 14:08 ` Thomas Petazzoni
2016-11-06 14:06 ` Thomas Petazzoni
2016-11-06 15:42 ` [Buildroot] -mcpu=native [was: Re: [autobuild.buildroot.net] Build results for 2016-11-05] Arnout Vandecappelle
2016-11-06 19:33 ` [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-05 Waldemar Brodkorb
2016-11-06 21:22 ` Thomas Petazzoni
2016-11-06 22:48 ` Sam Bobroff
2016-11-11 20:41 ` Thomas Petazzoni
2016-11-07 4:12 ` Sam Bobroff
2016-11-07 8:28 ` Thomas Petazzoni [this message]
2016-11-07 18:25 ` Waldemar Brodkorb
2016-11-07 20:53 ` 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=20161107092836.17506e71@free-electrons.com \
--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