henkp@nikhefk.UUCP (Henk Peek) (02/23/88)
-> >>It would be helpful if Larry could include the yacc output. -> >Actually, we discussed this with larry when perl was first being -> >developed. The problem is that the output of yacc contains AT&T -> >propriatary code (inserted by the yacc program), and so yacc -> >output can only be sent to parties with a source license. -> ->Actually, this *MIGHT* not be the case. About 12 to 24 months ago, ->ATT put out an announcement saying that the stuff in /lib and /usr/lib ->could be used in vendor code without any licensing restrictions. -> /r$ I remember me the same discussion. You could do it your self. Cross generate the yacc output on a big unix machine!! Take your yacc source to the big (32 bit!) unix machine and yacc it and put the output and the 2 include-files to the c compiler on your small unix machine. I have used it for a 16 bit machine without yacc. I haven't tested it with perl. Henk Peek ..!uunet!mcvax!nikhefk!henkp.UUCP
sl@van-bc.UUCP (Stuart Lynne) (02/25/88)
In article <323@nikhefk.UUCP> henkp@nikhefk.UUCP (Henk Peek) writes: > >Cross generate the yacc output on a big unix machine!! >Take your yacc source to the big (32 bit!) unix machine and yacc it and >put the output and the 2 include-files to the c compiler on your >small unix machine. I have used it for a 16 bit machine without yacc. >I haven't tested it with perl. > I've got quite a bit of mail since I posted about this problem. This was the response from Microport. >To: mit-eddie!van-bc!sl >Subject: Re: System V yacc / perl problem >Newsgroups: comp.sources.bugs,comp.unix.questions >In-Reply-To: <1675@van-bc.UUCP> >Organization: Microport Systems, Scotts Valley, CA >Date: 22 Feb 88 16:32:45 PST (Mon) >From: uunet!EDDIE.MIT.EDU!garp!ames!uport!amdcad!jmsully >Message-Id: <8802221632.AA15349@uport.UUCP> > >In regards to the article which you posted about problems with >Microport's System V/386: the yacc which was originally supplied >with Microport (and probably Bell Tech and Interactive) was compiled >without the -DHUGE option which is normally only set for 3b's and >VAXES. If you have a Microport support or update contract you can >download a yacc which was compiled with -DHUGE from our BBS system. >The numbers are: > >408-438-1680 >408-438-6687 >408-438-6567 > >-- >John M. Sully UUCP: ...!{sun | ucbvax | ihnp4}!amdcad!uport!techs >Microport Systems ARPA: uport!techs@ucscc.UCSC.EDU >Technical Support To recap I mentioned in my original posting that perl.y would blow yacc out of the water on my *tiny little 386 box* at work, but worked fine on my *big huge 68010 box* at home :-). Apparently Microport (and Bell Tech, possibly Interactive - I havn't checked) seem to think they are running on a small box. I have to admit that the Intel Mother board is one of the slower 386 systems around (16MHz, 1 wait state, etc). And ok, it only has 4.5 MB of RAM, 150MB of hard disk - but it still runs circles around your average 780, at least for small numbers of users. I wish these guys would get it right first time around. Now all I have to do to get the correct version from the Microport BBS is to subscribe to their silly support contract. Give me a break. Next job I'm going to specify Xenix/386, it can't be any worse than this. -- {ihnp4!alberta!ubc-vision,uunet}!van-bc!Stuart.Lynne Vancouver,BC,604-937-7532