From: Lukasz Majewski <lukma@denx.de>
To: GNU C Library <libc-alpha@sourceware.org>
Cc: Joseph Myers <joseph@codesourcery.com>,
"Libc-help" <libc-help@sourceware.org>
Subject: Problem with build-many-glibcs.py (sparc, mips, etc)
Date: Wed, 20 May 2020 14:00:36 +0200 [thread overview]
Message-ID: <20200520140036.0ced5d60@jawa> (raw)
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
Dear Community,
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
Wed 20 May 2020 01:52:41 PM CEST
Newest master branch.
SHA1: 4c4fc04826c2e02635c65163efb1244148735c41
Have I done something wrong?
I've used:
../src/scripts/build-many-glibcs.py --replace-sources
/home/lukma/work/glibc/glibc-many-build checkout &&
../src/scripts/build-many-glibcs.py
/home/lukma/work/glibc/glibc-many-build host-libraries &&
../src/scripts/build-many-glibcs.py
/home/lukma/work/glibc/glibc-many-build compilers &&
../src/scripts/build-many-glibcs.py
/home/lukma/work/glibc/glibc-many-build glibcs
To update the setup.
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-05-20 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 12:00 Lukasz Majewski [this message]
2020-05-20 12:30 ` Florian Weimer
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=20200520140036.0ced5d60@jawa \
--to=lukma@denx.de \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-help@sourceware.org \
/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).