[FFe][Ubuntu 16.04] Use glibc-2.23 in Ubuntu 16.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glibc (Ubuntu) |
Fix Released
|
Medium
|
Adam Conrad |
Bug Description
Repurposing this as a Feature Freeze request bug for the glibc update. The justification for POWER is laid out below but, obviously, 2.21->2.23 brings in a lot of random minor improvements and bugfixes for all architectures, and has been requested by several different contracts.
The plan is to get it into the archive Friday evening/night at the latest, watch all the automated testing, iterate through bugfixes as necessary, and see it ship in the final beta next week.
As for the GCC feature mentioned in the original bug report, that was fixed by wschmidt and doko a few hours ago to actually work in xenial.
[Original Report]
glibc-2.23 will introduce an important ABI change for Power. It will be a prerequisite for __builtin_cpu_is() and __builtin_
The __builtin_cpu_is () / __builtin_
These gcc builtins will be disabled when the binary is built against a glibc older than 2.23, making glibc-2.23 a requirement for this feature to work.
This version of glibc will be released in early February/2016.
tags: | added: architecture-ppc64le bugnameltc-133658 severity-medium targetmilestone-inin1604 |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → glibc (Ubuntu) |
Changed in glibc (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Adam Conrad (adconrad) |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: s390x |
tags: | added: architecture-s39064 |
tags: | removed: architecture-s39064 |
summary: |
- [Ubuntu 16.04] Use glibc-2.23 in Ubuntu 16.04 + [FFe][Ubuntu 16.04] Use glibc-2.23 in Ubuntu 16.04 |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1521172/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]