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,
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: ERROR:
* 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 pretty sure the
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
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.
Re http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368012,
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 cleanup of
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
