Re: coreutils 6.6 HP-UX build error

2007-01-04 Thread Matthew Woehlke
Bob Proulx wrote: Matthew Woehlke wrote: The OS is 11.00, and I can't tell about the compiler ('cc -v' is giving some odd output but no version number). Because of historical legacy most of the HP-UX programs report version information using SCCS what strings. Running 'what' on binary is the

Re: coreutils 6.6 fails to compile on IRIX 5.3

2007-01-04 Thread Paul Eggert
Thanks for checking it. Can you please try the enclosed wctype_.h instead? (You may need to do a 'make clean' first.) This is a bit more drastic, but I think it's more likely to compile and link on IRIX 5.3. Thanks. /* A substitute for ISO C99 , for platforms that lack it. Copyright (C) 20

Re: clean-temp and large files

2007-01-04 Thread Paul Eggert
Eric Blake-1 <[EMAIL PROTECTED]> writes: > Should we just make GL_EARLY always invoke AC_SYS_LARGEFILE, so > that any application that uses gnulib automatically also supports large > files? Won't that be overkill for applications (probably libraries) that don't do any file I/O? 'configure' is bl

Re: Autobuild of gnulib

2007-01-04 Thread Bruno Haible
Simon Josefsson writes: > Btw, does anyone know why --create-testdir runs ./configure + make > distclean? It does it when the gllib/ directory contains built sources. A possible and worthy optimization would be to do it only if it contains built sources that are not listed in MOSTLYCLEANFILES, C

Re: clean-temp and large files

2007-01-04 Thread Eric Blake-1
> > I was assuming that invoking AC_SYS_LARGEFILE is the programmer's > > responsibility, because AC_SYS_LARGEFILE is a global switch. > > Yes, that was my assumption too. However, as you mentioned, any > portable program that accesses files should use AC_SYS_LARGEFILE these > days. Should we j

wctype.h port to IRIX 5.3

2007-01-04 Thread Paul Eggert
I installed this to make it easier to port wctype.h to IRIX 5.3. 2007-01-04 Paul Eggert <[EMAIL PROTECTED]> * lib/wctype_.h (_ctmp_) [HAVE_WCTYPE_CTMP_BUG]: Now of type wchar_t, not wint_t. Also, include , to fix another IRIX bug. * m4/wctype.m4 (gl_WCTYPE_H): Likewise.

Re: declaring only the functions that are defined

2007-01-04 Thread Paul Eggert
"Bruno Haible" <[EMAIL PROTECTED]> writes: >> For the special case of nanosleep, one might want nanosleep declared >> even if the nanosleep module isn't being used, for the benefit of >> hosts that define nanosleep but don't declare it. > > Huh? If the program uses nanosleep(), it needs the gnulib

Re: clean-temp and large files

2007-01-04 Thread Paul Eggert
"Bruno Haible" <[EMAIL PROTECTED]> writes: > I was assuming that invoking AC_SYS_LARGEFILE is the programmer's > responsibility, because AC_SYS_LARGEFILE is a global switch. Yes, that was my assumption too. However, as you mentioned, any portable program that accesses files should use AC_SYS_LAR

Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."

2007-01-04 Thread Richard Sandiford
"Richard Guenther" <[EMAIL PROTECTED]> writes: > On 1/4/07, Richard Sandiford <[EMAIL PROTECTED]> wrote: >> Paul Eggert <[EMAIL PROTECTED]> writes: >> > Mark Mitchell <[EMAIL PROTECTED]> writes: >> >> it sounds like that would eliminate most of the problem. Certainly, >> >> making -INT_MIN evaluat

Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."

2007-01-04 Thread Richard Sandiford
Paul Eggert <[EMAIL PROTECTED]> writes: > Mark Mitchell <[EMAIL PROTECTED]> writes: >> it sounds like that would eliminate most of the problem. Certainly, >> making -INT_MIN evaluate to INT_MIN, when expressed like that, is an >> easy thing to do; that's just a guarantee about constant folding. >

Re: coreutils bootstrapping issue on non-GNU platforms

2007-01-04 Thread Paul Eggert
"James Youngman" <[EMAIL PROTECTED]> writes: > Doesn't the previous code actually produce the _maximum_ version (that > is, with sort .. | tail -1)? Yes, and thanks for catching that. Hmm, nobody has used this since December 30? Anyway, I installed this: 2007-01-04 Paul Eggert <[EMAIL PROTEC

Re: re_compile_pattern change

2007-01-04 Thread Paul Eggert
"James Youngman" <[EMAIL PROTECTED]> writes: > I'll consider myself notified.Apart from that bugfix are there any > other essential changes I should import, or are you suggesting I > update the whole of gnulib to current CVS? Generally speaking, I find it easiest just to sync all of gnulib. T

Re: Autobuild of gnulib

2007-01-04 Thread Simon Josefsson
Simon Josefsson <[EMAIL PROTECTED]> writes: > Btw, does anyone know why --create-testdir runs ./configure + make > distclean? I'd rather remove that step, since it constitute a > noticeable part of the total build time. The code snippet that does > the step is: > > if grep '^BUILT_SOURCES *+='

Re: declaring only the functions that are defined

2007-01-04 Thread Simon Josefsson
"Bruno Haible" <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> I know gnulib never promised to provide code that worked without the >> gnulib-tool machinery, but previously the tweaks to make that work >> anyway was small. Now they are larger. Before, you'd typically only >> have to copy

Re: gnulib-tool: indicating the presence of gnulib modules

2007-01-04 Thread Bruno Haible
Eric Blake writes: > > In the presence of multiple gnulib-tool invocations from the same directory > > with the same configure.ac file, such macros may indicate the wrong thing > > (because if you build libgnuA.a and libgnuB.a, the module may be compiled > > into libgnuA but not into libgnuB). But

Re: declaring only the functions that are defined

2007-01-04 Thread Bruno Haible
Simon Josefsson wrote: > I know gnulib never promised to provide code that worked without the > gnulib-tool machinery, but previously the tweaks to make that work > anyway was small. Now they are larger. Before, you'd typically only > have to copy the source code and the M4 files, and arrange for

Re: declaring only the functions that are defined

2007-01-04 Thread Bruno Haible
Paul Eggert wrote: > I'm a bit dubious about this one, as it adds to the .h maintenance > burden and I'm not sure the benefit is worth the cost. > ... > The other parts I'm ambivalent about. So let's drop the idea. I was hesitating too. > For the special case of nanosleep, one might want nanoslee

Re: clean-temp and large files

2007-01-04 Thread Bruno Haible
Eric Blake wrote: > Is there any reason that using the clean-temp module does not AC_REQUIRE > ([AC_SYS_LARGEFILE]) in the configure script? Without that, it is possible > on some hosts that temporary files are artificially capped at 2GiB, even > though enabling largefile support could make things

Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."

2007-01-04 Thread Richard Guenther
On 1/4/07, Richard Sandiford <[EMAIL PROTECTED]> wrote: "Richard Guenther" <[EMAIL PROTECTED]> writes: > On 1/4/07, Richard Sandiford <[EMAIL PROTECTED]> wrote: >> Paul Eggert <[EMAIL PROTECTED]> writes: >> > Mark Mitchell <[EMAIL PROTECTED]> writes: >> >> it sounds like that would eliminate most

Re: base64.c vs. newlines

2007-01-04 Thread Simon Josefsson
Jim Meyering <[EMAIL PROTECTED]> writes: > In the mean time -- sometimes it's easier to review things > when they're checked in... Thanks! I hope to review it soon. Sorry about the delay on this... I'm still catching up many things after an almost one-month vacation. /Simon

Re: re_compile_pattern change

2007-01-04 Thread James Youngman
On 12/25/06, Paul Eggert <[EMAIL PROTECTED]> wrote: The 'tar' version is correct. But this is not an Autoconf issue; it is a gnulib version issue. The gnulib fix (dated March 25) is here: http://cvs.savannah.gnu.org/viewcvs/gnulib/gnulib/m4/regex.m4?r1=1.50&r2=1.51 but apparently findutils is

Re: changing "configure" to default to "gcc -g -O2 -fwrapv ..."

2007-01-04 Thread Richard Guenther
On 1/4/07, Richard Sandiford <[EMAIL PROTECTED]> wrote: Paul Eggert <[EMAIL PROTECTED]> writes: > Mark Mitchell <[EMAIL PROTECTED]> writes: >> it sounds like that would eliminate most of the problem. Certainly, >> making -INT_MIN evaluate to INT_MIN, when expressed like that, is an >> easy thing

Re: base64.c vs. newlines

2007-01-04 Thread Jim Meyering
Jim Meyering <[EMAIL PROTECTED]> wrote: > For your reviewing fun, I've included both the gnulib parts > and the coreutils parts: > > [gnulib] > 2007-01-03 Jim Meyering <[EMAIL PROTECTED]> > > When decoding, always allow newlines in input, with almost no > performance impact. > *

CVS statistics for gnulib

2007-01-04 Thread Simon Josefsson
Hi all! I run statcvs on most of my projects, and I thought I could run it for gnulib as well. Starting today, the following URL will hopefully be updated with fresh statistics about gnulib CVS: http://josefsson.org/gnulib/statcvs/ Enjoy, Simon

Re: make safe_read usable in a mixed C/C++ build

2007-01-04 Thread Lorenzo Bettini
Bruno Haible wrote: > Eric Blake asked: >> Is it also necessary to wrap safe-read.c with extern "C", for use when >> using g++ as a type-safe variant of a C compiler, to match the header? > > Normally not. The 'extern "C"' is only needed in mixed C/C++ builds. > >> And should you be symmetric wit

Re: unicode string functions

2007-01-04 Thread Simon Josefsson
"Bruno Haible" <[EMAIL PROTECTED]> writes: > Simon Josefsson wrote: >> > unicasecase folding >> >> Is this NFKC? > > I didn't consider normalization functions so far, on the premise that text > being exchanged between applications is assumed to be precomposed. > But their presence in Java AP