develooper Front page | perl.perl5.porters | Postings from October 2001

Re: MacOS X.1 build w/some problems

Thread Previous | Thread Next
From:
Jarkko Hietaniemi
Date:
October 26, 2001 06:23
Subject:
Re: MacOS X.1 build w/some problems
Message ID:
20011026162323.F6305@alpha.hut.fi
On Fri, Oct 26, 2001 at 04:28:33AM -0400, schwern@pobox.com wrote:
> I just installed MacOS X 10.1, and boy is it perdy.  I've got rootless
> X working, Xemacs, gimp...  Except for the fact that everytime it
> pronounces "Schwern" there's a loud buzzing noise.  You'd think Apple
> had a personal vandetta against me.
> 
> Anyhow, here's the interesting parts from a perl-current test.  I'm
> using 64-bit ints and perl's malloc just to be difficult.

I think something else, too, has a personal vendetta against you since
I have less problems with blead in Mac OS X 10.1..

> op/lfs................................skipped: no sparse files?
> 
> Darwin doesn't have sparse files?

This ain't your father's UFS, this is HFS+.

> op/pat................................dubious                                
>         Test returned status 0 (wstat 11, 0xb)

Not for me.

> ../ext/DB_File/t/db-recno.............FAILED tests 61, 63, 65                
>         Failed 3/149 tests, 97.99% okay

These are known, as you can tell from the message.   The DB_File
of OS X is broken.

> ../ext/Encode/Encode/Tcl..............dubious                                
>         Test returned status 0 (wstat 11, 0xb)
> DIED. FAILED tests 8-632
>         Failed 625/632 tests, 1.11% okay
> 
> Segfault after test #7.  Again, can't find the damned thing.

Not for me.

> ../ext/IPC/SysV/ipcsysv...............skipped: $Config{d_sem} undefined
> ../ext/IPC/SysV/t/msg.................skipped: $Config{d_sem} undefined
> ../ext/IPC/SysV/t/sem.................skipped: $Config{d_sem} undefined
> 
> This supposed to happen?

Yes.  No semaphores, no tests.

> ../ext/POSIX/t/posix..................FAILED test 10                         
>         Failed 1/29 tests, 96.55% okay

Known.  IIRC the test behaves if run manually.

> ../lib/Unicode/Collate/t/test.........dubious                                
>         Test returned status 0 (wstat 11, 0xb)
> DIED. FAILED tests 20-22
>         Failed 3/22 tests, 86.36% okay
> 
> Another segfault.

Not for me.

> ../lib/warnings.......................ok 314/448PROG:                        
> ..
> ####################################################################
> # The next test is known to fail on some systems (Linux+old glibc, #
> # some *BSDs (including Mac OS X and NeXT), among others.          #
> # We skip it for now (on the grounds that it is "just" a warning). #
> ####################################################################
> ../lib/warnings.......................FAILED test 315                        
>         Failed 1/448 tests, 99.78% okay

As you can see, known.  IIRC a weirdo buffering glitch that
can't be much helped by Perl.

The difference in our configs seems to be that you have use64bitint
(but not in config_args, how did you manage that?  reused config.sh?)
I'll retry with that.

Recap: all the other are known, but the Encode and Collate core
dumps are surprising.

As for the core dumps, I think the "limit" command will tell
what happened to them.

-- 
$jhi++; # http://www.iki.fi/jhi/
        # There is this special biologist word we use for 'stable'.
        # It is 'dead'. -- Jack Cohen

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About