gensio 2.5.1-2 fails due to missing symbols (lto issue?)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gensio (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
lto-disabled-list (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
"""
gensio FTBFS with LTO due to missing symbols. I had a look at fixing
this, but the symbols file needs a lot of work and has many
duplicates. gensio also has no autopkgtest, so it should be tested
that it still works when built with LTO, and if not, maybe adding it
to lto-disabled-list is the way forward.
"""
Debian updated symbols with commits 48df4fb1 and 132d03d5 that are included in 2.5.1-2, however these appear to be mismatching somehow, e.g.:
- (c++)"vtable for gensios::Sctp@Base" 2.5.1
- (c++)"vtable for gensios:
+#MISSING: 2.5.1-2# (c++)"vtable for gensios::Sctp@Base" 2.5.1
+#MISSING: 2.5.1-2# (c++)"vtable for gensios:
etc.
description: | updated |
This bug was fixed in the package lto-disabled-list - 38
---------------
lto-disabled-list (38) lunar; urgency=medium
* Add libpillowfight on amd64 to avoid autopkgtest failure (LP: #2007000)
* Add gensio to avoid FTBFS due to missing symbols (LP: #1991617)
-- Graham Inggs <email address hidden> Sat, 11 Feb 2023 17:05:01 +0000