Gilles Espinasse wrote:
> It compile fine. I didn't look the result of tests.
> The problem stay un-noticed for some times until I was looking at the
> console screen during compilation.
So the only problem is that the configure test crashes? This is easy to
fix; I'm applying this patch:
2007-12-
On Thursday 13 December 2007, Eric Blake wrote:
> According to Gilles Espinasse on 12/12/2007 3:29 PM:
>
> Hi Gilles,
>
> > -- System Information:
> > Debian Release: 4.0
> > APT prefers stable
> > APT policy: (500, 'stable')
> > Architecture: amd64 (x86_64)
> > Shell: /bin/sh linked to /bin/b
- Original Message -
From: "Eric Blake" <[EMAIL PROTECTED]>
To: "Gilles Espinasse" <[EMAIL PROTECTED]>
Cc: ; "bug-gnulib" <[EMAIL PROTECTED]>
Sent: Friday, December 14, 2007 3:43 AM
Subject: Re: m4-1.4.10 segfault with x86_64 during .
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Gilles Espinasse on 12/12/2007 3:29 PM:
Hi Gilles,
> -- System Information:
> Debian Release: 4.0
> APT prefers stable
> APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Shell: /bin/sh linked to /bin/bash
> Kernel: Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tim Rice on 10/28/2007 7:15 PM:
>
> It looks like there are some regressions in 1.4.10 on some of my platforms.
Thanks for the report. Many of these issues have already been fixed in
gnulib, and will thus be in m4 1.4.11 when I release
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[redirecting to the list, so that others may see the resolution]
According to [EMAIL PROTECTED] on 8/10/2007 3:32 PM:
> Thanks for the quick reply, Eric.
>
>
> Turns out quad_t is defined as int64_t, which is not defined in that file.
>
> it's in "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[Adding bug-m4, since that is the list for M4 problems, and bug-gnulib,
since this particular problem comes from the gnulib file fseeko. Feel
free to drop bug-gnu-utils on replies]
According to Ancient_Hacker on 8/10/2007 11:02 AM:
> Hi, I'm trying t
On Jul 22, 2007, at 6:52 PM, Eric Blake wrote:
Hi Gary,
Hi Eric!
On Jul 22, 2007, at 12:27 AM, Eric Blake wrote:
This is the patch, I'm still working on a testsuite addition:
This bug seems to be present in HEAD too. If so, can you please
commit the
patch there too?
Done.
Excellen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Gary V. Vaughan on 7/22/2007 10:56 AM:
> Hi Eric,
Hi Gary,
>
> On Jul 22, 2007, at 12:27 AM, Eric Blake wrote:
>> This is the patch, I'm still working on a testsuite addition:
>>
>
> This bug seems to be present in HEAD too. If so, ca
Hi Eric,
On Jul 22, 2007, at 12:27 AM, Eric Blake wrote:
This is the patch, I'm still working on a testsuite addition:
2007-07-21 Eric Blake <[EMAIL PROTECTED]>
Fix failure on NetBSD.
* src/output.c (m4_tmpopen): Explicitly reset append-mode stream
position to byte 0.
On Sat, Jul 21, 2007 at 10:27:04PM -0600, Eric Blake wrote:
> Nevermind - I finally figured it out! POSIX states "a ``file position
> indicator'' associated with the stream is positioned at the start (byte
> number 0) of the file, unless the file is opened with append mode, in
> which case it is i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 7/21/2007 10:06 PM:
>
> I'm hoping that you can see the temporary files, and that the file sizes
> look reasonable (since I tested this on CVS head instead of 1.4.10, the
> numbers will be slightly different). At which poin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Klausner on 7/21/2007 3:47 PM:
> On Sat, Jul 21, 2007 at 10:23:44AM -0600, Eric Blake wrote:
>> Thanks. I need at least one more piece of information - could you send
>> the config.log created when you built m4-1.4.10 from the tarb
On Sat, Jul 21, 2007 at 10:23:44AM -0600, Eric Blake wrote:
> Thanks. I need at least one more piece of information - could you send
> the config.log created when you built m4-1.4.10 from the tarball?
Sure, attached.
Hope it helps,
Thomas
config.log.bz2
Description: Binary data
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Klausner on 7/21/2007 12:14 AM:
> I can reproduce this problem with m4's configure script.
> The file created by running 'autoconf' is just 35354 bytes long, while
> the one distributed with the m4-1.4.10 tarball is 647263.
The dif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Klausner on 7/21/2007 12:14 AM:
> On Fri, Jul 20, 2007 at 09:38:00PM -0600, Eric Blake wrote:
>> Thanks for the report. I have re-bootstrapped m4 1.4.10 with itself, and
>> didn't have any problems on my cygwin platform with the re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Klausner on 7/20/2007 5:05 PM:
> Hi!
>
> After the m4 update in pkgsrc there have been reports of breakage in
> packages where autoconf is run. In pkgsrc this affects e.g. mng,
> firefox, thunderbird and others.
Thanks for the rep
Bruno Haible schrieb:
Clemens Koller wrote:
m4-1.4.10 doesn't build anymore (1.4.9 built fine):
make[1]: Entering directory `/usr/ports/core/m4/work/src/m4-1.4.10/
src'
gcc -std=gnu99 -O2 -pipe -o m4 m4.o builtin.o debug.o eval.o
format.o freeze.o input.o macro.o output.o path.o symtab.o
Gary V. Vaughan schrieb:
Thanks for the bug report. I'm forwarding to the bug-m4 mailing list for
wider visibility.
Thanks.
This looks like a corner case for one of the files from gnulib that m4
imports during bootstrap: I'm forwarding to the bug-gnulib mailing list
too, so the author of th
Clemens Koller wrote:
> > m4-1.4.10 doesn't build anymore (1.4.9 built fine):
> >
> > make[1]: Entering directory `/usr/ports/core/m4/work/src/m4-1.4.10/
> > src'
> > gcc -std=gnu99 -O2 -pipe -o m4 m4.o builtin.o debug.o eval.o
> > format.o freeze.o input.o macro.o output.o path.o symtab.o
On Jul 13, 2007, at 12:22 PM, Clemens Koller wrote:
Hi, Gary!
Hi Clemens,
Thanks for the bug report. I'm forwarding to the bug-m4 mailing list
for
wider visibility.
This looks like a corner case for one of the files from gnulib that m4
imports during bootstrap: I'm forwarding to the bug-
21 matches
Mail list logo
