Jim Meyering [EMAIL PROTECTED] writes:
Anyway, I installed this patch into coreutils. Can you please try it
with your GCC? If it pacifies your GCC I'll propagate it into gnulib
and glibc.
It does. Thanks!
OK, I installed it. I also started the ball rolling on propagating
the changes
[ this thread starts at
http://lists.gnu.org/archive/html/libtool/2005-06/msg00169.html ]
Hi Sven, others,
* Sven Verdoolaege wrote on Thu, Jun 23, 2005 at 09:11:36AM CEST:
On Thu, Jun 23, 2005 at 08:31:48AM +0200, Ralf Wildenhues wrote:
It's this version that fails on solaris.
Let's
Paul Eggert [EMAIL PROTECTED] wrote:
It will take a while for this fix to propagate, though. In the
meantime, why not modify the definition of xalloc_oversized(n,s) to
always return 0 if if s is a constant and if the size of n is such
that the comparison cannot possibly fail. Something like
I noticed the following disagreement between gnulib and coreutils:
--- gnulib/lib/canon-host.c 2005-05-13 23:03:57 -0700
+++ cu/lib/canon-host.c 2005-05-14 00:58:06 -0700
@@ -54,8 +54,9 @@ canon_host (char const *host)
#if HAVE_GETADDRINFO
{
-struct addrinfo hint = { 0 };
+
Here are rms's comments on our draft about the quote character stuff.
1) I don't know how to address his problem with domain at hand, please help?
2) I hope that if I point the preferably, and that gcc is using
'...', and that the rest of the world thinks ' is the standard, he
will let the
Derek Price [EMAIL PROTECTED] writes:
Do you want me to keep sending FYI's to this list for this sort of minor
change?
Yes, please.
___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib
[EMAIL PROTECTED] (Karl Berry) writes:
Here are rms's comments on our draft about the quote character stuff.
1) I don't know how to address his problem with domain at hand, please help?
How about changing this:
Sticking to the ASCII character set (plain text, 7-bit characters) is
