RE: AC_SYS_LARGEFILE macro

2001-07-03 Thread Andrej Borsenkow
> > > From: "Andrej Borsenkow" <[EMAIL PROTECTED]> > > Date: Thu, 28 Jun 2001 13:58:35 +0400 > > > > It checks only for specific option for IRIX and _FILE_OFFSET_BITS and > > _LARGE_FILES macros. That is not enough; e.g. on o

Portable API for writing own macros

2001-07-01 Thread Andrej Borsenkow
Sometimes just the "official" macros, like AC_TRY_COMPILE etc are not enough. 2.50 includes many very insteresting macros (AC_VAR_PUSHDEF/POPDEF, AC_*_IFELSE, m4_* suite to name some). What macros can be "safel" used to write own macros (safely meaning they remain in future versions)? At the very

AC_SYS_LARGEFILE macro

2001-06-28 Thread Andrej Borsenkow
I was about to replace our custom check for LFS flags with AC_SYS_LARGEFILE but found that it is no real replacement. It checks only for specific option for IRIX and _FILE_OFFSET_BITS and _LARGE_FILES macros. That is not enough; e.g. on our system: bor@itsrm2% getconf LFS_CFLAGS -D_FILE_OFFSET_B

RE: Commited: RE: PATCH: Re: zsh and autoconf-2.50

2001-06-06 Thread Andrej Borsenkow
> > I fear I understand what you mean, but I might be wrong. The use of a > cache is a decision that belongs to the user and no one else. You > should not try to change this. > To clarify - if I have used conifgure -C initially and have config.status: $(sdir)/configure $(SHELL) ./confi

RE: Commited: RE: PATCH: Re: zsh and autoconf-2.50

2001-06-06 Thread Andrej Borsenkow
> > > Note, that config.cache is incompatible between two versions. 2.50 by > > default does not cache anything; you can persuade it but then > better remove > > old cache. > > Can we turn this on, or is there some good reason for not having it? > It depends. For initial configure run you have t

RE: zsh and autoconf-2.50

2001-06-01 Thread Andrej Borsenkow
> | > | % autoconf2.50 > | configure.in:55: error: undefine: undefined: zsh-debug > | configure.in:55: the top level > | > | The offending construct is here. > | > | undefine([zsh-debug])dnl > | AC_ARG_ENABLE(zsh-debug, > | [ --enable-zsh-debug compile with debug code and > debugger symbo

RE: Current CVS - test suite needs gawk???

2000-12-07 Thread Andrej Borsenkow
> | After updating CVS I cannot run testsuite anymore. Every test > ends with nawk > | error: > | > | nawk: Tempcell list is curdled > | nawk: Source line number 7 > | > | I could run testsuite sometimes ago ... around 2.49a IIRC. > > I don't understand. I'll need help here. For a start, an sh -

Current CVS - test suite needs gawk???

2000-12-07 Thread Andrej Borsenkow
After updating CVS I cannot run testsuite anymore. Every test ends with nawk error: nawk: Tempcell list is curdled nawk: Source line number 7 I could run testsuite sometimes ago ... around 2.49a IIRC. As a related matter - testsuite --help chokes on egrep, it does not like (|banner-1|...) (it

RE: autoupdate requires GNU sed

2000-10-24 Thread Andrej Borsenkow
> >>>>> "Andrej" == Andrej Borsenkow <[EMAIL PROTECTED]> writes: > > Andrej> bor@itsrm2% ./autoupdate --help autoupdate requires GNU sed > > Andrej> Just curious, what are the reasons behind it? This is with > Andrej> current CVS. >

autoupdate requires GNU sed

2000-10-24 Thread Andrej Borsenkow
bor@itsrm2% ./autoupdate --help autoupdate requires GNU sed Just curious, what are the reasons behind it? This is with current CVS. cheers -andrej Have a nice DOS! B >>