From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/gcc: fix ARC failure to build in 2 phases.
Date: Thu, 2 Jul 2015 07:46:12 +0000 [thread overview]
Message-ID: <1435823172.2966.25.camel@synopsys.com> (raw)
In-Reply-To: <20150629174920.10f52a00@free-electrons.com>
Hi Thomas, Tal,
On Mon, 2015-06-29 at 17:49 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Mon, 29 Jun 2015 15:39:12 +0000, Tal Zilcer wrote:
>
> > We have one source tree for both build phases of GCC.
> > First phase must have this patch while second phase must NOT have
> > it.
> > it doesn't seems reasonable to have two GCC source trees because of
> > this patch.
>
> Ah right. I think there's probably a way to write the change so that
> it
> does not try to use these object files during the initial gcc build.
> This is really what the real fix is.
>
> > > In any case, I don't think it's worth the effort making that
> > > conditional, just register the post-rsync hook unconditionally.
> > It is only to explain our intentions, do you prefer a comment or
> > just to add the RSYNC hook?
>
> For now, we can just add the rsync hook, but...
>
> > > BTW, this problem should have been sorted out by the ARC
> > > developers, maybe you should ping them about this?
> > Adding Alexey to this correspondence
>
> ... I'd like to hear from Alexey about this, since I reported this
> issue a while ago now.
Please pardon my late reply was super busy with internal activities.
As for known problem of gmon that includes libc headers unfortunately
nothing has been done on that front. That's because we have a
workaround with disabling libgmon in Buildroot.
I'll ping our gcc guy but I don't think things will change soon here
again because it doesn't look as a blocker.
So probably rsync hook is a way to go for now.
-Alexey
prev parent reply other threads:[~2015-07-02 7:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-29 12:50 [Buildroot] [PATCH 1/2] package/gcc: fix ARC failure to build in 2 phases Tal Zilcer
2015-06-29 12:50 ` [Buildroot] [PATCH 2/2] package/pkg-kconfig: define KCONFIG_EDITORS_MAKE_ENV Tal Zilcer
2015-07-02 7:44 ` Alexey Brodkin
2015-07-02 7:52 ` Thomas Petazzoni
2015-07-02 7:56 ` Alexey Brodkin
2015-06-29 14:29 ` [Buildroot] [PATCH 1/2] package/gcc: fix ARC failure to build in 2 phases Thomas Petazzoni
2015-06-29 15:39 ` Tal Zilcer
2015-06-29 15:49 ` Thomas Petazzoni
2015-07-02 7:46 ` Alexey Brodkin [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=1435823172.2966.25.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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