Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1026048

Bug#970735: mpdecimal FTBFS in bullseye: symbol differences

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Source: mpdecimal
Version: 2.5.0-4
Severity: serious
Tags: ftbfs patch
User: helmutg@debian.org
Usertags: rebootstrap

mpdecimal has a number of symbols whose appearance is quite dependent on
the precise compiler version. These tend to be symbols for inlined
functions and template instantiations. This presently causes FTBFS in
bullseye, e.g.:

https://tests.reproducible-builds.org/debian/rbuild/bullseye/amd64/mpdecimal_2.5.0-4.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/bullseye/arm64/mpdecimal_2.5.0-4.rbuild.log.gz
https://tests.reproducible-builds.org/debian/rbuild/bullseye/armhf/mpdecimal_2.5.0-4.rbuild.log.gz

This happens, because the bullseye toolchain was not exactly the same as
the unstable toolchain at the time of the build and the compiler decided
to instantiate symbols differently. Instead of changing symbols back and
forth, I suggest simply marking them as optional.

Beyond this, you can use arch-bits=32 and arch-bits=64 to remove the
need for interpolating the symbol file since that feature is now present
in oldstable.

I'm attaching a patch for the optional stuff for your convenience.

Helmut

Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread

Thread

Bug#970735: mpdecimal FTBFS in bullseye: symbol differences Helmut Grohne <helmut@subdivi.de> - 2020-09-22 20:10 +0200

csiph-web