It's --enable-amule-gui, not --enable-amulegui (note the dash; without the dash the option is unrecognized and unrecognized options are ignored; that's a feature and it's the same for all autoconf based projects)
By the way:
- "rpmbuild -tb aMule-2.1.0.tar.bz2" does not work because aMule-CVS.spec is in the tarball:
$ LC_ALL=C rpmbuild -tb aMule-2.1.0.tar.bz2
error: File /tmp/aMule-CVS-20060102.tar.bz2: No such file or directory
$ bunzip2 aMule-2.1.0.tar.bz2
$ tar --delete -f aMule-2.1.0.tar aMule-2.1.0/aMule-CVS.spec
$ bzip2 aMule-2.1.0.tar
$ rpmbuild -tb aMule-2.1.0.tar.bz2
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.68331
+ umask 022
+ cd /usr/src/packages/BUILD
+ cd /usr/src/packages/BUILD
+ rm -rf aMule-2.1.0
+ tar -xf -
+ /usr/bin/bzip2 -dc /tmp/aMule-2.1.0.tar.bz2
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd aMule-2.1.0
++ /usr/bin/id -u
+ '[' 1001 = 0 ']'
++ /usr/bin/id -u
+ '[' 1001 = 0 ']'
+ /bin/chmod -Rf a+rX,g-w,o-w .
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.20495
etc...
- there are ~ 40000 lines of unneeded stuff (~ 1.3 MB uncompressed, ~200 kB compressed) in the autom4te.cache directory
EDIT: looks like rpmbuild uses the ASCII order ASCII to find out which .spec file to use and the dash comes directly before the dot in ASCII, so aMule-CVS.spec has a higher priority than aMule.spec...