./configure - useless?

[code]
$ ./configure

   _____  ____  _   _ ______ _____  _____ _    _ _____  ______
  / ____|/ __ \| \ | |  ____|_   _|/ ____| |  | |  __ \|  ____|
 | |    | |  | |  \| | |__    | | | |  __| |  | | |__) | |__  
 | |    | |  | | . ` |  __|   | | | | |_ | |  | |  _  /|  __| 
 | |____| |__| | |\  | |     _| |_| |__| | |__| | | \ \| |____
  \_____|\____/|_| \_|_|    |_____|\_____|\____/|_|  \_\______|
                                                              
          __  ____     __           _   _ _    _  _____
         |  \/  \ \   / /     /\   | \ | | |  | |/ ____|
         | \  / |\ \_/ /     /  \  |  \| | |  | | (___ 
         | |\/| | \   /     / /\ \ | . ` | |  | |\___ \
         | |  | |  | |     / ____ \| |\  | |__| |____) |
         |_|  |_|  |_|    /_/    \_\_| \_|\____/|_____/
 
[code]

No need for a configure script in here, but I guess some people got used to it. To commit, or not to commit?

This thread is now about how much of a horrible mess Autoconf is. I distinctly remember one checking for strcmp. That's right, fucking strcmp. Whoever tries to compile anything on a system lacking that deserves to get errors up his ass, but instead everyone else who has it (and several dozen other standard library functions it checks) has to wait a ton of time. And don't get me started on the idiots including checks for a FORTRAN compiler in a package that is 100% C. Fucking GNUtards.