Christoph Lohmann dixit:

>Remove  this  Build.sh crap and add some real Makefile and I will recon‐
>sider using it.

You can let Build.sh generate a Makefile using the -M option,
but that Makefile would then be specific to the system it ran
on (actually “for”, not “on”, considering cross-compiling).

This is done in MirBSD, MidnightBSD and Android currently.

On GNU/Linux targets you would additionally need to provide
signames.inc which is generated by Build.sh, or better, the
libc should provide a sys_signame[] array. Note that Linux,
kernel-side, has different signal names (even amount of them!)
per architecture, and even libc…

>wc -l Build.sh
>2362

An equivalent autoconf crap would be ten to hundred times
that size, FWIW.

>Does this script really need to emulate autohell?

Yes given mksh’s portability requirement.

>Can’t a shell run in a minimal C function library subset which is
>available everywhere?

I wish. Really.

mksh has very few imports, but the system-specific parts
sadly vary greatly across OSes.

bye,
//mirabilos
-- 
17:08⎜«Vutral» früher gabs keine packenden smartphones und so
17:08⎜«Vutral» heute gibts frauen die sind facebooksüchtig
17:10⎜«Vutral» aber auch traurig; früher warst du als nerd voll am arsch
17:10⎜«Vutral» heute bist du als nerd der einzige der wirklich damit klarkommt

Reply via email to