From: Mason <slash.tmp@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-01-14
Date: Sun, 17 Jan 2016 10:05:42 +0100 [thread overview]
Message-ID: <569B5966.5080706@free.fr> (raw)
In-Reply-To: <7mqqmcx6cr.ln2@ID-313208.user.individual.net>
On 16/01/2016 22:52, Bernd Kuhls wrote:
> Am Sat, 16 Jan 2016 22:16:47 +0100 schrieb Arnout Vandecappelle:
>
>> On 16-01-16 11:34, Bernd Kuhls wrote:
>>
>>> the reason for this build error is a arc-only gcc bug which was fixed in
>>> gcc-4.9: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59049
>>>
>>> The toolchain used by the autobuilders is gcc-4.8 which explains the
>>> build error. Afaics Kconfig does not allow something like this:
>>>
>>> depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_9 if BR2_arc
>>>
>>> Could you please give me some advise on how to fix the problem?
>>
>> Apply logic. FOO if BAR is the same as FOO || !BAR.
>
> Hi Arnout,
>
> this would mean that the package is blocked on BR2_arc, regardless of the
> toolchain used there, and all other archs need gcc-4.9+, right?
> If yes, then this is not what I want to achieve. The package works with
> all buildroot-supported gcc versions on all archs _except_ that it is
> broken on arc with gcc-4.8 or older, gcc bug 59049 is arc-only.
Arnout is suggesting:
depends on !BR2_arc || BR2_TOOLCHAIN_GCC_AT_LEAST_4_9
This equivalence is called "material implication".
https://en.wikipedia.org/wiki/Material_implication_%28rule_of_inference%29
Reading more closely, are you saying the build is broken
on ARC if gcc version >= 4.8 ? Or is gcc version <= 4.8 ?
Regards.
next prev parent reply other threads:[~2016-01-17 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-01-14 Thomas Petazzoni
2016-01-16 10:34 ` Bernd Kuhls
2016-01-16 21:16 ` Arnout Vandecappelle
2016-01-16 21:52 ` Bernd Kuhls
2016-01-17 9:05 ` Mason [this message]
2016-01-17 11:44 ` Bernd Kuhls
2016-01-17 13:05 ` Mason
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=569B5966.5080706@free.fr \
--to=slash.tmp@free.fr \
--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