what Id wonder is, if you are building SC, how did you get into a position where libs are mismatching?
did you have to upgrade things from pacman? as ive mentioned previously, this always carries a ‘risk’, as pacman/arch linux is not designed for ‘partial upgrades’
… thats why I said, unfortunately, the best (ideal?) way forward is to get Organelle to work with a modern kernel, and so be able to bring arch linux fully up to date, and so to get all libs/modules/apps all on to a square footing.
btw - why do you want the SC IDE on the Organelle?
the IDE and X are going to consume precious CPU/memory.
personally, I prefer to run the SC server on the Organelle (so that sound is generated there), and run the IDE remotely.
a laptop is ideal - easier than lugging around HDMI monitor/keyboard/mouse.
but if you want to use an existing hdmi/monitor/keyboard, why not just use a rPI running the ide, and remotely connected to your Organelle.
when Ive thought about this myself, its raised interesting questions about my end game/goal
(and ones I keep having to ask myself)
why use Organelle at all for SC?
(one can easily argue a laptop or even rPI + soundcard is more suitable)
my answer is I like creating standalone SC patches that run on organelle… in a similar way to the way we use PD. at this point its disconnect and portable
so the IDE is just use as a development setup to get the patch working - so I don’t even need to use SC for much of the work, I can do it on a Mac (+ OscProxy to integrate the Organelle hardware)
id be really interested to hear - whats your goal? what are you trying to achieve?