From: Florian Weimer <fweimer@redhat.com>
To: Vincent Lefevre <vincent@vinc17.net>
Cc: libc-alpha@sourceware.org
Subject: Re: "make check" on git master fails with 175 FAIL and leaves processes behind on Debian/unstable
Date: Wed, 22 Feb 2023 17:58:57 +0100 [thread overview]
Message-ID: <87y1opskku.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20230222153821.GA1343217@cventin.lip.ens-lyon.fr> (Vincent Lefevre's message of "Wed, 22 Feb 2023 16:38:21 +0100")
* Vincent Lefevre:
> On 2023-02-22 10:10:31 -0500, Carlos O'Donell via Libc-alpha wrote:
>> On 2/22/23 09:56, Vincent Lefevre wrote:
>> > I did
>> >
>> > mkdir glibc-build
>> > cd glibc-build
>> > ../glibc/configure --prefix=$HOME/opt/glibc
>>
>> Please review:
>> https://sourceware.org/glibc/wiki/Testing/Builds#Testing_a_glibc_build
>>
>> If you use a unique --prefix, that is an ABI change, and it will require
>> you to have everything required under that path as-if it was a sysroot.
>
> I'll test it again with --prefix=/usr, but IMHO, the INSTALL file
> should clarify this point. I assumed that --prefix=/usr was
> recommended for the case where the GNU C Library would be installed
> as a replacement, not just for testing a new glibc. Moreover,
> I would have thought that --prefix would not have any influence
> for "make check" (as --prefix is related to the installation,
> while "make check" occurs before installation).
We have tests for unwinding facilities, and those need libgcc_s. (Some
of the C++ tests need libstdc++ as well.) If the required shared
objects are not available under the --prefix= directory (or copied
manually into the glibc build directories), these tests will fail.
Thanks,
Florian
next prev parent reply other threads:[~2023-02-22 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 14:56 Vincent Lefevre
2023-02-22 15:10 ` Carlos O'Donell
2023-02-22 15:38 ` Vincent Lefevre
2023-02-22 16:58 ` Florian Weimer [this message]
2023-02-22 17:04 ` Vincent Lefevre
2023-02-22 20:00 ` Adhemerval Zanella Netto
2023-02-23 14:00 ` Vincent Lefevre
2023-02-22 15:24 ` Andreas Schwab
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=87y1opskku.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=vincent@vinc17.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).