Hello Paul,
* Paul Eggert wrote on Wed, Oct 25, 2006 at 12:34:02AM CEST:
> I installed this into gnulib, since I think other modules can use it:
[...]
> +
> +AC_DEFUN([AC_C_VARARRAYS],
> +[
> + AC_CACHE_CHECK([for variable-length arrays],
> +ac_cv_c_vararrays,
This uses Autoconf name space f
Karl Berry wrote:
> Is supporting compilation with C++ of interest? (I'm not arguing for
> it, just reporting it, since Nelson went to the trouble of trying it.)
My opinion (which counts for very little here) is that while C++ is
designed to be as close to C as possible, but no closer, that it is
[EMAIL PROTECTED] (Karl Berry) writes:
> Is supporting compilation with C++ of interest?
Not in general. Coreutils, for example, generates about 400 lines worth
of diagnostics when compiled using g++ 4.1.1. This explains the quotearg
problems you mentioned: quotearg doesn't attempt to be portab
I installed this into gnulib, since I think other modules can use it:
2006-10-24 Paul Eggert <[EMAIL PROTECTED]>
* modules/vararrays: New file.
* m4/vararrays.m4: New file, taken from diffutils.
* MODULES.html.sh: New module vararrays.
Index: MODULES.html.sh
===
Paul Eggert <[EMAIL PROTECTED]> wrote:
> Thanks for catching those. I prefer the 'const' after the type that
> it modifies, so I installed the following into gnulib. (For coreutils
> I guess I need to come up to speed on its new version control system.)
No rush. I'm looking at them now.
I committed this.
Cheers,
Ralf
2006-10-24 Ralf Wildenhues <[EMAIL PROTECTED]>
* users.txt: Add Libtool.
Index: users.txt
===
RCS file: /cvsroot/gnulib/gnulib/users.txt,v
retrieving revision 1.10
diff -u -r1.10 users.txt
-
* Ralf Wildenhues wrote on Sat, Oct 14, 2006 at 12:24:52PM CEST:
> * Paul Eggert wrote on Fri, Oct 13, 2006 at 12:01:16AM CEST:
>
> > If there are actual projects that don't use AC_CONFIG_HEADERS then of
> > course we have to be cautious about assuming config-h. But if not,
> > then why wouldn't
Hi,
On MacOS X 10.2 (Darwin 6.x), wcwidth.h gives a compilation error, because
wint_t is not defined. All other uses of wint_t in gnulib are protected by
HAVE_WCHAR_H or HAVE_WINT_T, only this one is missing the check. I'm applying
this:
2006-10-24 Bruno Haible <[EMAIL PROTECTED]>
* mo
I asked Nelson to try compiling hello on his array of systems, which he
graciously did. It basically went fine, and then he went further and tried
compiling it with C++ compilers. The hello code itself is so simple it
is no problem, but there are a variety of syntax errors in various
gnulib modul
These were a little more than Texinfo niglets:
Your definition and my definition obviously vary. Sorry.
American typography probably does it differently than European typography.
Indeed, spaces around dashes is an American/European difference.
(Sometimes I use thinspaces, but that's not
Paul Eggert wrote:
Does this include all the patches that have been flying around for NSK?
I've been meaning to apply those, but between some in gnulib, some in
coreutils, and some that need manual filtering to apply at all, I
haven't gotten to it.
That release includes a snapshot of gnulib stat
Thanks for catching those. I prefer the 'const' after the type that
it modifies, so I installed the following into gnulib. (For coreutils
I guess I need to come up to speed on its new version control system.)
2006-10-24 Paul Eggert <[EMAIL PROTECTED]>
* lib/getdate.y (yyerror): Make t
>> Does this include all the patches that have been flying around for NSK?
>> I've been meaning to apply those, but between some in gnulib, some in
>> coreutils, and some that need manual filtering to apply at all, I
>> haven't gotten to it.
>
> That release includes a snapshot of gnulib state from
[EMAIL PROTECTED] (Karl Berry) wrote:
> When I run MODULES.html.sh now, I get the following msg (several times):
>
> gnulib-tool: module uinttostr doesn't exist
That was my doing. Fixed.
* MODULES.html.sh: Remove uinttostr. It's not a module.
Reported by Karl Berry.
Index: MODU
When I run MODULES.html.sh now, I get the following msg (several times):
gnulib-tool: module uinttostr doesn't exist
Help?
Bruno Haible wrote:
> Karl Berry wrote:
> > -it works on Unix and Windows
> > +it works on GNU/Unix and Windows
>
> Now this is ridiculous. Do you consider a Solaris or a Tru64 system a
> "GNU/" system?
No, I consider those a Unix system, or at least a Unix-like system.
The Unix part would have d
Just fixed this.
2006-10-24 Bruno Haible <[EMAIL PROTECTED]>
* lib/gl_list.h: Use C comment style, not C++ comment style.
*** lib/gl_list.h 6 Oct 2006 12:06:07 - 1.3
--- lib/gl_list.h 24 Oct 2006 13:23:28 -
***
*** 360,366
struct gl_list_
Eric Blake wrote:
> But texinfo documents that using '---' without surrounding spaces is the
> correct way to typeset an mdash, which is exactly the punctuation you want
> here.
Here's what I get:
Input: '---' ' --- '
Output in .info:'--'
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Compiling coreutils-6.4 with gcc-4.1 and
>
> ./configure --prefix=/packages/gnu \
> CPPFLAGS="-Wall -Wformat=2 -Wmissing-field-initializers
> -Wmissing-format-attribute -Wpointer-arith -Wstrict-aliasing=2
> -Wwrite-strings" \
> CFLAGS="-O2 -g -Wbad-fu
Hi,
Compiling coreutils-6.4 with gcc-4.1 and
./configure --prefix=/packages/gnu \
CPPFLAGS="-Wall -Wformat=2 -Wmissing-field-initializers
-Wmissing-format-attribute -Wpointer-arith -Wstrict-aliasing=2 -Wwrite-strings"
\
CFLAGS="-O2 -g -Wbad-function-cast -Wdeclaration-after-statement"
yiel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 10/24/2006 6:19 AM:
>> +glibc--examples: @samp{getopt}, @samp{fnmatch}---and often new
>> +APIs---for example, for all functions that allocate memory in one way
>> +or the other, we have variants which also include the erro
Karl Berry wrote:
> I fixed a few Texinfo niglets.
ChangeLog entry? Diffs to this mailing list?
These were a little more than Texinfo niglets:
> @@ -144,18 +146,18 @@
> @subsection Enhancements of ISO C or POSIX functions
>
> These are sometimes POSIX functions with GNU extensions also found
22 matches
Mail list logo
