bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: textutils version 2.1 bug


From: Parimi, Venkateshwara Rao
Subject: RE: textutils version 2.1 bug
Date: Wed, 16 Jul 2003 16:46:32 +0530

>The 'configure' script should not get /bin/sh on that platform.  It
>should set CONFIG_SHELL to /bin/ksh (or to Bash, if you have installed
>that yourself).
That's true CONFIG_SHELL is ksh and SHELL is sh

>Also, which sh and ksh are you using?  Here's what I get on my Solaris
>2.6 system.  If your shells are older, perhaps you need to install the
>free Sun patches for them.

>67-dew $ type sh
>sh is /usr/bin/sh
>68-dew $ type ksh
>ksh is /usr/bin/ksh
>69-dew $ ls -l /usr/bin/sh /usr/bin/ksh
>-r-xr-xr-x   2 bin      bin       186528 Jan  7  2003 /usr/bin/ksh
>-r-xr-xr-x   3 bin      root       89028 Dec 18  2002 /usr/bin/sh
>70-dew $ /usr/bin/sum /usr/bin/sh /usr/bin/ksh
>18780 174 /usr/bin/sh
>8794 365 /usr/bin/ksh

parimiv > /usr/bin/sum /usr/bin/sh /usr/bin/ksh
48041 174 /usr/bin/sh
63046 365 /usr/bin/ksh

parimiv > ls -l /usr/bin/sh /usr/bin/ksh
-r-xr-xr-x   2 bin      bin       186520 Nov 29  2000 /usr/bin/ksh
-r-xr-xr-x   3 bin      root       88972 Nov 29  2000 /usr/bin/sh

With the same shells it works fine on another machine with Solaris 2.6.

What I want to know is, what would be the next check done by the configure
script that causing Segmentation fault.
I have different kind of packages installed on both the machines and want to
see which one is the culprit.
I thought it will be easy for you guys to advice instead of me reinventing
the wheel digging through the configure.


Other bugs in core-utils:
1) src/wheel-gen.pl has #!/usr/bin/perl hard-coded(I have perl in
/usr/local/bin).
        Can this be auto detected?

2) Basic test of du fails because of the test file is written with less
bytes than required (>64 bytes).
parimiv > diff basic basic.fixed
22a23,24
> printf 'make-sure-the-file-is-non-empty\n' >> a/b/F || framework_failure=1
> printf 'make-sure-the-file-is-non-empty\n' >> a/b/F || framework_failure=1


b) fail-2eperm of rm fails because of the error string expected is different
from the actual error string returned
parimiv > diff fail-2eperm fail-2eperm.fixed
46c46
< rm: cannot remove `a/b': Operation not permitted
---
> rm: cannot remove `a/b': Not owner



Thanks in advance.
-Venkatesh




reply via email to

[Prev in Thread] Current Thread [Next in Thread]