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!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!nerds-end From: "Steven G. Kargl" Newsgroups: comp.compilers Subject: Re: LRSTAR 3.0: LALR(k) parser generator & lexer generator for C++ Date: Sat, 11 Feb 2012 18:31:29 +0000 (UTC) Organization: A noiseless patient Spider Lines: 36 Sender: johnl@iecc.com Approved: comp.compilers@iecc.com Message-ID: <12-02-013@comp.compilers> References: <12-02-004@comp.compilers> <12-02-006@comp.compilers> <12-02-009@comp.compilers> NNTP-Posting-Host: news.iecc.com X-Trace: leila.iecc.com 1329027425 64490 64.57.183.58 (12 Feb 2012 06:17:05 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Sun, 12 Feb 2012 06:17:05 +0000 (UTC) Keywords: tools, C++ Posted-Date: 12 Feb 2012 01:17:05 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:453 On Fri, 10 Feb 2012 13:24:41 -0800, Paul B Mann wrote: >> 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. Thanks. Yes, more changes are needed. First, one needs to comment out '#define DOS' in globals.h. Then, (on at least FreeBSD) one needs to remove '#include "malloc.h", because everything that at one time was declared in that file is now found in stdlib.h and inclusion of malloc.h leads to an error. Now, I hit the show stopper: laptop:kargl[240] g++ -o z -I. dfac.cpp |& more In file included from actions.cpp:4, from dfac.cpp:2: global.h:52:15: error: "or" cannot be used as a macro name as it is an operator in C++ -- steve