Wed 09 Jan 2013 09:48:10 AM UTC, comment #10:
Sure, you are entirely right. Sorry for the confusion.
|
Wed 09 Jan 2013 08:46:11 AM UTC, comment #9:
Well, if I have an `acinclude.m4' file, I have to maintain the list of included files. Passing option `-I m4', aclocal takes care of that. Now guess what I consider the better solution :-)
|
Tue 08 Jan 2013 06:59:00 PM UTC, comment #8:
Thanks, calling autreconf that way works for me as well. Even though it looks simpler and less error-prone to me to put the m4_include statements into acinclude.m4 instead of aclocal.m4.
|
Mon 07 Jan 2013 04:37:05 PM UTC, comment #7:
OK, found my thinko. You always have to pass the macro directory:
autoreconf -if -I m4
Future versions of autoreconf will honour
AC_CONFIG_MACRO_DIR([m4])
in configure.ac so that `-I m4' is no longer necessary. The other mechanism using ACLOCAL_AMFLAGS (which already works) is not applicable since groff doesn't use automake.
If you do the above call, no change to groff's configure setup is necesssary.
|
Mon 07 Jan 2013 03:11:19 PM UTC, comment #6:
by no means I'm a expert for the whole auto* stuff, but as far as I understand from the aclocal man-page aclocal.m4 will be generated by aclocal from configure.ac and therefore overwritten by each call of aclocal resp. 'autoreconf -i'.
That way all
m4_include([m4/codeset.m4])
....
statements in aclocal.m4, that comes with the tarball, will be lost.
If I rename aclocal.m4 to acinclude.m4 everything works fine and the new generated aclocal.m4 contains only one statement:
m4_include([acinclude.m4])
Tested with autoconf 2.69 and automake 1.12.5, 1.12.6 and 1.13.1
which are both installed in /usr.
|
Sun 06 Jan 2013 07:19:09 PM UTC, comment #5:
I get this:
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
configure.ac:120: warning: macro 'AM_ICONV' not found in library
configure.ac:138: warning: macro 'AM_LANGINFO_CODESET' not found in library
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/local/bin/autoconf
autoreconf: running: /usr/local/bin/autoheader
autoreconf: configure.ac: not using Automake
autoreconf: Leaving directory `.'
So this is slightly different...
Have you checked the versions of `autoconf', `autoheader', and `autoreconf'? And `aclocal', of course (I have 1.12.5). Note that both the `autoconf' and `automake' packages must be installed in the same tree (e.g. /usr or /usr/local). In particular, it doesn't work out of the box if one of the package is in /usr, and the other one in /usr/local.
|
Sun 06 Jan 2013 06:31:21 PM UTC, comment #4:
hmm, that's strange. I'm using autoconf 2.69 as well, because I've had some trouble with autoconf 1.13.1 lately, I've tried 1.12.6 too, with the same result.
Here's what I see while running autoreconf -iv after extracting the groff sources, note the different file sizes of configure and aclocal.m4:
$:/tmp> tar -xf groff-1.22.1.tar.gz
$:/tmp> cd groff-1.22.1
$:/tmp/groff-1.22.1> ls -nh configure aclocal.m4
-rw-r--r-- 1 500 100 786 Dez 30 09:40 aclocal.m4
-rwxr-xr-x 1 500 100 328K Dez 30 09:40 configure
$:/tmp/groff-1.22.1> autoreconf -iv
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: configure.ac: not using Automake
autoreconf: Leaving directory `.'
$:/tmp/groff-1.22.1> ls -nh configure aclocal.m4
-rw-r--r-- 1 500 100 56K Jan 6 19:27 aclocal.m4
-rwxr-xr-x 1 500 100 228K Jan 6 19:27 configure
|
Sun 06 Jan 2013 05:53:46 PM UTC, comment #3:
Again, I can't repeat this. Using a self-compiled version of autoconf 2.69, a call to
autoreconf -i
produces the correct configure script.
|
Sun 06 Jan 2013 03:04:03 PM UTC, comment #2:
Sorry, I got the problem after running 'autoreconf -i' and not 'autoconf' which is quite a different thing.
Thanks
|
Sun 06 Jan 2013 02:22:01 PM UTC, comment #1:
I can't repeat this. Using autoconf 2.69, it works just fine. I now notice that I've forgotten to re-run autoconf after updating to 1.22.1 (so you will see 1.22 at some places), but options --with-x or --with-gs are present.
Actually, it's not clear at all to me how you don't get those options: The file `aclocal.m4' in the top-level directory is certainly found, and it includes `m4/groff.m4' which contains the code for those two options.
Maybe running `autoconf --force --verbose' gives more hints.
|
Sun 06 Jan 2013 01:43:26 PM UTC, original submission:
I tried to recreate configure with autoconf and the configure.ac from the groff tarball. This leads to a different configure with less options, e.g. the --with-x or --with-gs options are no longer available.
|