From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-06-29
Date: Sat, 30 Jun 2018 21:12:16 +0200 [thread overview]
Message-ID: <20180630211216.193bca6b@windsurf.home> (raw)
In-Reply-To: <f38c57af-44a3-2766-2512-1f0e9f4f4f98@gmail.com>
Hello,
On Sat, 30 Jun 2018 20:30:44 +0200, Romain Naour wrote:
> > arm | host-llvm-6.0.0 | NOK | http://autobuild.buildroot.net/results/84222a111d7a4cecb14f9fb280ff5763d61ed592 |
> > x86_64 | host-llvm-6.0.0 | NOK | http://autobuild.buildroot.net/results/d9265c7a1f9d6568d0a187dc52a08168e1954c91 |
>
> It seems that gcc 8.1.1 from the host (ArchLinux) is buggy, there is no such
> error with a Fedora 28 with gcc 8 installed.
>
> 1)
> /usr/include/c++/8.1.1/type_traits:1054:12: internal compiler error:
> Segmentation fault
> struct is_nothrow_move_constructible
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <https://bugs.archlinux.org/> for instructions.
>
> 2)
>
> /home/joseph/buildroot-test/instance-13/output/build/host-llvm-6.0.0/include/llvm/ADT/MapVector.h:104:3:
> internal compiler error: Segmentation fault
> }
> ^
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <https://bugs.archlinux.org/> for instructions.
Thanks Romain for the analysis. Joseph, could you bring this up to the
Archlinux maintainers ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-06-30 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-06-29 Thomas Petazzoni
2018-06-30 18:30 ` Romain Naour
2018-06-30 19:12 ` Thomas Petazzoni [this message]
2018-06-30 19:17 ` Joseph Kogut
2018-06-30 19:21 ` Thomas Petazzoni
2018-06-30 19:28 ` Joseph Kogut
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=20180630211216.193bca6b@windsurf.home \
--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