On Thu, Mar 28, 2002 at 03:00:03PM +0100, H.Merijn Brand wrote:
> On Thu 28 Mar 2002 13:23, Abigail <[EMAIL PROTECTED]> wrote:
> > Automated smoke report for patch 15544 on solaris - 2.8
> > v1.12 using gcc version 2.95.2 19991024 (release)
> > O = OK
> > F = Failure(s), extended report at the bottom
> > ? = still running or test results not (yet) available
> > Build failures during: - = unknown
> > c = Configure, m = make, t = make test-prep
> >
> > Configuration
> > ------- --------------------------------------------------------------------
> > O O ? ? -Uuseperlio
> > O O ? ? -Duseperlio
> > O O ? ? -Duseperlio -Duse64bitint
> > O O ? ? -Duseperlio -Duselongdouble
> > c c ? ? -Duseperlio -Duse64bitall -Duselongdouble
> > m m ? ? -Dusethreads -Duseithreads -Uuseperlio
> > m m ? ? -Dusethreads -Duseithreads -Duseperlio
> > m m ? ? -Dusethreads -Duseithreads -Duseperlio -Duse64bitint
> > m m ? ? -Dusethreads -Duseithreads -Duseperlio -Duselongdouble
>
> Because of 'as' you say? What does *your* crypt.h look like?
> For HP-UX 10.20 and AIX 4.2 I get loads of thread-'m's because of crypt.h
Should we have something in perldelta and/or README.{hpux,aix} about this?
I seem to remember that we have known patchlevels where this thing works
(i.e. it's only a simple matter of broken header files with wrong prototypes?0
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
