From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2017-07-08
Date: Mon, 10 Jul 2017 20:54:52 +0200 [thread overview]
Message-ID: <20170710185452.GA22803@waldemar-brodkorb.de> (raw)
In-Reply-To: <87lgnwtoth.fsf@dell.be.48ers.dk>
Hi Peter,
Peter Korsgaard wrote,
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>
> Hi,
>
> >> > Build failures related to your packages:
> >> >
> >> > mips64el | host-util-linux-2.30 |
> >> > http://autobuild.buildroot.net/results/a0096eb6e65b83b2b0c7d38e5f978c3fe636cb30
> >>
> >> Segfault in /bin/bash. Does not seem to be related to the package.
>
> > This is happening on Peter's autobuilder instance. It failed twice:
> > http://autobuild.buildroot.net/?reason=host-util-linux-2.30. One time
> > due to an Illegal instruction, second time due to a Segmentation fault.
>
> > Peter ? :-)
>
> Sorry, no idea. gcc68 is a new Ryzen based machine in the compile farm
> that I recently started an autobuilder instance on:
>
> https://cfarm.tetaneutral.net/machines/list/
>
> I'll try to reproduce manually and have a closer look tonight.
I have seen a lot of illegal instruction errors from the host gcc
on this machine. (also on gcc67).
Dunno if the Debian is too old or what is the reason.
So the problems are not specific to buildroot.
best regards
Waldemar
next prev parent reply other threads:[~2017-07-10 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170709063052.6F78221DB3@mail.free-electrons.com>
2017-07-10 12:30 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-07-08 Carlos Santos
2017-07-10 12:43 ` Thomas Petazzoni
2017-07-10 13:16 ` Peter Korsgaard
2017-07-10 13:29 ` Wolfgang Grandegger
2017-07-10 18:54 ` Waldemar Brodkorb [this message]
2017-07-10 21:49 ` Thomas Petazzoni
2017-07-11 11:53 ` Thomas Petazzoni
2017-07-11 12:19 ` Peter Korsgaard
2017-07-11 20:59 ` Yann E. MORIN
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=20170710185452.GA22803@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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