Joachim Mairböck

Alternatively, we could also build ninja with the python-based bootstrap instead of cmake: https://github.com/ninja-build/ninja/blob/master/README.md#python

IIRC we could also change cmake to use its own bundled libarchive instead of the system package, if that helps. I think that links libarchive statically then though. In general,...

The currently used Java version seems to be 11, according to https://josm.openstreetmap.de/browser/josm/trunk/nodist/pom.xml#L12

I understood the distinction like this: everything that is executed during the build (on the build host) belongs to BUILD_PREREQUIRES, everything else belongs to BUILD_REQUIRES (e.g. libraries to be linked,...

I think I made a mistake there also in some of my perl recipes, now thinking of it. I put the perl modules also into BUILD_REQUIRES which would belong into...

The new fontconfig version is linked against the newer version of libxml2 (libxml2_2.14). Could it be that something else still requires the old version, thus causing the problem?

You could add a `REPLACES="minetest$secondaryArchSuffix"`. Then, old installations will get upgraded automatically.

Did you test this with gcc 2? According to https://github.com/openssl/openssl/blob/master/NEWS.md#openssl-36, this now uses C99, so it likely doesn't work any more as is with gcc 2.

I decided to give it a try anyway and found only one actual compile error so far (other than a huge load of warnings because of `#pragma once`) in `test/mem_alloc_test.c`,...

> @jmairboeck With the tests disabled I guess it's only one (parse) error that shows up, so maybe you can still push the patchset for this? I pushed it to...