From: Mark Wielaard <mark@klomp.org>
To: Christophe Lyon <christophe.lyon@arm.com>
Cc: buildbot@sourceware.org
Subject: Re: Arm GCC buildbot workers
Date: Fri, 12 Aug 2022 18:44:15 +0200 [thread overview]
Message-ID: <20220812164415.GI5520@gnu.wildebeest.org> (raw)
In-Reply-To: <b14c1554-0c72-ac65-2e57-276af3511542@arm.com>
Hi Christophe,
On Fri, Aug 12, 2022 at 09:23:36AM +0200, Christophe Lyon wrote:
> >ubuntu22_04-arm64
> >ubuntu22_04-armhf
> >
> >See the attached patch.
>
> Thanks, LGTM, the 2 new workers are now running.
The ubuntu22_04-arm64 worker seems to happily do full gcc bootstrap
and check builds:
https://builder.sourceware.org/buildbot/#/workers/34
It does find a couple of failing testcases, which you might want to
look at, but most seem expected. All results are recorded in bunsen to
be compared.
The ubuntu22_04-armhf worker however fails to do a full gcc build:
https://builder.sourceware.org/buildbot/#/workers/33
In file included from ../../../gcc/libgcc/../gcc/tsystem.h:87,
from ../../../gcc/libgcc/libgcc2.c:27:
/usr/include/stdio.h:27:10: fatal error: bits/libc-header-start.h: No such file or directory
27 | #include <bits/libc-header-start.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
It looks like that happens while building libcc for
armv8l-unknown-linux-gnueabihf. Maybe missing devel header files? Or
does the build needs to be configured to exclude this target?
Cheers,
Mark
next prev parent reply other threads:[~2022-08-12 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 7:54 Christophe Lyon
2022-08-11 20:39 ` Mark Wielaard
2022-08-12 7:23 ` Christophe Lyon
2022-08-12 16:44 ` Mark Wielaard [this message]
2022-08-16 11:54 ` Christophe Lyon
2022-08-17 11:51 ` Christophe Lyon
2022-08-17 13:00 ` Mark Wielaard
2022-08-17 13:45 ` Christophe Lyon
2022-08-17 20:42 ` Mark Wielaard
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=20220812164415.GI5520@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=buildbot@sourceware.org \
--cc=christophe.lyon@arm.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).