Re: 2.49e problems with gcc

2001-05-19 Thread Thomas Dickey
On Sat, May 19, 2001 at 03:00:38PM +0200, Akim Demaille wrote: > > (partly stolen from AC_CHECK_DECLS) but this requires cvs autoconf, I > believe. > > Yes, it does. And if you require 2.50, then just use AC_CHECK_DECLS :) > > Is there a good way to say this in 2.13-speak, so

Re: 2.49e problems with gcc

2001-05-19 Thread Akim Demaille
(partly stolen from AC_CHECK_DECLS) but this requires cvs autoconf, I believe. Yes, it does. And if you require 2.50, then just use AC_CHECK_DECLS :) Is there a good way to say this in 2.13-speak, so I can suggest a patch to the gcc maintainers? Sorry,

RE: 2.49e problems with gcc

2001-05-17 Thread Tim Van Holder
> | Nice patch, but I don't think it works. I'd be surprised if you > | actually have the #undef templates in config.h.in since you pass an sh > | var, which is opaque to autoheader. You need `static' values for > | autoheader. That's why they had the last chunk. > | > | Use > | > | -if test x

Re: 2.49e problems with gcc

2001-05-15 Thread Tim Van Holder
On 12 May 2001 15:47:10 +0200, Akim Demaille wrote: > > On a second thought, the right way to handle this depends upon the > nature of $1: is it always a literal, or can it be a shell variable? > If it's always a literal, then your first approach but using > translit([HAVE_DECL_$1], [a-z], [A-Z])

Re: 2.49e problems with gcc

2001-05-15 Thread Tim Van Holder
Sorry for the delay in replying; my home PC suffered a minor heat stroke and will be out of action for a while :-) On 12 May 2001 15:36:53 +0200, Akim Demaille wrote: > > "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes: > > Tim> The only call is > > Tim> gcc_AC_CHECK_PROG_VER(MAKEINFO,

Re: 2.49e problems with gcc

2001-05-12 Thread Akim Demaille
| Index: aclocal.m4 | === | RCS file: /cvs/gcc/gcc/gcc/aclocal.m4,v | retrieving revision 1.40.4.1 | diff -u -r1.40.4.1 aclocal.m4 | --- aclocal.m42001/02/18 05:41:46 1.40.4.1 | +++ aclocal.m42001/05/11 15:49:26 |

Re: 2.49e problems with gcc

2001-05-12 Thread Akim Demaille
> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes: Tim> The only call is Tim> gcc_AC_CHECK_PROG_VER(MAKEINFO, makeinfo, --version, [GNU Tim> texinfo.* \([0-9][0-9.]*\)], [4.*]) Hm, looks good. Tim> This would put the texinfo pattern inside the special << >> Tim> quotes, which might be

Re: 2.49e problems with gcc

2001-05-11 Thread Tim Van Holder
> | [changequote(<<,>>)dnl > | ac_prog_version=`<<$>>$1 $3 2>&1 | > |sed -n 's/^.*patsubst(<<$4>>,/,\/).*$/\1/p'` > | echo "configure:__oline__: version of $2 is $ac_prog_version" > >&AC_FD_CC > | case $ac_prog_version in > | '') gcc_cv_prog_$2_modern=no;; > |

Re: 2.49e problems with gcc

2001-05-11 Thread Akim Demaille
> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes: Tim> Note that I think you shouldn't redirect the first run; this Tim> masks any useful error messages sourcing traces.sh might produce. Hm, maybe. OK with me.

Re: 2.49e problems with gcc

2001-05-11 Thread Akim Demaille
| In fact, this macro (also from gcc/aclocal.m4) seems to be the cause | of the recursion problem: | | dnl Locate a program and check that its version is acceptable. | dnl AC_PROG_CHECK_VER(var, name, version-switch, | dnl version-extract-regexp, version-glob) | AC_DEFUN(gcc_AC_

RE: 2.49e problems with gcc

2001-05-10 Thread Tim Van Holder
> > Tim> And as for the autoheader problem: is it supposed to fail > > Tim> silently (as it does for me), > > > > No, it should not. > OK - I'll look into possible problems (I expect there'll be some issue > with FDs/redirection again). For further evidence, is autoheader > supposed to clean up a

Re: 2.49e problems with gcc

2001-05-10 Thread Tim Van Holder
> (NOTE: This is with a fresh aclocal.m4 but > a configure.in stripped of changequotes; there may be similar > showstoppers in the stock configure.in). Actually, just checked and the macro I posted is the only one causing problems for the current autoconf in gcc.

RE: 2.49e problems with gcc

2001-05-10 Thread Tim Van Holder
> Again, I think it is just miscommunication. I really understood > `changequote is broken' (which is likely since we do redefine it), > while it should read `people were used to change arbitrarily the > quotes, i.e., change deeply the environment and were expecting the > macros invoked in betwee

Re: 2.49e problems with gcc

2001-05-10 Thread Akim Demaille
> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes: Tim> As for Akim's statement: changequote is clearly to blame here; is Tim> there no way for autoconf to detect such problems before invoking Tim> m4? Again, I think it is just miscommunication. I really understood `changequote is broken

Re: 2.49e problems with gcc

2001-05-10 Thread Tim Van Holder
> you have to code-around it rather than simply remove them > (can escape '[' by '[[', for instance). Hmm - allow me to exclaim 'Duh!'. I guess I should've been more precise: "I removed all changequote's, replaced the replacement quotes by [/] and doubled existing [/]'s where appropriate. This

Re: 2.49e problems with gcc

2001-05-10 Thread Akim Demaille
> "Thomas" == Thomas E Dickey <[EMAIL PROTECTED]> writes: Thomas> check/see if it (gcc's configure script) uses changequote(). Thomas> That feature is broken in the current alpha versions of Thomas> autoconf, has been reported a few times (and shows up with Thomas> this symptom). Akim> No Th

Re: 2.49e problems with gcc

2001-05-10 Thread Thomas E. Dickey
On 10 May 2001, Akim Demaille wrote: > > "Thomas" == Thomas E Dickey <[EMAIL PROTECTED]> writes: > > Thomas> check/see if it (gcc's configure script) uses changequote(). > Thomas> That feature is broken in the current alpha versions of > Thomas> autoconf, has been reported a few times (and sh

Re: 2.49e problems with gcc

2001-05-10 Thread Akim Demaille
> "Thomas" == Thomas E Dickey <[EMAIL PROTECTED]> writes: Thomas> check/see if it (gcc's configure script) uses changequote(). Thomas> That feature is broken in the current alpha versions of Thomas> autoconf, has been reported a few times (and shows up with Thomas> this symptom). No Thomas,

Re: 2.49e problems with gcc

2001-05-09 Thread Thomas Dickey
On Wed, May 09, 2001 at 11:13:10PM +0200, Tim Van Holder wrote: > > You found it. Configure.in is loaded with changequote() calls. > > > > > > > That feature is broken in the current alpha versions of autoconf, > > > has been reported a few times (and shows up with this symptom). > > > > > > Some

RE: 2.49e problems with gcc

2001-05-09 Thread Tim Van Holder
> You found it. Configure.in is loaded with changequote() calls. > > > > That feature is broken in the current alpha versions of autoconf, > > has been reported a few times (and shows up with this symptom). > > > Something broken? Is it to be fixed before 2.50? > OK - tried removing all changequ

Re: 2.49e problems with gcc

2001-05-09 Thread Matthew Schalit
Thomas ! "Thomas E. Dickey" wrote: > > On Wed, 9 May 2001, Matthew Schalit wrote: > > > > > Hi folks, > > > > I raised this problem once before, where I can't > > boostrap CVS gcc using autoconf 2.49e > > > > Gcc builds just fine with 2.13. > > > > Summary: > > - > > autoconf -l .

Re: 2.49e problems with gcc

2001-05-09 Thread Thomas E. Dickey
On Wed, 9 May 2001, Matthew Schalit wrote: > > Hi folks, > > I raised this problem once before, where I can't > boostrap CVS gcc using autoconf 2.49e > > Gcc builds just fine with 2.13. > > Summary: > - > autoconf -l . gets run and fails with a gm4 > recursion limit of 250 exceeded.

2.49e problems with gcc

2001-05-09 Thread Matthew Schalit
Hi folks, I raised this problem once before, where I can't boostrap CVS gcc using autoconf 2.49e Gcc builds just fine with 2.13. Summary: - autoconf -l . gets run and fails with a gm4 recursion limit of 250 exceeded. Running an i586-sco-sysv5uw7.1.1, gnu make-3.79.1 binutils 2.1