From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next] util-linux: fix build for SPARC
Date: Fri, 23 Nov 2018 10:47:14 +0100 [thread overview]
Message-ID: <20181123104714.7300215f@windsurf> (raw)
In-Reply-To: <20181122115930.21278-1-casantos@datacom.com.br>
Hello,
On Thu, 22 Nov 2018 09:59:30 -0200, Carlos Santos wrote:
> Pull a patch already applied upstream that fixes the build of setarch
> for SPARC processors.
>
> Fixes:
> http://autobuild.buildroot.net/results/44d0538332499cea691a381048562a09cda23624
> http://autobuild.buildroot.net/results/e7e3469717ab27d66d2528087fd7c3a41477ae05
>
> Signed-off-by: Carlos Santos <casantos@datacom.com.br>
> ---
> ...-setarch-fix-obscure-sparc32bash-use-case.patch | 83 ++++++++++++++++++++++
> 1 file changed, 83 insertions(+)
> create mode 100644 package/util-linux/0003-setarch-fix-obscure-sparc32bash-use-case.patch
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-11-23 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 11:59 [Buildroot] [PATCH next] util-linux: fix build for SPARC Carlos Santos
2018-11-23 9:47 ` 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=20181123104714.7300215f@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