On Tue 07 Sep 2004 15:17, "H.Merijn Brand" <[EMAIL PROTECTED]> wrote:
> Automated smoke report for 5.9.2 patch 23275
> r3: 9000/800 (9000/800/2 cpu)
>     on        hp-ux - 11.11/64
>     using     gcc version 3.4.1
>     smoketime 6 hours 27 minutes (average 24 minutes 12 seconds)
> 
> Summary: FAIL(c)
> 
> O = OK  F = Failure(s), extended report at the bottom
> X = Failure(s) under TEST but not under harness
> ? = still running or test results not (yet) available
> Build failures during:       - = unknown or N/A
> c = Configure, m = make, M = make (after miniperl), t = make test-prep
> 
>    23275     Configuration (common) -Dcc=gcc
> ----------- ---------------------------------------------------------
> O O O O O O 
> O O O O O O -Duse64bitall
> O O O O O O -Duseithreads
> c - - c - - -Duseithreads -Duse64bitall
> O O O O O O -Accflags='-DPERL_COPY_ON_WRITE'
> c - - c - - -Accflags='-DPERL_COPY_ON_WRITE' -Duse64bitall
> O O O O O O -Accflags='-DPERL_COPY_ON_WRITE' -Duseithreads
> c - - c - - -Accflags='-DPERL_COPY_ON_WRITE' -Duseithreads -Duse64bitall

It caught me during update process of gcc to 3.4.2
I've seen this before. Now what was it that I did to `fix' it?

Configure -Dusedevel -Dusethreads -Duseithreads -Dcc=gcc64 -Duse64bitall -Duse64bitall 
-des
(I see you are using the Korn shell.  Some ksh's blow up on Configure,
mainly on older exotic systems.  If yours does, try the Bourne shell instead.)
First let's make sure your kit is complete.  Checking...
Locating common programs...
Checking compatibility between /pro/local/bin/echo and builtin echo (if any)...
Symbolic links are supported.
Checking how to test for symbolic links...
You can test for symbolic links with 'test -h'.
Good, your tr supports [:lower:] and [:upper:] to convert case.
Using [:upper:] and [:lower:] to convert case.
3b1          dos_djgpp      isc_2         os2           svr4
aix          dynix          linux         os390         svr5
aix_3        dynixptx       lynxos        os400         ti1500
aix_4        epix           machten       posix-bc      titanos
altos486     esix4          machten_2     powerux       ultrix_4
amigaos      fps            mint          qnx           umips
apollo       freebsd        mips          rhapsody      unicos
atheos       genix          mpc           sco           unicosmk
aux_3        gnu            mpeix         sco_2_3_0     unisysdynix
beos         greenhills     ncr_tower     sco_2_3_1     utekv
bsdos        hpux           netbsd        sco_2_3_2     uts
convexos     i386           newsos4       sco_2_3_3     uwin
cxux         irix_4         next_3        sco_2_3_4     vmesa
cygwin       irix_5         next_3_0      solaris_2     vos
darwin       irix_6         next_4        stellar
dcosx        irix_6_0       nonstopux     sunos_4_0
dec_osf      irix_6_1       openbsd       sunos_4_1
dgux         isc            opus          super-ux
Which of these apply, if any? [Policy hpux]
===== PROCURA Policy for hpux/gcc64 ========================
      Using /pro/local/bin/cached/gcc64
Your C compiler (gcc64) is 64 bit native!

*** This version of gcc uses 64 bit longs. -Duse64bitall is
*** implicitly set to enable continuation
Operating system name? [hpux]
Operating system version? [11.11]
Build Perl for SOCKS? [n]
Use the PerlIO abstraction layer? [y]
Build a threading Perl? [y]
Use the newer interpreter-based ithreads? [y]
Use which C compiler? [gcc64]
Your compiler is ok.
Checking for GNU cc in disguise and/or its version number...
Now, how can we feed standard input to your C preprocessor...
Directories to use for library searches?
[/usr/local/pa20_64/lib /lib/pa20_64 /lib /usr/lib /usr/ccs/lib /usr/local/lib]
What is the file extension used for shared libraries? [sl]
Try to use long doubles if available? [n]
Checking for optional libraries...
What libraries to use?
[-lcl -lpthread -lnsl -lnm -lgdbm -ldb -ldl -ldld -lm -lsec -lc]
What optimizer/debugger flag should be used? [-g -O]
Any additional cc flags?
[-D_POSIX_C_SOURCE=199506L -D_REENTRANT -mpa-risc-2-0 -DDEBUGGING -D_HPUX_SOURCE 
-DDEBUGGING -fno-strict-aliasing -pipe -I/usr/local/pa20_64/include]
Let me guess what the preprocessor flags are...
Any additional ld flags (NOT including libraries)?
[ -L/usr/local/pa20_64/lib -L/lib/pa20_64]
Checking your choice of C compiler and flags for coherency...
I've tried to compile and run the following simple program:

#include <stdio.h>
int main() { printf("Ok\n"); return(0); }

I used the command:

        gcc64 -o try -g -O -D_POSIX_C_SOURCE=199506L -D_REENTRANT -mpa-risc-2-0 
-DDEBUGGING -D_HPUX_SOURCE -DDEBUGGING -fno-strict-aliasing -pipe 
-I/usr/local/pa20_64/include -L/usr/local/pa20_64/lib -L/lib/pa20_64 try.c -lcl 
-lpthread -lnsl -lnm -lgdbm -ldb -ldl -ldld -lm -lsec -lc
         ./try

and I got the following output:

/usr/lib/pa20_64/dld.sl: Unsatisfied data symbol '__unwind_start' in load module 
'/lib/pa20_64/libcl.2'.
/usr/lib/pa20_64/dld.sl: Unsatisfied data symbol '__unwind_end' in load module 
'/lib/pa20_64/libcl.2'.
/usr/lib/pa20_64/dld.sl: Unsatisfied data symbol '__text_start' in load module 
'/lib/pa20_64/libcl.2'.
/bin/sh: 20080 Abort(coredump)
The program compiled OK, but exited with status 134.
You have a problem.  Shall I abort Configure [y]
Ok.  Stopping Configure.

-- 
H.Merijn Brand        Amsterdam Perl Mongers (http://amsterdam.pm.org/)
using perl-5.6.1, 5.8.3, & 5.9.x, and 809 on  HP-UX 10.20 & 11.00, 11i,
   AIX 4.3, SuSE 9.0, and Win2k.           http://www.cmve.net/~merijn/
http://archives.develooper.com/[EMAIL PROTECTED]/   [EMAIL PROTECTED]
send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org


Reply via email to