[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: a coreutils release is imminent
From: |
Matthew Woehlke |
Subject: |
Re: a coreutils release is imminent |
Date: |
Wed, 21 Mar 2007 10:39:43 -0500 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.4.0 |
powerpc-ibm-aix5.1.0.0 OK (with Bruno's patch... thanks!)
Jim Meyering wrote:
Matthew Woehlke wrote:
mips-sgi-irix6.5 FAIL (tty-eof)
I've investigated this enough to be pretty confident it is solely
a problem in that particular test script, maybe in Expect.pm.
That might be. I did notice that another platform (I forget which) had
skipped this; something about expect.pm. I guess the verbose output
(remind me again how to do that? 'VERBOSE=1 make check TESTS=tty-eof'?)
might help to get this test skipped?
alphaev56-dec-osf4.0g FAIL
What version of Perl do you have there?
(below...)
I have *NO* c99-compatible compiler on sparc/Solaris, at least configure
is not detecting it properly. This includes the most recent one I have
available, 'cc: Sun WorkShop 6 update 2 C 5.3 2001/05/15'! It looks
suspiciously like my compiler may be broken.
No problem. Just apply the c99-to-c89 patch.
Right, just pointing out that this one platform apparently /does not
have/ a c99 compiler. Even with (more) modern compilers available.
Actually, what I get is:
cc -xc99 -c -g conftest.c >&5
"/usr/include/stdbool.h", line 42: #error: "Use of <stdbool.h> is valid
only in a c99 compilation environment."
cc: acomp failed for conftest.c
...which feels distinctly like the compiler is *broken*.
sort-compress still fails with a low process limit (e.g. my OSF
system)... I thought this was fixed? It also failed on ia64/hpux.
There is (still) a really annoying problem with the perl detection that
leads to "can't find strict.pm" problems; maybe we could check that perl
This is the first I've heard of such a problem.
What version of Perl is installed there?
I may simply raise the required version number to one for which
"use strict;" works. In the mean time, you can work around that
by manually removing the "use strict" lines.
That's what I was thinking. Hmm, 'perl --version' hangs waiting for
input, and 'perl -V' is a usage error. So... how do I *tell* what
version? (Clearly I'm not a perl expert :-).)
Hmm, ok, I see this in the error:
/freeware/lib/perl5/alpha-dec_osf/5.00401
...so maybe it is 5.00401?
If I remove 'use strict' from all the .pm's in tests/, then I get this:
make[2]: Entering directory
`/home/install/gnu/src/foo/alpha_osf/coreutils-6.8+/tests/cut'
rm -f Makefile.am Makefile.amt
sed -n '1,/^##test-files-begin/p' ./../Makefile.am.in > Makefile.amt
tool=`echo tests/cut|sed 's/^tests.//;s/-test//'`; \
echo "x = $tool" >> Makefile.amt
/bin/sh
/home/install/gnu/src/foo/alpha_osf/coreutils-6.8+/build-aux/missing
--run perl -I. -w -- ./../mk-script . --list >> Makefile.amt
Can't locate strict.pm in @INC (@INC contains: .
/freeware/lib/perl5/alpha-dec_osf/5.00401 /freeware/lib/perl5
/freeware/lib/perl5/site_perl/alpha-dec_osf
/freeware/lib/perl5/site_perl /freeware/lib/perl5/alpha-dec_osf .) at
./../mk-script line 29.
...and something (presumably perl) hangs waiting for input. So methinks
my perl is b0rk.
Anyway, sort-compress is still "broken". Wasn't there talk of limiting
the number of forks based on getrlimit?
More on the IA64/HPUX failures pending...
is *usable*, not just if it exists? Because of this it isn't clear how
many test failures are spurious. (It's also unfortunate that so many
tests need perl; perl isn't fun to build... so far every time I've
considered trying it I've given up.) For now I'm not even going to try
to chase the OSF test failures, this needs to be addressed first.
No big deal.
Very few people depend on OSF-based systems for real work.
Especially 4.0, since it's so buggy.
Well, *we* still depend on the very box I am trying to build on to build
software for people that need OSF versions. So, um... we kinda depend on
it, at least for the moment. :-) I guess I can't prove we're not in the
'very few' category though.
--
Matthew
Congratulations! You've won a free trip to the future! All you have to
do to claim your prize is wait five minutes...
- a coreutils release is imminent, Jim Meyering, 2007/03/20
- Re: a coreutils release is imminent, Matthew Woehlke, 2007/03/20
- Re: a coreutils release is imminent, Bob Proulx, 2007/03/21
- Re: a coreutils release is imminent, Jim Meyering, 2007/03/21
- Re: a coreutils release is imminent,
Matthew Woehlke <=
- Re: a coreutils release is imminent, Matthew Woehlke, 2007/03/21
- Re: a coreutils release is imminent, Jim Meyering, 2007/03/21
- Re: a coreutils release is imminent, Matthew Woehlke, 2007/03/21
- Re: a coreutils release is imminent, Andreas Schwab, 2007/03/21
- Re: a coreutils release is imminent, Matthew Woehlke, 2007/03/21
- Re: a coreutils release is imminent, Jim Meyering, 2007/03/21
- Re: a coreutils release is imminent, Matthew Woehlke, 2007/03/21
- Re: a coreutils release is imminent, Paul Eggert, 2007/03/21
- Re: a coreutils release is imminent, Paul Eggert, 2007/03/21
Re: a coreutils release is imminent, Paul Eggert, 2007/03/21