From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain/crosstool-ng: vendor part of tuple should be 'buildroot'
Date: Thu, 18 Oct 2012 00:19:27 +0200 [thread overview]
Message-ID: <507F2EEF.7060400@mind.be> (raw)
In-Reply-To: <201210172349.13982.yann.morin.1998@free.fr>
On 17/10/12 23:49, Yann E. MORIN wrote:
> On Wednesday 17 October 2012 Thomas Petazzoni wrote:
>> > Since 11017f081fc5b034e680d89eaea729c19f450e01, the Crosstool-ng
>> > backend generates toolchains that have a prefix inconsistent with what
>> > Buildroot expects. Buildroot expects a "buildroot" vendor name, while
>> > Crosstool-NG builds toolchain with the "unknown" vendor name.
>> >
>> > This is causing build failure such as:
>> >
>> > http://autobuild.buildroot.org/results/15b2c0e50a81b86dd13af684c9254df2bc0df8de/build-end.log
>> >
>> > Fix this by changing the vendor part of the tuple used by Crosstool-NG
>> > to "buildroot".
>> >
>> > Signed-off-by: Thomas Petazzoni<thomas.petazzoni@free-electrons.com>
> Acked-by: "Yann E. MORIN"<yann.morin.1998@free.fr>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
I had the very same patch lined up but forgot to commit and mail it...
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-10-17 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 21:46 [Buildroot] [PATCH] toolchain/crosstool-ng: vendor part of tuple should be 'buildroot' Thomas Petazzoni
2012-10-17 21:49 ` Yann E. MORIN
2012-10-17 22:19 ` Arnout Vandecappelle [this message]
2012-10-18 7:10 ` Peter Korsgaard
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=507F2EEF.7060400@mind.be \
--to=arnout@mind.be \
--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