From: Lee Mracek <lee.mracek@uber.com>
To: libc-help@sourceware.org
Cc: carlos@systemhalted.org
Subject: GLIBC 2.25 and up test failures listed on wiki
Date: Tue, 11 Jun 2019 20:47:00 -0000 [thread overview]
Message-ID: <CALQeLk3uagYsdQb8DfRfuGDujaVHTxQyMsU1k5YL30GP8jEBwg@mail.gmail.com> (raw)
While building GLIBC I've been running into the issues with
test-cond-printers, etc as listed in the architecture-independent section
of https://sourceware.org/glibc/wiki/Release/2.25. Since I am sure that
Python is in my path, I'm assuming that this is due to the potential cause
added to the wiki regarding "gcc 7.8 or newer" but I'd like to confirm that.
Currently my error presents as an unexpected output, and running the binary
itself doesn't provide any information. I can provide a full log if
necessary to compare.
Furthermore, I'm wondering what changed in gcc 7.8 to make this test pass.
I'd love to deeply understand what is going on before I deploy a glibc that
is failing unit tests.
Regards,
Lee Mracek
next reply other threads:[~2019-06-11 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 20:47 Lee Mracek [this message]
2019-06-11 20:54 ` Carlos O'Donell
2019-06-11 21:00 ` 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=CALQeLk3uagYsdQb8DfRfuGDujaVHTxQyMsU1k5YL30GP8jEBwg@mail.gmail.com \
--to=lee.mracek@uber.com \
--cc=carlos@systemhalted.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).