From: joel@abigale.UUCP (Joel Rosi-Schwartz)
Newsgroups: comp.lang.perl
Subject: Re: Building on SunOS 4.1.2 -- Core dump...
Date: 12 Oct 92 12:01:14 GMT
Organization: Techne Research, Finchampstead, Berkshire (UK)

Hi,

I got a reponse from Dave Greunke, which is attached below.  His
advice solved the problem and I know have working perls on the
Sun with both Suns cc and gcc.  Thanks Dave,  I tried to E-mail
you back both the Inet and UUCP addressed you list, but both
bounced.  If your are interested in why I have saved the baunce
reports, the only problem is how to get them to you without
posting them, to c.l.p  ;-)

Cheers,
Joel

>>|> I've been trying to build perl-4.035 on a Sparc IPX with
> [ stuff deleted ]
>>
>>Try using gcc, I had the same problem under SunOS 4.1.3. When I used gcc
>>everything worked fine (except 1 test).
>
>I find this thread interesting and relevant to me at the moment.  I
>am currently porting my application to Sun and it uses perl.  My
>experience is exactly the opposite of what is stated above.  I tried
>several times to build with gcc 2.2.2 and regardless of what I tried
>(SysV/BSD universes for lib/includes, perl/Sun malloc, -O or no -O, -
>static or using shared libs) I got the following test results (ok's
>deleted):
>
>	op/eval........FAILED on test 0
>	op/regexp......FAILED on test 45
>	lib/big........ok
>	/bin/sh: 19198 Memory fault - core dumped
>
>I finally gave up and compiled with Suns /usr/bin/cc and everything
>work perfectly.  I will probably backtrack and try it with
>/usr/5bin/cc and the SysV libs/includes, if I have the time before I
>have to return the loaner machine.  The relevant details are:
>
>	SparcStation2 GX
>	SunOS: 4.1.2/5.0
>
>Cheers,
>Joel

I'm not sure that this is your problem but I had similar problems building
perl 4.35 on a Sparc IPC under 4.1.1 with gcc2.2.2. Try rerunning the
configure script and when it come to the line where it adds extra flags
to pass to gcc it will probably try to include /usr/ucb/include on that
line. DON'T let it do that. I think what happens if you let this get thru is
varargs.h gets included when it shouldn't which causes all the perl routines
that use varargs() to get screwed up. Hope this trick works for you. It made
things run much better on my machine.


	Dave

-- 
-------------------------------------------------------------------------------
Dave Greunke                        | Internet:
Consultant                          | maplgrv!vid%astroatc.uucp@cs.wisc.edu
Maple Grove Computing               | UUCP:
Madison, WI.                        | ...uwvax!astroatc!maplgrv!vid
(608)273-0950                       |
-- 
     ==================================================================
     ||               T E C H N E   R E S E A R C H                  ||
     ||  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++  ||
     ||                     Joel Rosi-Schwartz                       ||
     ||   Hildorien House            +   Email: joel@abigale.UUCP    ||
     ||   12 Waverley Way            +    (pyrltd!abigale.UUCP!joel) ||
     ||   Finchampstead, Wokingham   +   Phone: +44 (734) 730.260    ||
     ||   Berkshire RG11 4YD (UK)    +   Fax:   +44 (734) 730.272    ||
     ==================================================================
Newsgroups: comp.lang.perl