[Bug 1997161] Re: libunwind-dev has wrong LTO data

[Ghislain Bourgeois]

I get the exact same error when building a rock on 22.04. The build is
using g++.

:: lto1: fatal error: bytecode stream in file ‘/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libunwind.a’ generated with LTO version 11.2 instead of the expected 11.3
:: compilation terminated.
:: lto-wrapper: fatal error: g++ returned 1 exit status

** Also affects: libunwind (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: llvm-toolchain-14 (Ubuntu)
       Status: Confirmed => New

** Changed in: libunwind (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1997161

Title:
  libunwind-dev has wrong LTO data

Status in libunwind package in Ubuntu:
  Confirmed
Status in llvm-toolchain-14 package in Ubuntu:
  New

Bug description:
  When linking libunwind into my program I get the following message:

  lto1: fatal error: bytecode stream in file '/usr/lib/gcc/x86_64-linux-
  gnu/11/../../../x86_64-linux-gnu/libunwind-x86_64.a' generated with
  LTO version 11.2 instead of the expected 11.3

  LTO stands for link time optimization.

  My guess is that libunwind-x86_64.a in Ubuntu repositories was
  compiled with earlier gcc 11.2, but the gcc version on this new
  installation of 22.04 is 11.3.

  I am not certain whether the right fix is to recompile with newer
  compiler version, or to make the library without turning on link time
  optimization options. libunwind is used for debugging, so there is no
  obvious benefit in enabling link time optimization for this library.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1997161/+subscriptions