Just to be clear, these are both upstream commits. Is there any work
going on upstream to resolve the issue?
Currently eoan is using a kernel copied forward from disco, but we
should be putting a 5.2 kernel into eoan-proposed within the next couple
of weeks. This is likely to be before we could expect to see them in a
disco-proposed kernel, as the patch deadline for the next kernel SRU
cycle has passed.
I agree that the likelihood of regressions is slim for us, as the
changes were made only to support builds using clang. So I will go ahead
and revert these in our 5.2 tree.
I'm not sure why there's a xenial nomination here for a ftbfs in eoan
though ...
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834315
Title:
Revert x86/vdso linker changes from #1830890 as this causes glibc
2.29-0ubuntu3 FTBFS on eoan
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
In Progress
Bug description:
[Impact]
As reported in #1833067 and
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1830890/comments/7 some
glibc testcases are still regressing on i386 after applying both the following
commits:
commit 379d98ddf41344273d9718556f761420f4dc80b3
Author: Alistair Strachan <astrac...@google.com>
Date: Fri Aug 3 10:39:31 2018 -0700
x86: vdso: Use $LD instead of $CC to link
commit cd01544a268ad8ee5b1dfe42c4393f1095f86879
Author: Alistair Strachan <astrac...@google.com>
Date: Fri Dec 14 14:36:37 2018 -0800
x86/vdso: Pass --eh-frame-hdr to the linker
[Fix]
Revert both these patches to restore the original behaviour.
[Test]
ADT tests for glibc.
[Regression Potential]
Low. This restores the status quo before the original change to
vdso/x86/Makefile to restore the original linker behaviour.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834315/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
