hggdh wrote:
...
> Thank you, both Eric and Andreas.
>
> I guess, then, it would be correct to update the references to
> automake in README-{prereq|hacking}, and to update bootstrap.conf.
>
> Patch attached. Please keep in mind this is my first one following the
> rules -- I may have made some mis
Ralf Wildenhues wrote:
> Hi Paul, all,
> Paul Eggert writes:
>>
>> This patch is by Glen Lenker, Matt Pham, Benjamin Nuernberger, Sky
>> Lin, TaeSung Roh, and Paul Eggert. It adds support for parallelism
>> within an internal sort. On our simple tests on a 2-core desktop x86,
>> overall performan
Jim Meyering wrote:
> diff --git a/README-prereq b/README-prereq
> -$ cd automake && ./configure --prefix=$HOME/coreutils/deps
> +$ cd automake
> +$ git checkout --track origin/next -b next
> +$ ./configure --prefix=$HOME/coreutils/deps
I needed to switch the git checkout paramete
Pádraig Brady wrote:
> Jim Meyering wrote:
>
>> diff --git a/README-prereq b/README-prereq
>> -$ cd automake && ./configure --prefix=$HOME/coreutils/deps
>> +$ cd automake
>> +$ git checkout --track origin/next -b next
>> +$ ./configure --prefix=$HOME/coreutils/deps
>
> I needed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[please post with a valid email address]
According to dae3 on 4/1/2009 2:56 PM:
> Eric Blake wrote:
>
>> [moving to bug-coreutils, which is the address listed in tail --help]
>
> Thank you for reposting to the appropriate place. Unfortunately, it
>
Eric Blake wrote:
> Wrong patch?
definitely ;-) thanks
___
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 4/2/2009 5:44 AM:
>> git checkout -b next --track origin/next
>
> Thanks.
> How about this?
>
>>From b1332b9b429dfa9a8bba7286a78bbc7e37a2e419 Mon Sep 17 00:00:00 2001
> From: Jim Meyering
> Date: Thu, 2 Apr 2009 12:35:08
Steven Schveighoffer wrote:
> Follow-up Comment #4, patch #6797 (project coreutils):
>
> Thanks for the suggestion, but I really don't understand the reluctance to
> utilize the (already implemented) internal random number generator. It's
> there, it costs nothing extra to use it, it doesn't requ
Pádraig Brady wrote:
> Steven Schveighoffer wrote:
>> Follow-up Comment #4, patch #6797 (project coreutils):
>>
>> Thanks for the suggestion, but I really don't understand the reluctance to
>> utilize the (already implemented) internal random number generator. It's
>> there, it costs nothing extra
> From: Jim Meyering
> Pádraig Brady wrote:
> > Steven Schveighoffer wrote:
> >> Follow-up Comment #4, patch #6797 (project coreutils):
> >>
> >> Thanks for the suggestion, but I really don't understand the reluctance to
> >> utilize the (already implemented) internal random number generator.
Just a quick follow up to this now archived bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472590
The last message there mentioned selinux query overhead.
On my system with selinux disabled, there is currently
a significant overhead in doing the selinux lookup per file
with a standard `ls -
I installed the following into gnulib; it fixes a problem that
causes the build of coreutils 7.2 to fail on Solaris 8.
* modules/fnmatch (Depends-on): Add mbsrtowcs, to fix a porting
problem to Solaris 8 encountered with coreutils 7.2, which
resulted in a message "fnmatch.c:292: warning: passing
I installed the following patch to gnulib, to fix the following
symptoms when trying to build coreutils 7.2 on Solaris 8:
inet_ntop.c:73: error: conflicting types for 'inet_ntop'
/usr/include/arpa/inet.h:55: error: previous declaration of 'inet_ntop' was here
make[4]: *** [inet_ntop.o] Error 1
--
>> Paul Eggert writes:
>>>
>>> This patch is by Glen Lenker, Matt Pham, Benjamin Nuernberger, Sky
>>> Lin, TaeSung Roh, and Paul Eggert. It adds support for parallelism
>>> within an internal sort. On our simple tests on a 2-core desktop x86,
>>> overall performance improved by roughly a factor o
14 matches
Mail list logo