Do you honestly think that I gradually developed a 2500 line configure script by hand over more than six years for an important project of mine <i>ironically</i>, in order to promote Autocrap?<p>The script detects just what is necessary for the program and is easy for me to understand, extend, port and debug.<p>You can fix it right on a given target platform where you&#x27;re trying to get it working.<p>You can&#x27;t do that with an Autoconf configure script (in a way that you can merge back to your stream), because it&#x27;s generated. You need an installation of Autoconf.<p>If you want to patch the Autoconf-generated configure script with minimal changes, just reflecting the topic of the change you&#x27;re making, you need the exact same version of Autoconf with which it was generated, otherwise there will be irrelevant diffs all over the script.<p>(I learned this when I developed an embedded, cross-compiled LInux distro from scratch. On my development system, I had about half a dozen installations of different versions of Autoconf, so that I could create minimal patches against configure scripts!!!)<p>And, of course, you first have to work backwards to figure out how to coax the script behavior you want indirectly through the m4 macro files. Forget about &quot;I just want to make this tiny tweak in one command and it will Just Work&quot;.<p>In my script, you just ... open the script and write the necessary code. Then regression-test it on the other targets, do any necessary tweaking and commit.<p>Once you have written one of these scripts, you can easily re-use it. My above script is BSD-licensed. Anyone can take it and cut out whatever they don&#x27;t need. If you want help using it or have any questions, you can fire me an e-mail.