Re: new snapshot [Re: coreutils 6.9.92 fail to configure on *bsd

[Jim Meyering]

Elias Pipping <address@hidden> wrote:
> On Thu, Jan 17, 2008 at 03:34:20PM +0100, Jim Meyering wrote:
>> I've built a new snapshot:
>>
>>   http://meyering.net/cu/coreutils-ss.tar.gz
>>   http://meyering.net/cu/coreutils-ss.tar.lzma
>>   http://meyering.net/cu/coreutils-ss.tar.gz.sig
>>   http://meyering.net/cu/coreutils-ss.tar.lzma.sig
>>
>> and confirmed that it fixes all of those problems on your
>> i386-apple-darwin9.1.0 system, as long as you disable ACL support:
>>
>>     ./configure --disable-acl
>>
>> The other two failures were fixed via changes in gnulib:
>>
>> >     FAIL: test-frexpl
>> >     FAIL: test-printf-frexpl
>
> With the above snapshot and --disable-acl, all of the default tests,
> including those enabled via RUN_VERY_EXPENSIVE_TESTS pass.

Thanks for testing it.

> as for the check-root tests:
>
>   this one now passes:
>
>     special-bits
>
>   these fail:
>
>     rm/fail-2eperm
>     cp/preserve-gid
>     touch/now-owned-by-other

It looks like they're all due to the fact that you used
NON_ROOT_USERNAME=nobody and "nobody" lacks access to required
files.  Can you run it again, as recommended in README
i.e., using NON_ROOT_USERNAME=your_user_name (assuming the
source tree belongs to "your_user_name"):

    **********************
    Running tests as root:
    ----------------------

    If you run the tests as root, note that a few of them create files
    and/or run programs as a non-root user, `nobody' by default.
    If you want to use some other non-root username, specify it via
    the NON_ROOT_USERNAME environment variable.  Depending on the
    permissions with which the working directories have been created,
    using `nobody' may fail, because that user won't have the required
    read and write access to the build and test directories.
    I find that it is best to unpack and build as a non-privileged
    user, and then to run the following command as that user in order
    to run the privilege-requiring tests:

      sudo env NON_ROOT_USERNAME=$USER make -k check-root

    If you can run the tests as root, please do so and report any
    problems.  We get much less test coverage in that mode, and it's
    arguably more important that these tools work well when run by
    root than when run by less privileged users.