From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Martin Sebor via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: tests failing on x86_64-linux
Date: Wed, 09 Dec 2020 20:03:36 +0100 [thread overview]
Message-ID: <87k0tq4x9z.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <011327e1-276d-7ea5-460e-7838f94ee4c9@gmail.com> (Martin Sebor via Libc-alpha's message of "Wed, 9 Dec 2020 11:17:22 -0700")
* Martin Sebor via Libc-alpha:
> I've been seeing quite a few test failures in recent builds, more
> than I used to in the past. Are those expected? I configure with
> no options other than --prefix=/usr and after building without
> installing (i.e., just make -j16) run make -j16 check.
You have likely configured glibc without --prefix=/usr. As a result,
the default search path does not include /usr/lib64, and required GCC
components cannot be found.
Maybe we should just default to that prefix (and the appropriate prefix
for Hurd). It's a common trap.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
prev parent reply other threads:[~2020-12-09 19:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 18:17 tests failing on x86_64-linux Martin Sebor via Libc-alpha
2020-12-09 18:28 ` H.J. Lu via Libc-alpha
2020-12-09 21:17 ` Martin Sebor via Libc-alpha
2020-12-09 21:44 ` H.J. Lu via Libc-alpha
2020-12-09 22:31 ` H.J. Lu via Libc-alpha
2020-12-10 2:50 ` H.J. Lu via Libc-alpha
2020-12-15 0:55 ` Martin Sebor via Libc-alpha
2021-04-28 20:07 ` tests failing on x86_64-linux (due to test-container?) Martin Sebor via Libc-alpha
2021-04-28 20:37 ` DJ Delorie via Libc-alpha
2021-04-28 21:50 ` Martin Sebor via Libc-alpha
2021-04-28 23:08 ` DJ Delorie via Libc-alpha
2021-04-28 23:42 ` Martin Sebor via Libc-alpha
2021-04-28 23:54 ` DJ Delorie via Libc-alpha
2021-05-13 21:29 ` Martin Sebor via Libc-alpha
2022-01-12 22:04 ` Martin Sebor via Libc-alpha
2022-01-12 22:13 ` H.J. Lu via Libc-alpha
2022-01-12 23:24 ` Martin Sebor via Libc-alpha
2022-01-14 23:51 ` Martin Sebor via Libc-alpha
2022-01-17 18:04 ` Adhemerval Zanella via Libc-alpha
2022-01-17 19:09 ` Joseph Myers
2022-01-20 22:23 ` Martin Sebor via Libc-alpha
2020-12-16 10:21 ` tests failing on x86_64-linux Florian Weimer via Libc-alpha
2020-12-09 19:03 ` Florian Weimer via Libc-alpha [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0tq4x9z.fsf@oldenburg2.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.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).