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] gdb: Fix compilation for arc-2018.09 in some cases
Date: Mon, 10 Dec 2018 12:15:17 +0100	[thread overview]
Message-ID: <20181210121517.6ab76211@windsurf> (raw)
In-Reply-To: <bccaa89e46d7b185a8daa109545b656bbd7db049.camel@synopsys.com>

Hello,

On Mon, 10 Dec 2018 11:09:19 +0000, Alexey Brodkin wrote:

> > Under what exact situations is this build failure happening ?  
> 
> That's a good question.
> As I wrote in my commit message it has to do with some specifics of toolchain headers
> configuration. But I'm not really sure what triggers this.
> 
> I mean I spent quite some time looking at differences between very similar build trees
> in one of which this issue happens but not in another but didn't get to any
> conclusion.
> 
> And given there's an upstream fix for that issue I didn't want to invest more time into
> this investigation, sorry.

Do you have a defconfig that fails to build ? Or is it related to the
build machine environment ?

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

  reply	other threads:[~2018-12-10 11:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10  9:35 [Buildroot] [PATCH] gdb: Fix compilation for arc-2018.09 in some cases Alexey Brodkin
2018-12-10 10:47 ` Thomas Petazzoni
2018-12-10 10:52   ` Alexey Brodkin
2018-12-10 11:03     ` Thomas Petazzoni
2018-12-10 11:09       ` Alexey Brodkin
2018-12-10 11:15         ` Thomas Petazzoni [this message]
2018-12-10 13:09           ` Alexey Brodkin

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=20181210121517.6ab76211@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