[opensuse-factory] Binutils 2.31
Adrian, In binutils 2.31, relocation type R_X86_64_PLT32 for 32-bit PC-relative branches has been enabled. With this change, VirtualBox VMs fail to start. The kernel fix is in commit b21ebf2fb4cde16, and a similar fix is available for VB in the VB Developers Mailing List and has been applied to Debian unstable. Is this new version of binutils in the pipeline for TW? If not, I will allow the normal Oracle update process to get the fix, probably in VB 5.2.16, which will likely be realeased in about 2 months. Should I push a new version of VB with this fix to Factory? Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello I'd tried to teach myself to make a fire and find out whether VB is being tested in openQA but the search function at https://openqa.opensuse.org/tests does not seem to be returning anything for search terms like "vim" "thunderbird" or "virtualbox". Ostensibly, it is not looking into the names of the "phases", screens or the script of a testrun. Is there a way to quickly verify if an application is being tested in openQA in any of the tests of a jobgroup? What am I missing here. Thanks in advance. yours, JuhaszI On 07/13/2018 05:34 PM, Larry Finger wrote:
Adrian,
In binutils 2.31, relocation type R_X86_64_PLT32 for 32-bit PC-relative branches has been enabled. With this change, VirtualBox VMs fail to start.
The kernel fix is in commit b21ebf2fb4cde16, and a similar fix is available for VB in the VB Developers Mailing List and has been applied to Debian unstable.
Is this new version of binutils in the pipeline for TW? If not, I will allow the normal Oracle update process to get the fix, probably in VB 5.2.16, which will likely be realeased in about 2 months. Should I push a new version of VB with this fix to Factory?
Thanks,
Larry
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, 13 Jul 2018, Larry Finger wrote:
Adrian,
In binutils 2.31, relocation type R_X86_64_PLT32 for 32-bit PC-relative branches has been enabled. With this change, VirtualBox VMs fail to start.
The kernel fix is in commit b21ebf2fb4cde16, and a similar fix is available for VB in the VB Developers Mailing List and has been applied to Debian unstable.
Is this new version of binutils in the pipeline for TW? If not, I will allow the normal Oracle update process to get the fix, probably in VB 5.2.16, which will likely be realeased in about 2 months. Should I push a new version of VB with this fix to Factory?
Two month will be too late I guess, I expect the binutils update to happen
earlier.
Richard.
--
Richard Biener
On 07/13/2018, 05:34 PM, Larry Finger wrote:
Adrian,
In binutils 2.31, relocation type R_X86_64_PLT32 for 32-bit PC-relative branches has been enabled. With this change, VirtualBox VMs fail to start.
The kernel fix is in commit b21ebf2fb4cde16, and a similar fix is available for VB in the VB Developers Mailing List and has been applied to Debian unstable.
I don't understand. the commit is in the kernel since 4.16. which is in Tumbleweed. I suppose older distro won't receive binutils 2.31. ANd if so, the commit was backported to 4.4 (LEap 42.*). If need be, we ca backport to 4.12 (Leap 15). thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 16 Jul 2018, Jiri Slaby wrote:
On 07/13/2018, 05:34 PM, Larry Finger wrote:
Adrian,
In binutils 2.31, relocation type R_X86_64_PLT32 for 32-bit PC-relative branches has been enabled. With this change, VirtualBox VMs fail to start.
The kernel fix is in commit b21ebf2fb4cde16, and a similar fix is available for VB in the VB Developers Mailing List and has been applied to Debian unstable.
I don't understand. the commit is in the kernel since 4.16. which is in Tumbleweed. I suppose older distro won't receive binutils 2.31.
Older distros will receive binutils 2.31 via the Toolchain Module (binutils will be updated in the main codestream). That will happen around October I guess. But binutils itself will not introduce those relocations (well, maybe it will relax to them, didn't check). Richard.
ANd if so, the commit was backported to 4.4 (LEap 42.*). If need be, we ca backport to 4.12 (Leap 15).
thanks,
--
Richard Biener
participants (4)
-
István Juhász -
Jiri Slaby -
Larry Finger -
Richard Biener