From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] toolchain-external: Fix EABIhf check
Date: Fri, 09 May 2014 21:53:39 +0200 [thread overview]
Message-ID: <536D3243.9090704@mind.be> (raw)
In-Reply-To: <CAAXf6LUActiMzXEXGqUJDkmrGhb_LXNaf1=Ca+A16PurGRBuBQ@mail.gmail.com>
On 09/05/14 09:23, Thomas De Schampheleire wrote:
> Hi Arnout,
>
> On Fri, May 9, 2014 at 12:35 AM, Arnout Vandecappelle <arnout@mind.be> wrote:
>> On 06/05/14 13:25, Thomas De Schampheleire wrote:
[snip]
>>
>>> + abistr_$(BR2_ARM_EABI)='EABI'; \
>>> + abistr_$(BR2_ARM_EABIHF)='EABIhf'; \
>>> + echo "Incorrect ABI setting: $${abistr_y} selected, but toolchain is incompatible"; \
>>
>> Nice approach! But to keep the original output, you could use:
>>
>> $${abistr_y} selected, but toolchain uses $${abistr_}
>>
>
> This did cross my mind, but it assumes that there are only two
> possibilities: EABI and EABIhf. Suppose that a new EABI pops up. Or
> suppose the compilation/link step fails for a completely different
> reason. Then we have told the user that their toolchain is EABI or
> EABIhf while it is not true.
> So here I choice correctness over completeness, but if you prefer I
> can change it. Do let me know if you still think we should add
> $${abistr_} to the message.
Good point, let's say "incompatible" then.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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
prev parent reply other threads:[~2014-05-09 19:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 11:25 [Buildroot] [PATCH v3] toolchain-external: Fix EABIhf check Thomas De Schampheleire
2014-05-08 22:35 ` Arnout Vandecappelle
2014-05-09 7:23 ` Thomas De Schampheleire
2014-05-09 19:53 ` Arnout Vandecappelle [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=536D3243.9090704@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 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.