Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] valgrind: fix mips64 compile
Date: Fri, 9 Nov 2018 11:55:56 +0100	[thread overview]
Message-ID: <20181109115556.424971fe@windsurf> (raw)
In-Reply-To: <20181108230814.4773-1-ps.report@gmx.net>

Hello,

On Fri,  9 Nov 2018 00:08:14 +0100, Peter Seiderer wrote:
> Disable gcc march mips64r2 detection (use compile flags already
> set by buildroot only), avoids double setting like '-march=mips64
> ... -march=mips64r2 -mabi=64'.
> 
> Fixes [1]:
> 
>   error: '-mips64r2' conflicts with the other architecture options, which specify a mips64 processor
> 
> [1] http://autobuild.buildroot.net/results/34f6e2352f1559f98c724fe5394db0035b42ddb1
> 
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>

Thanks for this patch. Could we find something acceptable upstream? Why
is valgrind configure script enforcing those CFLAGS ?

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-11-09 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 23:08 [Buildroot] [PATCH v1] valgrind: fix mips64 compile Peter Seiderer
2018-11-09 10:55 ` Thomas Petazzoni [this message]
2018-11-12 18:41   ` Peter Seiderer
2018-11-28 14:28 ` Thomas Petazzoni

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=20181109115556.424971fe@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