From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-01-29
Date: Wed, 30 Jan 2019 15:17:41 +0100 [thread overview]
Message-ID: <20190130151741.4d029f0b@windsurf> (raw)
In-Reply-To: <CANQCQpaAX1mdL8e=V2uNsamy4vLNpR7AhH0H1U0k8AG+U6bMAw@mail.gmail.com>
On Wed, 30 Jan 2019 08:01:32 -0600
Matthew Weber <matthew.weber@collins.com> wrote:
> > sparc64 | host-grpc-v1.16.1 | NOK | http://autobuild.buildroot.net/results/10fd13cef3389b0c88f85572911a01279407516e |
> > arc | host-grpc-v1.16.1 | NOK | http://autobuild.buildroot.net/results/7ec686d7b73886f01fba6a8ad690e6149113aeb7 |
> > mips64el | host-grpc-v1.16.1 | NOK | http://autobuild.buildroot.net/results/a61dd5e2eda71065d2a892843d4f2ea900a6688c |
> > mipsel | host-grpc-v1.16.1 | NOK | http://autobuild.buildroot.net/results/52911efd3380bfa5e20c2e37dedb5ecbf472dde3 |
>
> The bug that's causing this failure is an artifact of the old GCC
> configuration I'm building with. I've attempted to update GCC but
> this hasn't seemed to resolve the issue like it should. Rather then
> creating a even more non-standard distro configuration, (just for this
> machine)I've added a filter in autobuild-run to drop GRPC when it gets
> selected to build.
>
> I plan to re-install soon as EOL is coming up in a couple months.
Which host gcc version are you using ? We try to support old systems,
so perhaps instead of ignoring the problem we really need to fix it
and/or work around it.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-01-30 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-01-29 Thomas Petazzoni
2019-01-30 14:01 ` Matthew Weber
2019-01-30 14:17 ` Thomas Petazzoni [this message]
2019-01-30 14:20 ` Matthew Weber
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=20190130151741.4d029f0b@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.