From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev-announce@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev-announce] Getting glibc-2.26 stable (reminder)
Date: Fri, 30 Mar 2018 19:15:16 +0200 [thread overview]
Message-ID: <4728256.M3KvIINVCW@pinacolada> (raw)
[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]
Re-sending this as a reminder...
-------------------------------------------------------------------------
Hey all,
now that upstream has already released glibc-2.27, we should think about
getting glibc-2.26 stable soon. That, however, means work for all of us.
Typical problems:
* Build failures because xlocale.h is gone
https://bugs.gentoo.org/638010
Fix: include locale.h instead
* Build failures, undefined reference to 'minor' / 'major'
https://bugs.gentoo.org/575232
Fix: additionally include sys/sysmacros.h
No, we can't delay this further; the inclusion is (finally)
also upstream gone in 2.28. Everything we fix now will for
sure save us trouble later.
* Build failures because of missing rpc support in glibc
https://bugs.gentoo.org/381391
See the following wiki page for information:
https://wiki.gentoo.org/wiki/Project:Toolchain/RPC_implementation
* Build failures because of missing NIS support
After fixing rpc support, add a dependency on net-libs/libnsl
(unconditionally).
* Some internal type definitions have changed, which may lead
to more obscure build problems (rare).
Please test and fix bugs!!!
If you want to update your otherwise stable system, please
keyword the following (otherwise you'll get blockers):
~sys-libs/glibc-2.26
=net-libs/libnsl-1*
=net-libs/rpcsvc-proto-1*
Feel free to try emerging sys-libs/glibc with FEATURES=test
(that takes a while). On amd64/x86, nearly all of the ~4000 tests succeed; I
know of the following problems:
* elf/tst-prelink-cmp fails, still needs analysis
* only with gcc-7.3.0, six tests math/test-?float128* fail (with my CFLAGS)
This is a gcc regression (miscompilation of truncf128), already submitted
upstream.
In any case, I think this still looks nice:
Summary of test results:
7 FAIL
4109 PASS
11 UNSUPPORTED
29 XFAIL
2 XPASS
Other arches may show more test failures; please file separate bugs per arch;
see https://bugs.gentoo.org/634988#c1 for what is needed for a useful report.
Stabilization tracker (fresh and largely yet empty):
https://bugs.gentoo.org/show_bug.cgi?id=glibc-2.26-stable
General issue tracker:
https://bugs.gentoo.org/show_bug.cgi?id=glibc-2.26
Cheers,
Andreas
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, perl, libreoffice, comrel)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
reply other threads:[~2018-03-30 18:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4728256.M3KvIINVCW@pinacolada \
--to=dilfridge@gentoo.org \
--cc=gentoo-dev-announce@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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