Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!gem.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!umd5!cgs
From: cgs@umd5.umd.edu (Chris G. Sylvain)
Newsgroups: comp.os.minix
Subject: Re: Distributability Question (output of Lex and Yacc)
Keywords: Lex *AND* Yacc
Message-ID: <5656@umd5.umd.edu>
Date: 19 Nov 89 22:39:42 GMT
References: <5647@umd5.umd.edu> <1702@bruce.OZ>
Reply-To: cgs@umd5.umd.edu (Chris G. Sylvain)
Organization: University of Maryland, College Park
Lines: 20

In article <1702@bruce.OZ> cechew@bruce.OZ (Earl Chew) writes:
>From article <5647@umd5.umd.edu>, by cgs@umd5.umd.edu (Chris G. Sylvain):
>>   Since MINIX lacks both Lex and Yacc  ..
>
>I thought that we had Flex for Minix. Am I mistaken?
>

Thanks for your reply, but let me emphasize the key part of my post:

--> MINIX lacks **both** Lex and Yacc.
I need the output of a pair of files, one for each tool to port cdecl.

   I've had one post suggest using GNU's Lex and Yacc workalikes, but I don't
have them handy. If I can distribute the output generated by AT&T derived
tools, then I'll take the path of least resistance (I have those handy).
-- 
--==---==---==--
Slithy: Lithe and slimy. _Lithe_ is the same as _active_
--   ARPA: cgs@umd5.UMD.EDU     BITNET: cgs%umd5@umd2   --
--   UUCP: ..!uunet!umd5.umd.edu!cgs                    --