** Changed in: libunwind (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/1997161
Title:
libunwind-dev has wrong LTO data
Status in
The purpose of libunwind is to allow a program to lookup symbols by
addresses, for example to print a stack trace if some exception happens.
For that to work the program must not be stripped either. Does a version
recompiled with gcc 11.4 still works with other gcc versions one can
install on Ubunt
** Bug watch added: Debian Bug tracker #1039962
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039962
** Also affects: libunwind (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039962
Importance: Unknown
Status: Unknown
--
You received this bug notification be
The real issue is, that the .a files in the libunwind-dev package are
not stripped, and therefore the LTO information is kept in these files.
This is done by intent in the packaging. Trying to figure why ...
In the meantime the least invasive thing to do is to just rebuild with
GCC 11.4.
** Also
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-
5 matches
Mail list logo