Re: getlogin_r.m4 and host_os.m4

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > * getlogin_r.m4 (gl_PREREQ_GETLOGIN_R): Require AC_GNU_SOURCE. > * host-os.m4 (gl_HOST_OS): Require AC_CANONICAL_HOST. The host-os.m4 change looks fine, but the getlogin_r.m4 change (adding AC_REQUIRE([AC_GNU_SOURCE])) looks a bit GNU-spec

Re: Fix chdir-long.m4 caching (was: megatest fallout)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 9/25/2006 2:03 PM: > Hello Jim, > >> 7 checking whether this system has an arbitrary file name length >> limit... yes > > OK to apply this patch? I think this variable isn't used elsewhere in > gnulib nor coreu

SIZE_MAX and gl_SIZE_MAX

Ralf Wildenhues <[EMAIL PROTECTED]> writes: > 21 checking for SIZE_MAX... yes > > as the top gnulib candidates. The SIZE_MAX test is cheap on systems > that have it There's no reason to have a separate SIZE_MAX module any more, except for inertia, as the stdint module should now do that for

Re: coreutils-6.2: various runtime problems on Darwin-8.7.0 HFS+ (including attachment this time)

[EMAIL PROTECTED] wrote: [let me see if gmane lets me reply to posts] gmane works great, it's the only way I read this list (and several others). :-) btw, thanks for the mails... I just built coreutils on Darwin also, and had a good number of 'make check' failures. I am also noticing that

Re: coreutils-6.2: various runtime problems on Darwin-8.7.0 HFS+ (including attachment this time)

[let me see if gmane lets me reply to posts] On 2006-09-25 08:10:03 -0500, Jim Meyering <[EMAIL PROTECTED]> said: <[EMAIL PROTECTED]> wrote: I am new to this list, but not at all new to building and using open source projects. (Please CC me if needed as I haven't yet joined this list. Or I

Re: speed up gnulib-tool a bit

Bruno Haible clisp.org> writes: > > > To be safe, I think you > > need to `exec <$file', or, restoring stdin, something like this: > > exec 5<&1 <$file > > while read r > > do > > $whatever > > done > > exec <&5 5<&- > > Astonishing. I never saw this kind of low-level shell progr

Re: Fix chdir-long.m4 caching

Ralf Wildenhues <[EMAIL PROTECTED]> wrote: >> 7 checking whether this system has an arbitrary file name length >> limit... yes > > OK to apply this patch? I think this variable isn't used elsewhere in > gnulib nor coreutils, so renaming this shouldn't be a problem. > > * chdir-long.m4

another warn case: intmax.m4

Hello Bruno, I missed this case the last time (as the test isn't executed on my system). OK to apply? Cheers, Ralf * intmax.m4 (gt_TYPE_INTMAX_T): Avoid unused variable. Index: m4/intmax.m4 === RCS file: /cvsroot/gnulib/gn

getlogin_r.m4 and host_os.m4 (was: megatest fallout)

> (b) comparing (1) and (2): > getlogin_r declared in the glob test, but not in the getlogin_r test. > (c) HOST_OPERATING_SYSTEM is set to empty in (2). OK to apply? Cheers, Ralf * getlogin_r.m4 (gl_PREREQ_GETLOGIN_R): Require AC_GNU_SOURCE. * host-os.m4 (gl_HOST_OS): Require AC

Fix chdir-long.m4 caching (was: megatest fallout)

Hello Jim, > 7 checking whether this system has an arbitrary file name length > limit... yes OK to apply this patch? I think this variable isn't used elsewhere in gnulib nor coreutils, so renaming this shouldn't be a problem. Cheers, Ralf * chdir-long.m4 (gl_FUNC_CHDIR_LONG): Re

Re: megatest fallout

A bootstrapped megatest directory enables more kinds of tests. Let's look at these builds: 0) configure CC='gcc -Wall -Werror -fno-builtin' # as seen earlier 1) configure 2) configure -C 3) pre-seed config.cache with the file resulting from (2), then configure -C 4) create a config.cache from

Re: some missing module dependencies

Hello Jim, * Jim Meyering wrote on Fri, Sep 22, 2006 at 09:13:41AM CEST: > Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > > > Is this patch ok, or would you rather factor out clock_time.m4 into its > > own module (as it is listed by 3 modules already)? > It's a tiny bit nicer to alphabetize lists

Re: [bug-gnulib] unused variables and other nits in gnulib/m4

Ralf Wildenhues wrote: > > What's the point of that? > > To supply a prototype for strcpy which is used in the test. Thanks for explaining. The only risk is that of a possible prototype clash for stpncpy() between and the expected one, but I've checked AIX and glibc (the only platforms known so

Re: coreutils-6.2: various runtime problems on Darwin-8.7.0 HFS+ (including attachment this time)

<[EMAIL PROTECTED]> wrote: > I am new to this list, but not at all new to building and using > open source projects. (Please CC me if needed as I haven't yet > joined this list. Or I think I can access and post via > news.gmane.org with regular newsreaders.) > > I built coreutils-6.2 on Darwin-8.

FYI: typo fix for fcntl_h.m4

The intent is to exit nonzero if open-nofollow succeeds on a symlink, not only in the highly unlikely (probably impossible, in a configure script) event it returns FD 0. 2006-09-25 Jim Meyering <[EMAIL PROTECTED]> * fcntl_h.m4 (gl_FCNTL_H): Fix typo in test for failed open. This

Re: getloadavg and LIBOBJDIR

Jim Meyering wrote: > The problem that causes the coreutils build failure is due in part > to the way the bootstrap script invokes gnulib-tool, then moves/links > the resulting files into our canonical lib/ and m4/ directories. > Since coreutils is perhaps unusual in doing things this way, > ... *

Re: [bug-gnulib] unused variables and other nits in gnulib/m4

Hello Bruno, Thanks for the changes you applied. As usual, you show much more diligence in fixing things. :-) * Bruno Haible wrote on Fri, Sep 22, 2006 at 10:12:21PM CEST: > Ralf Wildenhues wrote: > > > * stpncpy.m4 (gl_FUNC_STPNCPY): Likewise. > > Not applied. The patch does something di

Re: [bug-gnulib] unused variables and other nits in gnulib/m4

Ralf Wildenhues wrote: > * lock.m4 (gl_LOCK_BODY): Avoid unused variables. > * mbswidth.m4 (gl_MBSWIDTH): Likewise. > * signed.m4 (bh_C_SIGNED): Likewise. Thanks for the patches. I applied these, using Paul's usual style "return !x;" (there's no reason for the 'if'). >