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.

** Changed in: linux (Ubuntu Disco)
       Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu Eoan)
       Status: Confirmed => Fix Committed

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

   linux-tools: perf incorrectly linking libbfd -- again

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed
Status in linux source package in Eoan:
  Fix Committed

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/linux-tools-*/perf from the generated
  linux-tools package and inspecting it with ldd. Old builds will have a
  reference to libbfd, the test builds will not.

  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 14541b1e7e723859ff2c75c6fc10cdbbec6b8c34
    Author: Stanislav Fomichev <>
    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.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to