Why not using autotools
Autotools in mawk was very old and autoconf failed on me badly. I
personally believe autotools is a malware, and fixing all the files to
make autotools work again would have taken a lot of time for me
(measured in weeks most probably). I feel like spending this time
on more useful things around libmawk thus I simply dropped autotools
support.
On the other hand, I have a great autotools replacement called scconfig
which is currently the way configuring libmawk.
Mawk generally dosn't require too many special things and should compile
fine on POSIX systems. If it doesn't compile for you, you have the following
choices:
- you can contact me for fixing scconfig
- you can create Makefile.conf.in for your system yoruself (won't help
much for fixing scconfig)
- if you are patient enough you can contribute a patch that adds really
working autotools support.
As for 3., you need to consider a few further points:
- please do it only if you are willing to maintain it long term. I don't
expect libmawk to change a lot on this level, but still... I am sure
I won't spend my time on maintaining it, and if it breaks again, I
will delete it again.
- there is a working scconfig method, and I prefer that over autotools.
I am not against alternatives, but the default will be scconfig, autotools
can be only a second choice for the user.
- autotools must occupy a separate directory and the patch should have a minimal
footprint on anything outside of that directory.