home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!usenet.ins.cwru.edu!agate!ames!sun-barr!news2me.EBay.Sun.COM!exodus.Eng.Sun.COM!vsync.Eng.Sun.COM!exodus
- From: exodus@vsync.Eng.Sun.COM (Greg Onufer)
- Newsgroups: comp.lang.perl
- Subject: Re: Perl 4.035 on Solaris 2.1
- Date: 9 Jan 1993 00:59:29 GMT
- Organization: Sun Microsystems Inc., Mountain View, CA
- Lines: 19
- Distribution: usa
- Message-ID: <lks8rhINNkmi@exodus.Eng.Sun.COM>
- References: <1993Jan8.203105.16916@eagle.lerc.nasa.gov>
- NNTP-Posting-Host: vsync
-
- In <1993Jan8.203105.16916@eagle.lerc.nasa.gov> drich@sandman.lerc.nasa.gov (Daniel Rich) writes:
- >Has anyone successfully compiled perl 4.035 on Solaris 2.1? I managed
- >to get an executable with only a couple hours of hacking, but the
- >executable core dumps during the first test. Can anyone offer any
- >suggestions? I would like to get inn 1.2 running, but need perl to
- >validate my configuration....
-
- I've done it with gcc and Sun's unbundled C compiler. Just answer all
- of the Configure questions and at the end when it asks you if you want
- to edit config.sh, do so and make sure that you 1) don't let it use
- vfork and 2) make sure it uses the system malloc and not its own. It
- then passes all of its tests except there are two cpp warnings about
- unterminated strings when one of the tests are run through the C
- preprocessor and the warnings seem harmless. If you want a glitchless
- run of the tests, edit the script those warnings are generated about and
- remove the apostrophes (they are in contractions like "isn't") from the
- two '#' comments.
-
- Cheers!greg
-