* Stepan Kasal wrote on Tue, May 23, 2006 at 02:18:37PM CEST:
The limit for record size means that no line nor substituted value
can be bigger than 3K on OSR5. I think that is a reasonable limit.
Do you?
$ cd coreutils/build-cvs
$ grep @LIBOBJS config.status | wc
1 1042634
I wrote:
I've just checked in the following change.
It made it so coreutils-5.96 uses the lib/lstat.c wrapper
when it shouldn't (e.g., w/linux) and doesn't when it should.
2006-05-23 Jim Meyering [EMAIL PROTECTED]
* lib/autoconf/functions.m4 (AC_FUNC_LSTAT_FOLLOWS_SLASHED_SYMLINK):
Ralf Wildenhues [EMAIL PROTECTED] writes:
the 2.59 shell selection algorithm would probably(?) have selected
/bin/sh as shell, whereas, due to changes we did because of OSF,
/usr/bin/posix/sh is preferred now.
Ouch. Good catch.
I hope we get away with this.
I don't think we will, since
Hi Michael,
* Michael B Allen wrote on Tue, May 23, 2006 at 12:33:02AM CEST:
If I have a check for libfoo and it depends on forkpty how do I
conditionally include -lutil in the test? Is there a builtin mechanism
for handling this?
Yes. Something like this:
my_LIBS=$LIBS
LIBS=-lutil $LIBS
Hello,
Thanks for the report.
* Holly Marie Schöne wrote on Mon, May 22, 2006 at 11:17:09PM CEST:
I just tried to install autoconf on my machine and got the following:
These tests all fail because they don't find a C compiler. If you don't
have a C compiler, please install one. Autoconf
Ralf Wildenhues wrote, quoting me:
Isn't it likely that, the problem here is that parameters cannot be
passed to an AC_REQUIREd macro?
That is not strictly true. It'd undocumented (and as such you shouldn't
rely on it), but you can
AC_REQUIRE([FOO], [FOO([arg])])
Hmm. Autoconf 2.59
Ralf Wildenhues wrote, quoting me:
That is not strictly true. It'd undocumented (and as such you
shouldn't rely on it), but you can
AC_REQUIRE([FOO], [FOO([arg])])
...
This suggested usage isn't simply undocumented; it actually conflicts
with explicitly documented behaviour. Even if
Hello,
On Tue, May 23, 2006 at 07:08:43PM +0200, Ralf Wildenhues wrote:
Regarding this: (info Autoconf Limitations of Usual Tools):
| Portable `sed' regular expressions should use `\' only to escape
| characters in the string `$()*.0123456789[\^n{}'. For example,
| alternation, `\|', is
Hi Stepan,
* Stepan Kasal wrote on Tue, May 23, 2006 at 08:42:34PM CEST:
On Tue, May 23, 2006 at 07:08:43PM +0200, Ralf Wildenhues wrote:
Conversely to the second half of the paragraph, can we be certain that
sed 's|a\|b||'
does what I think it should do, namely remove a literal
Hi all,
I'm trying to use libtool so that it links all libraries as static so
I added to configure.ac: AC_DISABLE_SHARED before AC_PROG_LIBTOOL
and I added the libraries (*.la files) I wanted to link in Makefile.am LDADD.
but still, it is linking all the librares as shared.
Any ideas on what's
Hi Paulo,
* Paulo J. Matos wrote on Tue, May 23, 2006 at 09:32:46PM CEST:
I'm trying to use libtool so that it links all libraries as static so
I added to configure.ac: AC_DISABLE_SHARED before AC_PROG_LIBTOOL
and I added the libraries (*.la files) I wanted to link in Makefile.am
LDADD.
On Mon, May 22, 2006 at 02:13:26PM -0400, Bob Rossi wrote:
Hi,
Does anyone know if bison generated files typically get checked into the
source repository, and build system the same way flex generated files
are? That way, other developers or users do not need bison installed if
they do not
Bob Rossi [EMAIL PROTECTED] writes:
Does anyone know if bison generated files typically get checked into the
source repository, and build system the same way flex generated files
are? That way, other developers or users do not need bison installed if
they do not change the bison grammar
On Tue, May 23, 2006 at 04:48:56PM -0700, Paul Eggert wrote:
Bob Rossi [EMAIL PROTECTED] writes:
Does anyone know if bison generated files typically get checked into the
source repository, and build system the same way flex generated files
are? That way, other developers or users do not
Hi Bob,
* Bob Rossi wrote on Wed, May 24, 2006 at 01:51:01AM CEST:
Does 'make dist' automatically include them in the distro though?
Yes. info Automake Yacc and Lex
Cheers,
Ralf
___
Autoconf mailing list
Autoconf@gnu.org
[ better keep the debian bug address in Cc: ]
* Ben Pfaff wrote on Tue, May 23, 2006 at 01:34:18AM CEST:
The configure script from the CVS autoconf did report warnings
for the lack of datarootdir. This appears to be harmless. The
two versions of configure generated identical config.h,
[ Cc:ing bug-autoconf again ]
* Tim Rice wrote on Tue, May 23, 2006 at 04:13:34AM CEST:
On Mon, 22 May 2006, Ralf Wildenhues wrote:
Next I tried
CONFIG_SHELL=/bin/sh /bin/sh \
/opt/src/gnu/coreutils-5.95/configure \
CONFIG_SHELL=/bin/sh
Again a valid config.h and
Hello,
On Tue, May 23, 2006 at 10:43:22AM +0200, Ralf Wildenhues wrote:
| s,^\([ ]*#[]*\)[^ ]*\([ ][ ]*HAVE_DECL_NANOSLEEP\)[
(].*$,\1define\2 0 ,
| s,^\([ ]*#[]*\)[^ ]*\([ ][ ]*HAVE_DECL_REALLOC\)[
(].*$,\1define\2 1 ,
| s,^\([ ]*#[
Hello,
On Tue, May 23, 2006 at 02:33:42PM +0200, Stepan Kasal wrote:
you are so bright, Ralf!
this doesn't sound nice, I'm afraid.
I wanted to say that it was realy clever to notice that
| s,^\([ ]*#[]*\)[^ ]*\([ ][ ]*HAVE_DECL_STPCPY\)[
(].*$,\1define\2 0 ,
|
Ralf Wildenhues [EMAIL PROTECTED] writes:
the 2.59 shell selection algorithm would probably(?) have selected
/bin/sh as shell, whereas, due to changes we did because of OSF,
/usr/bin/posix/sh is preferred now.
Ouch. Good catch.
I hope we get away with this.
I don't think we will, since
20 matches
Mail list logo
