Re: non portable sed scripts

Hi Paul, * Paul Eggert wrote on Fri, May 19, 2006 at 11:04:52PM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > We check the 99 commands limit, but > > not the [4000] characters limit any more... :-/ > > But the 4000-character limit is documented by Autoconf to be a limit > on the len

Re: fetchmail-6.2.5 solaris 8 GNUCC

Hi Jerry, * Carlin, Jerry wrote on Fri, May 19, 2006 at 09:40:00PM CEST: > > checking resolv.h presence... yes > configure: WARNING: resolv.h: present but cannot be compiled > configure: WARNING: resolv.h: check for missing prerequisite headers? > configure: WARNING: resolv.h: proceeding with the

Re: non portable sed scripts

On Fri, 19 May 2006, Ralf Wildenhues wrote: > Hi Tim, > > * Tim Rice wrote on Fri, May 19, 2006 at 06:57:48PM CEST: > > > > Autoconf version 2.59c > > > > I had an opportunity to run a configure script generated with 2.59c > > (ftp://ftp.gnu.org/gnu/coreutils/coreutils-5.95.tar.gz) and found >

Re: non portable sed scripts

* Ralf Wildenhues wrote on Fri, May 19, 2006 at 08:42:46PM CEST: > > > > I'm pretty sure the syntax of the sed script is ok. It's probably that > > your sed has a length restriction. Well, Autoconf-2.59 has been using 38 lines per here document: | # Maximum number of lines to put in a shell here

fetchmail-6.2.5 solaris 8 GNUCC

checking resolv.h presence... yes configure: WARNING: resolv.h: present but cannot be compiled configure: WARNING: resolv.h: check for missing prerequisite headers? configure: WARNING: resolv.h: proceeding with the preprocessor's result configure: WARNING: ## -

two host environments

Hello, In the newer version of GRUB, I've beein using autoconf in a tricky way. We aim at building tools which run on an operating system (such as an installer) as well as building binary images/files which run on a boot environment (such as a boot sector). GRUB wants to support that the user c

Re: Bug#368012: mingw crosscompilation broken with autoconf-2.59.cvs.2006.05.13-1

Re , Ralf Wildenhues <[EMAIL PROTECTED]> writes: > http://lists.gnu.org/archive/html/autoconf-patches/2006-04/msg00027.html > ... broke this. > > I'm still wondering whether we should just simply revert both patches, > ... and leave a cleanu

Re: non portable sed scripts

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > We check the 99 commands limit, but > not the [4000] characters limit any more... :-/ But the 4000-character limit is documented by Autoconf to be a limit on the length of lines of sed's input data, not a limit on the total size of the sed script. H

Re: Bug#368012: mingw crosscompilation broken with autoconf-2.59.cvs.2006.05.13-1

[ Cc:ing bug-autoconf as this is a genuine bug IMHO. ] Hi Tim, Thanks for reporting this! * Tim Kosse wrote on Fri, May 19, 2006 at 10:56:01AM CEST: > Package: autoconf > Version: 2.59.cvs.2006.05.13-1 > Severity: important > > If crosscompiling an autotools based package with mingw for Windows

Re: non portable sed scripts

Thanks for the bug report. I suspect that the sed usage is portable but that we are running into some limitation of your 'sed' implementation. Here is some further information that you can send that will help us debug this. (I don't have access to your platform so I can't debug the problem direc

Re: non portable sed scripts

* Ralf Wildenhues wrote on Fri, May 19, 2006 at 08:37:06PM CEST: > * Tim Rice wrote on Fri, May 19, 2006 at 06:57:48PM CEST: > > > > Autoconf version 2.59c > > config.status: creating config.h > > UX:sed: ERROR: Command garbled: HAVE_DECL_STRNDUP\)[ > > (].*$,\1define\2 0 , > > I'm pret

Re: non portable sed scripts

Hi Tim, * Tim Rice wrote on Fri, May 19, 2006 at 06:57:48PM CEST: > > Autoconf version 2.59c > > I had an opportunity to run a configure script generated with 2.59c > (ftp://ftp.gnu.org/gnu/coreutils/coreutils-5.95.tar.gz) and found > that it failed. > config.status: creating config.h > UX:sed:

Re: getloadavg module broken

Jim Meyering wrote: > That is because it's looking in the wrong place. > This patch fixes the immediate problem Indeed, thanks. But the bug is really in the AC_FUNC_GETLOADAVG macro in autoconf. The macros AC_FUNC_ERROR_AT_LINE, AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK, AC_FUNC_MALLOC, AC_FU

Re: [GNU Autoconf 2.59d] testsuite: 202 failed

Hi Paul, * Paul Eggert wrote on Fri, May 19, 2006 at 06:15:11AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> writes: > > > you need a different method in the config.status code to > > detect whether you need to munge with $MKDIR_P for subdirectories, > > Thanks for explaining that, and for the te