Mailing List Archive: problems compiling perl5.001m on Solaris 2.4

problems compiling perl5.001m on Solaris 2.4

Aug 23, 1995, 11:51 AM

Post #1 of 4 (1286 views)

problems compiling perl5.001m on Solaris 2.4 (sparcstation 20).

Actually it compiles fine but fails the lib/posix.t tests (9, 10, 11).
Checking with the perl debugger against perl5.000 on another Solaris
2.4 machine shows that the line

kill 'HUP', $$;

does nothing with perl5.001m but invokes the SigHUP routine on
perl5.000.

kill 'INT', $$;

works in both cases.

I've compiled with both /opt/SUNWspro/bin/cc and gcc 2.6.3 with the
same results in both cases.

According to the newsgroup and to all the notes I could find, perl5
shouldn't be having this result.

I suspect this may have something to do with the signal handling
problem mentioned in the PERL faq

> Michael D'Errico* reports:
>
> If you are using Solaris 2.x, the signal handling is broken. If
> you set up a signal handler such as 'ripper' it will be forgotten
> after the first time the signal is caught. To fix this, you need
> to recompile Perl. Just add '#define signal(x,y) sigset((x),(y))'
> after the '#include <signal.h>' directive in each file that it
> occurs, then make it again.

However (a) that seemed to be specific to perl4 and (b) adding it to
mg.c and util.c did nothing.

puzzled,

Emma

Re: problems compiling perl5.001m on Solaris 2.4 [ In reply to ]

emma at Csli

Aug 24, 1995, 7:58 AM

Post #2 of 4 (1266 views)

Permalink

Summary of my perl5 (patchlevel 1) configuration:
Platform:
osname=solaris, osver=2.4, archname=sun4-solaris
uname='sunos turing.stanford.edu 5.4 generic_101945-29 sun4m sparc '
hint=recommended
Compiler:
cc='cc', optimize='-O', ld='cc'
cppflags='-DDEBUGGING'
ccflags ='-DDEBUGGING'
ldflags =''
stdchar='unsigned char', d_stdstdio=define, usevfork=false
voidflags=15, castflags=0, d_casti32=define, d_castneg=define
intsize=4, alignbytes=8, usemymalloc=y, randbits=15
Libraries:
so=so
libpth=/lib /usr/lib /usr/ccs/lib /usr/local/lib /opt/SUNWspro/SW3.0.1/lib
libs=-lsocket -lnsl -ldl -lm -lc -lcrypt
libc=/usr/lib/libc.so
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef
cccdlflags='-Kpic', ccdlflags=' ', lddlflags='-G'

In <199508231851.LAA05311@Turing.Stanford.EDU>
On Wed, 23 Aug 1995 11:51:03 -0700
Emma Pease <emma@csli.Stanford.EDU> writes:
>problems compiling perl5.001m on Solaris 2.4 (sparcstation 20).
>
>Actually it compiles fine but fails the lib/posix.t tests (9, 10, 11).
>Checking with the perl debugger against perl5.000 on another Solaris
>2.4 machine shows that the line
>
>kill 'HUP', $$;
>
>does nothing with perl5.001m but invokes the SigHUP routine on
>perl5.000.
>
>kill 'INT', $$;
>
>works in both cases.
>
>I've compiled with both /opt/SUNWspro/bin/cc and gcc 2.6.3 with the
>same results in both cases.

Re: problems compiling perl5.001m on Solaris 2.4 [ In reply to ]

emma at csli

Aug 24, 1995, 7:58 AM

Post #3 of 4 (1267 views)

Permalink

Summary of my perl5 (patchlevel 1) configuration:
Platform:
osname=solaris, osver=2.4, archname=sun4-solaris
uname='sunos turing.stanford.edu 5.4 generic_101945-29 sun4m sparc '
hint=recommended
Compiler:
cc='cc', optimize='-O', ld='cc'
cppflags='-DDEBUGGING'
ccflags ='-DDEBUGGING'
ldflags =''
stdchar='unsigned char', d_stdstdio=define, usevfork=false
voidflags=15, castflags=0, d_casti32=define, d_castneg=define
intsize=4, alignbytes=8, usemymalloc=y, randbits=15
Libraries:
so=so
libpth=/lib /usr/lib /usr/ccs/lib /usr/local/lib /opt/SUNWspro/SW3.0.1/lib
libs=-lsocket -lnsl -ldl -lm -lc -lcrypt
libc=/usr/lib/libc.so
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef
cccdlflags='-Kpic', ccdlflags=' ', lddlflags='-G'

>Actually it compiles fine but fails the lib/posix.t tests (9, 10, 11).
>Checking with the perl debugger against perl5.000 on another Solaris
>2.4 machine shows that the line
>
>kill 'HUP', $$;
>
>does nothing with perl5.001m but invokes the SigHUP routine on
>perl5.000.
>
>kill 'INT', $$;
>
>works in both cases.
>
>I've compiled with both /opt/SUNWspro/bin/cc and gcc 2.6.3 with the
>same results in both cases.

Did you have /opt/SUNWspro/SW3.0.1/lib for both cases?
I doubt if it is appropriate for gcc. (My gcc 2.6.2 and gcc 2.7.0
builds both work okay - I don't have sun compiler on 2.4 machine).

Try without that library - Solaris should use compiler to link
by default in anycase, so Sun compiler should find its own
library without assistance.

Re: problems compiling perl5.001m on Solaris 2.4 [ In reply to ]

Nick.Ing-Simmons at tiuk

Aug 24, 1995, 8:31 AM

Post #4 of 4 (1279 views)

Permalink

In <199508231851.LAA05311@Turing.Stanford.EDU>
On Wed, 23 Aug 1995 11:51:03 -0700
Emma Pease <emma@csli.Stanford.EDU> writes:
>problems compiling perl5.001m on Solaris 2.4 (sparcstation 20).
>
>Actually it compiles fine but fails the lib/posix.t tests (9, 10, 11).
>Checking with the perl debugger against perl5.000 on another Solaris
>2.4 machine shows that the line
>
>kill 'HUP', $$;
>
>does nothing with perl5.001m but invokes the SigHUP routine on
>perl5.000.
>
>kill 'INT', $$;
>
>works in both cases.
>
>I've compiled with both /opt/SUNWspro/bin/cc and gcc 2.6.3 with the
>same results in both cases.

Send output of myconfig in perl5.001m directory.