@a1ba@navi Just in case you're building from something prior to 4.3BSD or AT&T UNIX® System V Release 4 (aka SVR4, which you can grep for in ./configure scripts).
@a1ba@navi Best is when some of those excessive checks occasionally fail with modern compilers because they screwed the syntax (and of course hide compiler warnings…).
@navi Which is one of the reasons why the oasis thing of just ignoring the upstream buildsystem is a bit appealing.
(Another being reviewability of the code involved, auto*hell configure scripts might as well be arcane assembly)
@lanodan appealing if you have time to understand how to build every package i guess
because you lose the easy of just inherit build-system and have it work as is (for meson and autotools usually, make it depends if the makefile is sane)
@navi Usually it just boils down to ${CC} -o ${P} *.c and few -D flags.
But yeah, you wouldn't do a full ports tree like that, but for something a bit like a BSD base system it makes sense and holy shit it's fast.
Add comment