It is the CPU back end that is giving me trouble with build all. The free as in freedom aspect of open source is violated when any software promotes and primarily supports a proprietary tool chain. Things like how there are two checklist files, one in the primary and one in the build directory likely prevents many from succeeding. If the initial configuration was wrong or needs to be changed, the user will likely attempt to change the checklist in the main directory only to find that the changes do nothing. Several of the back ends also require manually tracking down their library paths and adding these to the source. Many of these, such as BLAS, CuBLAS, and Vulkan will fail until just the right version is included while the errors have no hinting. There are numerous other issues like ARM options not described as such, and ambiguous runtime options. Various edge case options generate a fatal warning error. Once any of these are set, the build fails without hinting about the cause, and the barely mentioned solution of manually editing the checklist yields no results.

I'm sure this is trivial for the average dev, but dev I am not. I'm just some weird script kiddie that can also build an ALU with a NOR gate, or might talk about a 65C816 in a room of 6502 fans. But I have a large number of other interests in life.

Be nicer to people. When some dumbass takes 8.5 of your 9 cat lives on the road one day, cordiality can have a large impact on your daily. I was much the same to others and regret it.