From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] valgrind: disable for MIPS soft-float
Date: Mon, 23 May 2016 12:58:28 +0100 [thread overview]
Message-ID: <5742F064.5010300@imgtec.com> (raw)
In-Reply-To: <20160523135515.0bc85032@free-electrons.com>
Hi Thomas,
On 23/05/16 12:55, Thomas Petazzoni wrote:
> Hello,
>
> On Mon, 23 May 2016 12:31:51 +0100, Vicente Olivert Riera wrote:
>
>> diff --git a/package/valgrind/Config.in b/package/valgrind/Config.in
>> index 21b2608..40e219d 100644
>> --- a/package/valgrind/Config.in
>> +++ b/package/valgrind/Config.in
>> @@ -8,6 +8,7 @@ config BR2_PACKAGE_VALGRIND
>> BR2_powerpc || BR2_powerpc64 || BR2_powerpc64le || \
>> BR2_x86_64
>> depends on !BR2_STATIC_LIBS
>> + depends on !BR2_MIPS_SOFT_FLOAT
>
> I am wondering if it isn't better to do:
>
> depends on BR2_ARM_CPU_ARMV7A || BR2_i386 || \
> - BR2_mips || BR2_mipsel || BR2_mips64 || BR2_mips64el || \
> + ((BR2_mips || BR2_mipsel || BR2_mips64 || BR2_mips64el) && !BR2_MIPS_SOFT_FLOAT) || \
> BR2_powerpc || BR2_powerpc64 || BR2_powerpc64le || \
> BR2_x86_64
>
> But I'm not sure. It's completely equivalent from a functionality point
> of view, I'm just wondering which one is more logical.
I prefer mine.
We have architecture support in one block, and features support in
another one. More readable IMHO.
Anyway, you can commit whichever you want as at the end of the day they
will have the same functionality.
Regards,
Vincent.
> Thomas
>
next prev parent reply other threads:[~2016-05-23 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 11:31 [Buildroot] [PATCH] valgrind: disable for MIPS soft-float Vicente Olivert Riera
2016-05-23 11:55 ` Thomas Petazzoni
2016-05-23 11:58 ` Vicente Olivert Riera [this message]
2016-05-24 11:16 ` 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=5742F064.5010300@imgtec.com \
--to=vincent.riera@imgtec.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