more humour for the FSF Autoconf page

2009-01-01 Thread Ben Elliston
A few years ago, a friend submitted a Debian bug report against Autoconf
because it included `readable' in the permissions mask of the configure
script. :-)  See:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=140837

Ben

-- 
Ben Elliston b...@au.ibm.com
Australia Development Lab, IBM





--quiet option not carried through to config.status

2009-01-01 Thread Ben Elliston
When building GCC, I often pass --quiet to the top-level configure
script.  However, I sometimes find the need to blow away the build tree
and rebuild from scratch.  When this happens, I use config.status -V to
find out what options I passed when the build tree was first set up. eg:

  $ ./config.status -V
  config.status
  configured by /home/bje/source/gcc-trunk/configure, generated by GNU Autoconf 
2.59,
with options  '--disable-bootstrap' '--enable-languages=c,c++'
  [...]

If I configured this tree at the outset with --quiet, this will never be
recorded in the  config.status output and I must remember to append it
when reconstructing the configure command line.  This may well also
apply to other configure options.

A bug?

Cheers, Ben

-- 
Ben Elliston b...@au.ibm.com
Australia Development Lab, IBM





Re: man pages for config.guess and friends

2006-06-19 Thread Ben Elliston
  I suggest to move the man pages for config.guess and config.sub from
  autoconf to the config CVS.
 
 May be a good idea, if Ben agrees.  I think this can safely wait until
 after Autoconf 2.60, though, which we'd like to release ASAP.

I was not even aware that man pages exist; naturally I would be happy
to maintain them in the config CVS repository.

Thanks, Ben