From: "Binello, Severino" <sev@bnl.gov>
To: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: glibc build
Date: Tue, 26 Apr 2022 21:24:42 +0000 [thread overview]
Message-ID: <BLAPR09MB7027B80587AFA31CAAE92CE9AAFB9@BLAPR09MB7027.namprd09.prod.outlook.com> (raw)
Hello
After building glibc I run the make check
and receive the errors below
I was hoping you could point me to information that would help me interpret and evaluate the msgs
so that I can correct them.
Thanks of any assistance
Sev Binello
Brookhaven National Lab
631-344-5647
System
Building on RHEL 8
Build line
../glibc-2.28/configure CC="gcc -m32" CXX="g++ -m32" CFLAGS="-O2 -march=i686" CXXFLAGS="-O2 -march=i686" "LDFLAGS=-m32" i686-linux-gnu --enable-obsolete-rpc --disable-werror --prefix=/cfsx/usrLocals/WS/glibc-2.28/install --build=x86_64-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
UNSUPPORTED: assert/tst-assert-c++
UNSUPPORTED: assert/tst-assert-g++
XPASS: conform/UNIX98/ndbm.h/linknamespace
XPASS: conform/XOPEN2K/ndbm.h/linknamespace
XPASS: conform/XOPEN2K8/ndbm.h/linknamespace
XPASS: conform/XPG42/ndbm.h/linknamespace
FAIL: debug/tst-backtrace2
FAIL: debug/tst-backtrace3
FAIL: debug/tst-backtrace4
FAIL: debug/tst-backtrace5
FAIL: debug/tst-backtrace6
UNSUPPORTED: debug/tst-chk4
UNSUPPORTED: debug/tst-chk5
UNSUPPORTED: debug/tst-chk6
UNSUPPORTED: debug/tst-lfschk4
UNSUPPORTED: debug/tst-lfschk5
UNSUPPORTED: debug/tst-lfschk6
UNSUPPORTED: dlfcn/bug-atexit3
FAIL: elf/check-abi-libc
XPASS: elf/tst-protected1a
XPASS: elf/tst-protected1b
FAIL: grp/testgrp
FAIL: inet/tst-idna_name_classify
FAIL: io/ftwtest
UNSUPPORTED: io/tst-fallocate
UNSUPPORTED: io/tst-fallocate64
FAIL: malloc/tst-malloc-stats-cancellation
FAIL: misc/check-installed-headers-c
FAIL: nptl/tst-basic3
FAIL: nptl/tst-basic4
FAIL: nptl/tst-call-once
FAIL: nptl/tst-cancel-self
FAIL: nptl/tst-cancel-self-cancelstate
FAIL: nptl/tst-cancel-self-canceltype
FAIL: nptl/tst-cancel-self-testcancel
FAIL: nptl/tst-cancel1
FAIL: nptl/tst-cancel10
FAIL: nptl/tst-cancel11
FAIL: nptl/tst-cancel12
FAIL: nptl/tst-cancel13
FAIL: nptl/tst-cancel14
FAIL: nptl/tst-cancel15
FAIL: nptl/tst-cancel16
FAIL: nptl/tst-cancel17
FAIL: nptl/tst-cancel18
FAIL: nptl/tst-cancel2
FAIL: nptl/tst-cancel20
FAIL: nptl/tst-cancel21
FAIL: nptl/tst-cancel22
next reply other threads:[~2022-04-26 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 21:24 Binello, Severino [this message]
2022-04-27 6: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=BLAPR09MB7027B80587AFA31CAAE92CE9AAFB9@BLAPR09MB7027.namprd09.prod.outlook.com \
--to=sev@bnl.gov \
--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).