Remarks at the end.

Automated smoke report for patch 12057
                                                      |             cc           gcc
O = OK                                                | HP-UX 11.00 B.11.11.02   3.0.1 
   32-bit
F = Failure(s), extended report at the bottom         |                          
3.0.1-64 64-bit +GNUld
? = still running or test results not (yet) available | HP-UX 10.20 A.10.32.30   2.8.1
Build failures during:       - = unknown,   = skipped | AIX 4.3.3.0 vac 5.0.2.0  3.0.1
    c = Configure, m = make, t = make test-prep       | AIX 4.2.1.0 xlc 3.1.4.10 2.8.1

 HP-UX    HP-UX    HP-UX     AIX      AIX      AIX
 11.00    11.00    10.20     4.3      4.3      4.2
  HPc      gcc      HPc      vac      gcc      xlc
 12057    12057    12057    12057    12057    12057   Configuration
-------  -------  -------  -------  -------  -------  
--------------------------------------------------------------------
O O O O  O O O O  O O O O  O O t t  O O O O  O O O O  -Uuseperlio
O O O O  O O O O  O O O O  O O t t  O O O O  O O O O  -Duseperlio
O O O O  O O O O           O O t t  c c c c           -Duseperlio -Duse64bitint
O O O O  O O O O           O O t t                    -Duseperlio -Duse64bitall
O O O O  O O O O  O O O O  O O t t  O O O O  O O O O  -Duseperlio -Duselongdouble
O O O O  O O O O           O O t t                    -Duseperlio -Dusemorebits
O O O O  O O O O           O O t t  c c c c           -Duseperlio -Duse64bitall 
-Duselongdouble
O O O O  O O O O  O O m m  O O O O  ? ? ? ?  O O O O  -Uuseperlio -Dusethreads 
-Duseithreads
O O O O  O O O O  O O O O  O O O O  ? ? ? ?  O O O O  -Duseperlio -Dusethreads 
-Duseithreads
O O O O  O O O O           F F F F  ? ? ? ?           -Duseperlio -Duse64bitint 
-Dusethreads -Duseithreads
O O O O  O O O O           F F F F  ? ? ? ?           -Duseperlio -Duse64bitall 
-Dusethreads -Duseithreads
O O O O  O O O O  O O O O  O O O O  ? ? ? ?  O O O O  -Duseperlio -Duselongdouble 
-Dusethreads -Duseithreads
O O O O  O O O O           F F F F  ? ? ? ?           -Duseperlio -Dusemorebits 
-Dusethreads -Duseithreads
O O O O  O O O O           F F F F  ? ? ? ?           -Duseperlio -Duse64bitall 
-Duselongdouble -Dusethreads -Duseithreads
| |                            | |
| +----- PERLIO = perlio       | +- PERLIO = perlio -DDEBUGGING
+------- PERLIO = stdio        +--- PERLIO = stdio  -DDEBUGGING

Failures:

AIX 4.3      stdio/perlio     -Duseperlio -Duse64bitint -Dusethreads -Duseithreads
AIX 4.3      stdio/perlio     -DDEBUGGING -Duseperlio -Duse64bitint -Dusethreads 
-Duseithreads
AIX 4.3      stdio/perlio     -Duseperlio -Duse64bitall -Dusethreads -Duseithreads
AIX 4.3      stdio/perlio     -DDEBUGGING -Duseperlio -Duse64bitall -Dusethreads 
-Duseithreads
AIX 4.3      stdio/perlio     -Duseperlio -Dusemorebits -Dusethreads -Duseithreads
AIX 4.3      stdio/perlio     -DDEBUGGING -Duseperlio -Dusemorebits -Dusethreads 
-Duseithreads
AIX 4.3      stdio/perlio     -Duseperlio -Duse64bitall -Duselongdouble -Dusethreads 
-Duseithreads
AIX 4.3      stdio/perlio     -DDEBUGGING -Duseperlio -Duse64bitall -Duselongdouble 
-Dusethreads -Duseithreads
    ext/DB_File/t/db-btree.............FAILED at test 79

The 'm' in HP-UX 10.20 is from a strange dep in makefile:

k1:/pro/3gl/CPAN/perl-current 116 > make
make: *** No rule to make target `values.h', needed by `pp_sys.o'.  Stop.
k1:/pro/3gl/CPAN/perl-current 117 > grep values.h makefile
pp_sys$(OBJ_EXT): /usr/include/values.h
pp_sys$(OBJ_EXT): values.h
k1:/pro/3gl/CPAN/perl-current 118 > grep values.h *.h
config.h: *     include <values.h> to get definition of symbols like MINFLOAT or
perl.h:#  include <values.h>
perl.h: * following hacks are used if neither limits.h or values.h provide them:
perl.h:#  ifdef MAXSHORT    /* Often used in <values.h> */
perl.h:#  ifdef MAXINT    /* Often used in <values.h> */
perl.h:#  ifdef MAXLONG    /* Often used in <values.h> */
uconfig.h: *    include <values.h> to get definition of symbols like MINFLOAT or
k1:/pro/3gl/CPAN/perl-current 119 >

Why twice? Why suddenly wrong?

Can't find a (synced) patch that might have caused this.

Reply via email to