From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openblas: fix build with musl libc
Date: Wed, 25 Apr 2018 23:02:25 +0200 [thread overview]
Message-ID: <20180425230225.70be6ff2@windsurf> (raw)
In-Reply-To: <dbeb63928c8d303e263ff75475d99a82b6bfa2e4.1523980616.git.baruch@tkos.co.il>
Hello,
On Tue, 17 Apr 2018 18:56:56 +0300, Baruch Siach wrote:
> Add upstream patches to avoid use of __GLIBC_PREREQ when this macro is
> not defined.
>
> Fixes:
> http://autobuild.buildroot.net/results/f13/f13d93372449c9bf1b3c79ed056b8d820470ae89/
> http://autobuild.buildroot.net/results/e1c/e1cdcdfe15b4af523c7db71952ac25163733ffb1/
> http://autobuild.buildroot.net/results/778/77821a4a37171080fc7ee917862e77babeb06b88/
>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> ...REREQ-checks-to-avoid-breaking-non-g.patch | 73 +++++++++++++++++++
> ...d-when-__GLIBC_PREREQ-is-not-defined.patch | 45 ++++++++++++
> 2 files changed, 118 insertions(+)
> create mode 100644 package/openblas/0002-Rework-__GLIBC_PREREQ-checks-to-avoid-breaking-non-g.patch
> create mode 100644 package/openblas/0003-Fix-build-when-__GLIBC_PREREQ-is-not-defined.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-04-25 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 15:56 [Buildroot] [PATCH] openblas: fix build with musl libc Baruch Siach
2018-04-25 21:02 ` Thomas Petazzoni [this message]
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=20180425230225.70be6ff2@windsurf \
--to=thomas.petazzoni@bootlin.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