Bug#898502: ucommon: Please update symbols for riscv64 and ia64
Source: ucommon
Version: 7.0.0-12
Severity: serious
User: debian-riscv@lists.debian.org
Usertags: riscv64
Hi,
This is possibly related with #897878 (FTBFS due to symbols with GCC-8), and
indeed the solution it's similar, needs an update to the symbols file, but
decided to report it separately just in case.
The problem of symbols mismatch already happens with gcc-7, the default compiler
in unstable, for two arches:
https://buildd.debian.org/status/fetch.php?pkg=ucommon&arch=ia64&ver=7.0.0-12&stamp=1523296684&raw=0
https://buildd.debian.org/status/fetch.php?pkg=ucommon&arch=riscv64&ver=7.0.0-12&stamp=1524128306&raw=0
Also can be seen in the main buildd page in a clear way, the same missing symbol
for both ia64 and riscv64 (but different from the ones in gcc-8):
https://buildd.debian.org/status/package.php?p=ucommon&suite=sid
+ _ZN7ucommon6String6vscanfEPKcPv@Base 7.0.0-12
+ _ZN7ucommon6String7vprintfEPKcPv@Base 7.0.0-12
So, conjecturing a bit, to me it seems likely that it actually FTBFS in all
arches, only that it was not detected because the last builds for these two ones
happend in the last <33 days, and for the rest many months ago (8+ months, all
during the same days).
It's strange that symbols change in this way with the same GCC major version,
the compiler was 7.2 when compiled in the other arches. But the alternative
explanation that the symbols are fine in all arches except in ia64 and riscv64
is even more improbable IMO, given the additional coincidade of build dates.
I'm OK if you decide to set a lower priority, but given that it already fails in
at least two arches, the possibility that it happens in others nowadays, and
GCC-8 becoming the default soonish (< 3 months, if we look at what happened in
previous years), made me to decide for severity "serious".
Thanks and cheers.
--
Manuel A. Fernandez Montecelo <mafm@debian.org>
Reply to: