Re: coreutils 5.2.1 make check fails

[michael]

Hello Bob,

I appreciate your prompt response.  I will answer your questions below.

On Sun, 14 Mar 2004, Bob Proulx wrote:

> Thank you for reporting this.  But I would like a little more
> information.
>
> address@hidden wrote:
> > Trying to install coreutils 5.2.1 on a Linux 2.4.25 system.
>
> I don't think it is important this time but in the future the version
> of the compiler and libc are frequently more important than the kernel
> version.  There are many ways to get the version of these and here is
> one relatively generic way.  Only the version number need be
> reported.  Here is an example from my bleeding edge system.
>
>   gcc --version | sed 1q

gcc (GCC) 3.2.2

>   gcc (GCC) 3.3.3 20040125 (prerelease) (Debian)
>
>   ldd --version | sed 1q

ldd (GNU) 2.3.2

>   ldd (GNU libc) 2.3.2
>
> But this time your problem appears to be related to the filesystem
> which is part of the kernel.
>
> > ./configure --prefix=/ --sysconfdir=/etc --disable-nls \
> >     --mandir=/usr/man  --infodir=/usr/info
> >     make && make check && make install
>
> As a general comment it is usually not recommended to install directly
> into the system /bin, /usr/info, etc.  Some commands are supposed to
> go into /usr/bin and usually /usr/share/info and so forth.  Instead I
> recommend that the FHS is followed and the executables be placed as
> specified by the latest version of the Filesystem Hierarchy Standard.
>
>   http://www.pathname.com/fhs/

I understand.. This test system was originaly a RH 6.2.  But over the
years most everything has been updated from source.  I am just trying to
keep the files in the RH demenor.  Your point is well taken and I will
rethink the FHS before I do a final install on a production server.

>
> That is usually done by installing into a staging area first, such as
> /var/tmp/image-area, and then packaging up the result after making
> whatever modifications are desired.
>
> > Fails on make check :
> > [...]
> > make[3]: Entering directory `/home/src/coreutils-5.2.1/tests/chmod'
> > out exp differ: char 8, line 1
> > 1c1
> > < chmod: getting attributes of `d/no-x/y': Permission denied
> > ---
> > > chmod: `d/no-x': Permission denied
>
> Interesting...
>
> As root this has permissions.  As a normal user it does not have
> permissions.  The test frame does not take this into consideration.
>
> > Fails on make check-root:
> > [...]
> > make[3]: Entering directory `/home/src/coreutils-5.2.1/tests/rm'
> > out exp differ: char 12, line 1
> > 1,2c1
> > < rm: cannot unlink `a/b': Operation not permitted
> > < rm: cannot remove directory `a': Directory not empty
> > ---
> > > rm: cannot remove `a/b': Operation not permitted
> > FAIL: fail-2eperm
> > ======================================
> > 1 of 1 tests failed
> > Please report to address@hidden
>
> This test is one run only when testing as 'root'.  Since building as
> root is generally frowned upon I doubt this test gets very much
> exposure.  The test is expecting to fail with this message:
>
>   rm: cannot remove `a/b': Operation not permitted
>
> But in your case it failed with a different message.
>
>   rm: cannot unlink `a/b': Operation not permitted
>   rm: cannot remove directory `a': Directory not empty
>
> Again thank you for reporting this.  Can you say whether this is on an
> NFS mounted filesystem or on the local filesystem?  And if on the
> local filesystem can you say what type of filesystem?  (The output of
> 'df -T' will show this.)
>
>   df -T . | awk '{print$2}'

Local file system
Type
ext3

>
> Incidentally chmod's no-x test is skipped on my system and fail-2eperm
> passes when run as root.
>
> Can you run the tests like this and send the output back to the list?
>
>   cd tests/chmod
>   env VERBOSE=yes make check TESTS=no-x

make  check-TESTS
make[1]: Entering directory `/home/src/coreutils-5.2.1/tests/chmod'
chmod (coreutils) 5.2.1
Written by David MacKenzie and Jim Meyering.

Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
chmod (fileutils) 4.1
Written by David MacKenzie.

Copyright (C) 2001 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
out exp differ: char 8, line 1
1c1
< chmod: getting attributes of `d/no-x/y': Permission denied
---
> chmod: `d/no-x': Permission denied
FAIL: no-x
======================================
1 of 1 tests failed
Please report to address@hidden
======================================
make[1]: Leaving directory `/home/src/coreutils-5.2.1/tests/chmod'

>
>   cd tests/rm
>   env VERBOSE=yes make check TESTS=fail-2eperm

make  check-TESTS
make[1]: Entering directory `/home/src/coreutils-5.2.1/tests/rm'
rm (coreutils) 5.2.1
Written by Paul Rubin, David MacKenzie, Richard Stallman, and Jim Meyering.

Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
out exp differ: char 12, line 1
1,2c1
< rm: cannot unlink `a/b': Operation not permitted
< rm: cannot remove directory `a': Directory not empty
---
> rm: cannot remove `a/b': Operation not permitted
FAIL: fail-2eperm
======================================
1 of 1 tests failed
Please report to address@hidden
======================================
make[1]: Leaving directory `/home/src/coreutils-5.2.1/tests/rm'

Thanks,

Michael...

>
> Thanks
> Bob
>