Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!nerds-end From: Paul B Mann Newsgroups: comp.compilers Subject: Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ Date: Fri, 10 Feb 2012 13:24:41 -0800 (PST) Organization: Compilers Central Lines: 20 Sender: johnl@iecc.com Approved: comp.compilers@iecc.com Message-ID: <12-02-009@comp.compilers> References: <12-02-004@comp.compilers> <12-02-006@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: leila.iecc.com 1328933908 49072 64.57.183.58 (11 Feb 2012 04:18:28 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Sat, 11 Feb 2012 04:18:28 +0000 (UTC) Keywords: parse, tools, C++ Posted-Date: 10 Feb 2012 23:18:27 EST X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: x330-a1.tempe.blueboxinc.net comp.compilers:449 > UNIX and unix-like system are case sensitive. There is no chance that > this code will build without a significant porting effort. For > example, you have Global.H in some directory; yet, your source has > '#include "global.h"'. > > It may also be advantageous to include simple instructions of which > files need to be compiled and the order. I have created a newer release: 3.0.211 in which I renamed the file names to all lower case and changed the #include filenames to match. I also added "readme.txt" files to the "source" directories which tells you how to compile under UNIX/Linux (i.e. compile the "lrstar.cpp" file, the "dfastar.cpp" file and the "dfac.cpp" file). I'm sure there will be more changes needed, because I'm not so familiar with UNIX. Paul Mann