Hello,
Patch 2.6.1 fails to build on Darwin with Apple’s “GCC” [0]:
--8---cut here---start-8---
gcc -std=gnu99 -c -DHAVE_CONFIG_H
-Ded_PROGRAM=\/nix/store/1dk6yj85f9j1manfrd3001az2r7ggb8n-ed-1.4/bin/ed\
-DENABLE_MERGE -I. -I./src -I./gl/lib -g -O2 -o
According to Bruno Haible on 1/9/2010 8:53 AM:
Eric Blake wrote:
Here's spin two of the patch.
[PATCH 1/4] warn-on-use: new module
...
+ supported by the compiler. If the compiler does not support this
+ feature, the macro expands to an unused typedef declaration.
It's now an
This new warning is debatable:
utimecmp.c: In function 'utimecmp':
utimecmp.c:222:36: error: comparison between 'enum anonymous' and 'enum
anonymous' [-Wenum-compare]
The code in question:
enum { BILLION = 1000 * 1000 * 1000 };
/* Best possible resolution that utimens can set and
Eric Blake ebb9 at byu.net writes:
Here's spin two of the patch. It turns out that doing one shell loop per
header also allows us to fold in platform-specific inclusion requirements.
...
Some of our unit tests never use large files, so rather than drag
in a dependency on fseeko, they
Pádraig Brady wrote:
Here's a proposed patch.
Looks good.
OK, I've applied it now.
Bruno
Hi Bruno and Eric,
Considering the coreutils-8.3 build failures, I'm going to release
coreutils-8.4 soon, perhaps on Wednesday. A cursory review and
preliminary testing suggests that it will be safe to use the latest
from gnulib. Since you two have made relatively large changes recently,
what
Ludovic Courtès ludo at gnu.org writes:
Patch 2.6.1 fails to build on Darwin with Apple’s “GCC” [0]:
--8---cut here---start-8---
gcc -std=gnu99 -c -DHAVE_CONFIG_H
-Ded_PROGRAM=\/nix/store/1dk6yj85f9j1manfrd3001az2r7ggb8n-ed-1.4/bin/ed\ -
DENABLE_MERGE
Hi Jim,
Since you two have made relatively large changes recently,
what do you think of using the latest in a bug-fix-only coreutils release?
The changes between commit 7a29e0093f4a87478cdf7b7c87786272d6f37dfe and today
look reasonably safe. Most of new the libunistring tests won't affect
Eric Blake e...@byu.net writes:
According to Simon Josefsson on 1/9/2010 4:06 AM:
There is another dup2 failure due to Wine, see:
http://bugs.winehq.org/show_bug.cgi?id=21291
The patch below works around it. Thoughts?
Hmm. Repeatedly adding workarounds for wine bugs seems awkward. If
Bruno Haible br...@clisp.org writes:
The relevant code is:
/* Cannot create directory. */
errno = 0;
ASSERT (func (nonexist.ent/, O_CREAT | O_RDONLY, 0600) == -1);
Open returns 3 for me, and it has created a file 'nonexist.ent'.
This must be a bug in Wine, then. Please report
Paolo Bonzini bonz...@gnu.org writes:
On 01/09/2010 12:33 PM, Bruno Haible wrote:
Hmm, you and Paolo explained to me on 2009-08-21 that Wine should be
considered as a platform of its own. But I still don't fully agree. Can
you first report the bug to the Wine people and come back to patching
Hi,
I've released a new stable snapshot. See attached NEWS.stable for details.
Feedback welcome.
Tarball: http://erislabs.net/ianb/projects/gnulib/gnulib-20100109-stable.tar.gz
Gitweb: http://erislabs.net/gitweb?p=gnulib.git;a=shortlog;h=refs/heads/stable
Git: git://erislabs.net/gnulib.git
On Mon, Jan 11, 2010 at 10:25:53PM +0100, Jim Meyering wrote:
Considering the coreutils-8.3 build failures, I'm going to release
coreutils-8.4 soon, perhaps on Wednesday. A cursory review and
preliminary testing suggests that it will be safe to use the latest
from gnulib. Since you two have
Bison currently contains a wrapper around mbsnwidth to compute screen
columns while accounting for tabs. Based on Bison's ChangeLog, the
wrapper was originally written by Paul Eggert.
I'd like to use this wrapper in other projects, so I thought it would be
nice to generalize it a little and
Ian Beckwith wrote:
On Mon, Jan 11, 2010 at 10:25:53PM +0100, Jim Meyering wrote:
Considering the coreutils-8.3 build failures, I'm going to release
coreutils-8.4 soon, perhaps on Wednesday. A cursory review and
preliminary testing suggests that it will be safe to use the latest
from gnulib.
Bruno Haible wrote:
Since you two have made relatively large changes recently,
what do you think of using the latest in a bug-fix-only coreutils release?
The changes between commit 7a29e0093f4a87478cdf7b7c87786272d6f37dfe and today
look reasonably safe. Most of new the libunistring tests
16 matches
Mail list logo
