ubuntustudio-bugs team mailing list archive

[oliver stotz <1939293@xxxxxxxxxxxxxxxxxx>]

I can also confirm that the bug is now fixed with -proposed

THANKS A BUNCH to everyone involved !

best

Oliver

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to puredata in Ubuntu.
Matching subscriptions: Ubuntu Studio Bugs
https://bugs.launchpad.net/bugs/1939293

Title:
  unable to load externals: undefined symbol "__pow_finite" and similar

Status in puredata package in Ubuntu:
  Fix Released
Status in puredata source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Pd-0.50.2-3 (as shipped with focal) is unable to load the external
  objects (plugins) shipped in the "puredata-extra" package (which is
  built from the same source package as "puredata" itself) due to a
  problem with some symbols that should be provided by libm.

  The missing symbols are `__exp_finite`, `__log_finite`, `__logf_finite` and `__pow_finite`.
  The affected externals are:
  - bonk~
  - choice
  - fiddle~
  - sigmund~

  The problem appears to come from a change in the symbols when
  upgrading from glibc-2.30 to glibc-2.31 (e.g. see
  https://sourceware.org/pipermail/libc-alpha/2020-May/113773.html)

  A simple rebuild of the package seems to fix the problem.

  To trigger a rebuild I've added a debdiff that bumps the version
  number to "0.50.2-3build1~ubuntu20.04.1" (i hope this is the correct
  version scheme for such an upload).


  [Test Plan]

  A quick way to check whether the objects can be loaded is by running
  this script (after installing the "puredata-extra" package):

  ~~~
  find /usr/lib/puredata/extra/*/ -name "*-help.pd" -exec pd -nrt -nogui -send "pd quit" {} ";"
  ~~~

  I've attached the output of such a (failing) test run (note the lines
  starting with "error:")


  [Where problems could occur]

  The rebuild apparently fixes the problem, although a more correct fix would probably be to add "-lm" to the linker-flags when building the plugins.
  (This is what upstream did for the Pd-0.51 release).
  In order to keep the impact of my patch minimal, i have chosen to just trigger a rebuild.


  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: puredata-extra 0.50.2-3
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Aug  9 11:23:35 2021
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: puredata
  UpgradeStatus: No upgrade log present (probably fresh install)

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