From: Florian Weimer <fweimer@redhat.com>
To: Lukasz Majewski <lukma@denx.de>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Libc-help <libc-help@sourceware.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: Problem with build-many-glibcs.py (sparc, mips, etc)
Date: Wed, 20 May 2020 14:30:01 +0200 [thread overview]
Message-ID: <87ftbubxh2.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20200520140036.0ced5d60@jawa> (Lukasz Majewski's message of "Wed, 20 May 2020 14:00:36 +0200")
* Lukasz Majewski:
> Recently, when using build-many-glibcs.py, I've noticed many errors
> with "check-compilers" task:
>
> For example - in
> /glibc-many-build/logs/glibcs/sparc64-linux-gnu/000-glibcs-sparc64-linux-gnu-check-compilers-log.txt
>
> Description: glibcs-sparc64-linux-gnu check-compilers
> Command: test -f
> /home/lukma/work/glibc/glibc-many-build/install/compilers/sparc64-linux-gnu/ok
> Directory: Path addition:
>
>
> FAIL: glibcs-sparc64-linux-gnu check-compilers
You need to look for errors from the compilers stage. Probably
something went wrong building sparc64 toolchain components.
Thanks,
Florian
prev parent reply other threads:[~2020-05-20 12:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 12:00 Lukasz Majewski
2020-05-20 12:30 ` Florian Weimer [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=87ftbubxh2.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-help@sourceware.org \
--cc=lukma@denx.de \
/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).