Linux mintppc with axoloti?

#1

i have a ibook G4 with linux mintppc on , can this work with axoloti patcher ?
i am complete noob with linux so better ask around before wasting my time ...
tried it got the amd64 issue ...i already read about it but no luck yet
thanx in advance

#2

can this work... in theory, yes.

there is nothing in the axoloti UI or compiler code which is particular flavour of Linux,
its all cross-platform which is why it runs on Windows/OSX/Linux
BUT the issue is getting the platform setup correctly, with correct versions of software
this CAN take quite a bit of effort, and needs some experience of configuring the platforms and also looking at versions of software required... sometimes this is easy, other times its hard... and will sometimes mean compromise is required.
see the issue someone is having on GUIX Linux here

EDIT: I'm started a thread which will hopefully start highlighting issues/requirements etc for other platforms, but could take quite a while to make it meaningful - here

#3

Prebuilt binaries for the cross-compiler toolchain to build binaries for the ARM chip on a non-ARM platform are only available for the i686 platform. It only works on x86_64 because 32bit binaries can be run there with a 32bit libc.

There does not seem to be a release of the toolchain for the PowerPC platform, so you would have to compile the cross-compiler toolchain from source. Unfortunately, GNU Guix has not yet been ported to PowerPC, so you cannot just use my Guix packages to build and install the toolchain.

Building a cross-compiler from scratch in an uncontrolled environment is pretty hard as you have little control over what tools, libraries and headers are available at build time. (It's made a lot easier with Guix as packages are built and installed in an isolated environment.)

Once you've got a working arm-none-eabi cross-compiler with multilib enabled, a properly patched release of the cross-binutils, and a cross-build of newlib-nano (just "newlib" with the below-mentioned configure flags), the rest is comparatively easy to build.

These are the configure flags to pass for newlib:

"--target=arm-none-eabi"
"--enable-multilib"
"--disable-newlib-supplied-syscalls"
"--enable-newlib-reent-small"
"--disable-newlib-fvwrite-in-streamio"
"--disable-newlib-fseek-optimization"
"--disable-newlib-wide-orient"
"--enable-newlib-nano-malloc"
"--disable-newlib-unbuf-stream-opt"
"--enable-lite-exit"
"--enable-newlib-global-atexit"
"--enable-newlib-nano-formatted-io"
"--disable-nls"

Since you say that you are a "complete noob with linux" I don't think that building the cross-compiler from scratch will be feasible for you.