Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!mirror!necntc!necis!mrst!sdti!mjy
From: mjy@sdti.UUCP (Michael J. Young)
Newsgroups: comp.sources.d
Subject: Re: v16i034: Larry Wall's Configure - (nf)
Message-ID: <323@sdti.UUCP>
Date: 1 Nov 88 13:54:07 GMT
References: <0@andrew.UUCP> <3100001@nixpbe.UUCP> <265@mpx2.UUCP>
Reply-To: mjy@sdti.UUCP (0006-Michael J. Young)
Organization: Software Development Technologies, Sudbury MA
Lines: 26

In article <265@mpx2.UUCP> erik@mpx2.UUCP (Erik Murrey) writes:
>In article <3100001@nixpbe.UUCP>, kebsch@nixpbe writes:
>> Jay Libove wrote:
>> > 1) that you have Perl. Perl doesn't run on 80286 machines. Not at all.
>> 			 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> That's wrong! I yacc'ed perl.y on a 32 bit machine and compiled
>> Perl-2.0, Patchlevel-14 on a 80286 machine. It runs pretty good and
>> I have no problems! My Operatingsystem is UNIX Sytem V Rel-2 (Microport).
>
>Oh, no.  Not again...  I would note that your microport yacc wouldn't
>compile perl.y either, unless you just wanted to yacc it on a 32
>bit box for no reason.  This is an 80286 problem, not SCO's, not Microport's.

No, it's a yacc problem.  Using the new version of yacc from Microport's
bbs that was compiled with larger tables, I was able to yacc perl.y.  I
have a working perl, although I'm only running at patchlevel 10 (just
lazy, I guess).

But let's face it.  It didn't come easy.  There are a number of constructs
in the perl source that cause the Microport compiler to bite the big one.
I'm still looking forward to Larry's patches to make my hacked up copy more
"official".  Hopefully, the next update will include the yacc output as
well as the .y file for those who can't get access to a large-table yacc.
-- 
Mike Young
Software Development Technologies, Inc., Sudbury MA       Tel: +1 508 443 5779
Internet: mjy@sdti.sdti.com                 UUCP: {harvard,mit-eddie}!sdti!mjy