linux-tools: perf incorrectly linking libbfd -- again
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Committed
|
High
|
Unassigned | ||
Disco |
Won't Fix
|
High
|
Andy Whitcroft | ||
Eoan |
Won't Fix
|
High
|
Unassigned |
Bug Description
= SRU Justification =
Impact: Linking perf (part of the linux-tools package) against libbfd prevents users to have linux-tools of different kernel versions installed in parallel. Which makes debugging hard.
Fix: As stated above this had been fixed before but upstream changes of the kernel between 4.19 and 5.0 voided those fixes. Unfortunately without causing build failures but causing libbfd to be used again.
Testcase: Extracting ./usr/lib/
Risk of regression: low as this is a build-time change.
=====
It seems the previous attempt to disable use of libbfd has been rendered ineffective by an upstream change:
commit 14541b1e7e72385
Author: Stanislav Fomichev <email address hidden>
Date: Thu Nov 15 16:32:01 2018 -0800
perf build: Don't unconditionally link the libbfd feature test to -liberty and -lz
This leads us to have a hard dependency on libbfd at a specific minor version. We do not need this library, we can use libiberty and others for the same functions in perf.
This is a recurrance of Bug #1748922.
description: | updated |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Andy Whitcroft (apw) |
description: | updated |
Changed in linux (Ubuntu Disco): | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Andy Whitcroft (apw) |
Changed in linux (Ubuntu Eoan): | |
assignee: | Andy Whitcroft (apw) → nobody |
tags: | added: cscc |
Changed in linux (Ubuntu Disco): | |
status: | Fix Committed → Won't Fix |
This has been applied to Disco (and I believe to Eoan, too) but the bug reference was pointing to a different bug (just libbfd and libbfp looking too similar to notice): bug #1826410. This will require some care to untangle without requiring to do the kernel again.