GNOME Bugzilla – Bug 612329
automake --force unrecognized if POSIXLY_CORRECT set
Last modified: 2012-08-01 21:51:53 UTC
[ From http://bugs.debian.org/572840 ] emilio@saturno:~$ automake --force automake: `configure.ac' or `configure.in' is required emilio@saturno:~$ POSIXLY_CORRECT=1 automake --force automake: unrecognized option `--force'. automake: Try `/usr/bin/automake --help' for more information. emilio@saturno:~$ Since --no-force is not the default (so --force would be if it existed) as can be seen in the automake info manual or in automake's source code, the --force option could be removed, or alternatively POSIXLY_CORRECT unset. I like more the first option.
I don't see any indication in the automake manual that --force would be unrecognised when POSIXLY_CORRECT is set? Is that by design, or a bug ?
It's probably a bug in automake for letting Getopt::Long accept --force sometimes, but not always. Anyway I've looked in the automake info manual and I see no mention of --force for automake, only --no-force (--force is documented for aclocal but not automake) and automake --help doesn't list it either. Why not just remove the option since --force is the default?
Created attachment 219910 [details] [review] patch to drop --force with automake This patch removes the use of --force with automake in gnome-autogen.sh.
Comment on attachment 219910 [details] [review] patch to drop --force with automake Pushed to master as commit 0efa19df00955bfec29995736e262412fd32de86.