On Sun, 2021-09-12 at 13:09 +0200, IOhannes m zmölnig wrote: > Am 12. September 2021 11:48:22 MESZ schrieb Roman Haefeli < > reduz...@gmail.com>: > > On Sun, 2021-09-12 at 11:36 +0200, Ingo wrote: > > > Yep, looks like [declare -path /usr/lib/puredata/extra/iemlib > > > -lib > > > iemlib] > > > should work but it doesn't. > > > I'm suspecting that certain objects are simply not compiled > > > correctly. > > > > I confirm iemlib 1.22 from Deken is broken for the Raspberry Pi OS > > on > > Raspberry Pi. > > could you also confirm that iemlib from the raspbian (and/or Debian) > repositories is broken?
iemlib 1.22.1-1~bpo10+1 from buster-backports is working fine! Re deken version: I can't remember exactly the details, but I guess I cross-compiled iemlib 1.22 on Ubuntu 20.04 for the Raspberry Pi and uploaded this to Deken without even testing (I usually perform a basic functionality check, which I obviously didn't do here). It seems Ubuntu 20.04 uses a different glibc version that Debian Buster, so cross-compilation might be a bad idea. (At least that's what I understand is the issue from the error message). What would you do, if a build is broken in such a way? Does it warrant a plain removal from the Deken repositories? Roman
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
