Re: Support for configure.ac

2001-01-19 Thread Akim Demaille
"Tom" == Tom Tromey [EMAIL PROTECTED] writes: "Akim" == Akim Demaille [EMAIL PROTECTED] writes: Akim Once the `make check' finished, I'll check this in: Tom Did the bug affect any of the existing test cases? If not I Tom generally add a new test. Nope, and I was thinking about writing a

Re: Support for configure.ac

2001-01-19 Thread Lars Hecking
Tom Tromey writes: "Akim" == Akim Demaille [EMAIL PROTECTED] writes: Akim Once the `make check' finished, I'll check this in: Did the bug affect any of the existing test cases? If not I generally add a new test. As long as the bug was there, I couldn't even get as far as running the

Re: Support for configure.ac

2001-01-18 Thread Akim Demaille
"Lars" == Lars Hecking [EMAIL PROTECTED] writes: Lars I posted everything I did. I did not install automake, only ran Lars configure and make dist straight from a copy of my checked-out Lars tree. Well, I don't know. ~/src/am % ./configure loading cache ./config.cache checking for a BSD

Re: Support for configure.ac

2001-01-18 Thread Akim Demaille
"Lars" == Lars Hecking [EMAIL PROTECTED] writes: Lars Undoubtedly, automake-cvs running on its own files should Lars produce something useful, shouldn't it? Yes, indeed. But I just switched me brains on, and understood. Sure you have the new .am files, but since the Makefile want to update

Re: Support for configure.ac

2001-01-18 Thread Lars Hecking
Yes, indeed. But I just switched me brains on, and understood. Sure you have the new .am files, but since the Makefile want to update the Makefiles first, you run an old automake which does not, indeed, substitute @CONFIGURE_AC@. So find a means, but you have to `make automake' before

Re: Support for configure.ac

2001-01-18 Thread Akim Demaille
| Yes, indeed. But I just switched me brains on, and understood. | | Sure you have the new .am files, but since the Makefile want to update | the Makefiles first, you run an old automake which does not, indeed, | substitute @CONFIGURE_AC@. So find a means, but you have to `make |

Re: Support for configure.ac

2001-01-18 Thread Lars Hecking
| At no time an old copy of automake is run. You don't seem to understand. Make a diff automake.in automake and I think you'll see what I mean. % grep @CONFIGURE_AC@ Makefile.in $(srcdir)/stamp-vti: automake.texi $(top_srcdir)/@CONFIGURE_AC@ % If autoconf, not automake is

Re: Support for configure.ac

2001-01-18 Thread Akim Demaille
| | At no time an old copy of automake is run. | | You don't seem to understand. Make a | | diff automake.in automake | | and I think you'll see what I mean. | | % grep @CONFIGURE_AC@ Makefile.in | $(srcdir)/stamp-vti: automake.texi $(top_srcdir)/@CONFIGURE_AC@ | % | | If

Re: Support for configure.ac

2001-01-18 Thread Akim Demaille
$ diff -u automake.in automake --- automake.in Wed Jan 17 06:30:29 2001 +++ automakeThu Jan 18 13:46:25 2001 According to the headers of your mails, somehow, automake finally got created (the last failure you presented was at X-From-Line: [EMAIL PROTECTED] Thu Jan 18 13:06:26 2001). So, if

Re: Support for configure.ac

2001-01-18 Thread Lars Hecking
According to the headers of your mails, somehow, automake finally got created (the last failure you presented was at X-From-Line: [EMAIL PROTECTED] Thu Jan 18 13:06:26 2001). So, if indeed you have: In all cases I posted, automake _did_ get created. ~/src/am % grep CONFIGURE_AC automake

Re: Support for configure.ac

2001-01-18 Thread Akim Demaille
"Lars" == Lars Hecking [EMAIL PROTECTED] writes: Lars I have that, but it still doesn't work. What did you type? How did it fail? Do your Makefile.in still have the @CONFIGURE_AC@ stuff? If so, run `touch *.am; make'. Lars My idea is that this new feature in automake is not compatible

Re: Support for configure.ac

2001-01-18 Thread Lars Hecking
Akim Demaille writes: "Lars" == Lars Hecking [EMAIL PROTECTED] writes: Lars I have that, but it still doesn't work. What did you type? How did it fail? Do your Makefile.in still have the @CONFIGURE_AC@ stuff? If so, run `touch *.am; make'. $ touch *.am $ make cd .

Re: Support for configure.ac

2001-01-18 Thread Raja R Harinath
Lars Hecking [EMAIL PROTECTED] writes: | At no time an old copy of automake is run. You don't seem to understand. Make a diff automake.in automake and I think you'll see what I mean. % grep @CONFIGURE_AC@ Makefile.in $(srcdir)/stamp-vti: automake.texi

Re: Support for configure.ac

2001-01-18 Thread Lars Hecking
Akim Demaille writes: ~/src/am % perl --versionnostromo 17:58 This is perl, v5.6.0 built for i386-linux [...] What do you have? Tried both 5.005_03 and 5.6.0 built for sun4-solaris. It makes no difference.

Re: Support for configure.ac

2001-01-18 Thread Akim Demaille
| I see this even with an installed automake. It appears that | 'texi-vers.am' doesn't have the CONFIGURE_AC transform before being | inserted into Makefile.in. From automake.in, in handle_texinfo, | around line 2277 | | $output_rules .= |

Re: Support for configure.ac

2001-01-18 Thread Akim Demaille
Once the `make check' finished, I'll check this in: Index: ChangeLog from Akim Demaille [EMAIL PROTECTED] * automake.in (handle_texinfo): Use transform, and transform CONFIGURE_AC. Reported by Lars Hecking, and diagnosed by Raja R Harinath. Index: automake.in

Re: Support for configure.ac

2001-01-18 Thread Lars Hecking
[...] Now I have it. Sorry Lars... The test suite did not see anything... I'm fixing this. I have added . 's/\@VTEXI\@/' . $vtexi . '/g;' +. 's/\@CONFIGURE_AC\@/' . $configure_ac . '/g;' . 's,\@MDDIR\@,' . $conf_pat . ',g;',

Re: Support for configure.ac

2001-01-18 Thread Tom Tromey
"Akim" == Akim Demaille [EMAIL PROTECTED] writes: Akim Once the `make check' finished, I'll check this in: Did the bug affect any of the existing test cases? If not I generally add a new test. Tom

Re: Support for configure.ac

2001-01-17 Thread Lars Hecking
Akim Demaille writes: Will be applied within a couple of minutes. I don't think this is working as intended. cvs automake as of now. autoconf 2.13. $ ./configure creating cache ./config.cache checking for a BSD compatible install... /usr/local/gnu/bin/install -c checking whether build