Compile issues after 223a709a4f205809f0410708f8a4c19458db56ec commit

[dhwz]

Compile issues after 223a709a4f205809f0410708f8a4c19458db56ec commit

[midwan]

mt32emu requires CMake to build, so the requirements are updated accordingly since that commit.
The automated builds in the agents I use run make (and they don't fail), so I don't think it's a generic issue?

[dhwz]

Edit: Note seems it's only an issue when building via make, cmake-make does work, so for me it's ok but maybe you still want to fix it (make did work before).

[solskogen]

How do you compile? I suspect that libguisan didn't build. If you use -j remove it and try again

[dhwz]

Packages for our OS are build with parallel (which enforces the use of -j), but I also already tried unsetting the use of parallel, again with the same issue.

[dhwz]

Agreed, maybe it's only happening in special cases like with our make toolchain.
As said for me it's solved as it works with cmake-make toolchain.

[solskogen]

It's very strange that it doesn't build libguisan. Something else is wrong with your toolchain.

[dhwz]

Idk never had that issue before.
It's the toolchain also used by CoreELEC.

[solskogen]

Give us the full log please, and all of the commands you run (with flags)

[dhwz]

Ok I've solved it now also for make, seems the root cause was LDFLAGS, which somehow injected -lguisan to the linker for cmake of mt32emu.
After unsetting LDFLAGS in our package for amiberry it's now working again as expected.

AmberELEC/AmberELEC@261f8e1#diff-08f4eef81fb54d20229022e1a6a184e2ac07a1c9a1f943164602acf2cc0d6227R27