Date: Wed, 5 Jul 2000 09:22:36 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Frank Donahoe cc: DJGPP List Subject: Re: building flex 2.5.4 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Tue, 4 Jul 2000, Frank Donahoe wrote: > The failure of the build process with LFN enabled is because an > intermediate file `y.tab.c' is generated while the supplied Makefile > expects to see `y_tab.c'. What version of Bison do you have installed? I'm guessing that this problem appeared because the DJGPP port of the latest Bison produces Unix-style y.tab.c files under LFN, whereas the Bison port used for the original Flex build always produced y_tab.c. > Expect to use the supplied source under plain DOS or when LFN are > disabled. I think this is not a good idea. A better one would be to modify the Makefile to always DTRT. For example: parse.c: parse.y $(YACC) -d $(srcdir)/parse.y + @if exist y.tab.c ren y.tab.c y_tab.c + @if exist y.tab.h ren y.tab.h y_tab.h @sed '/extern char.*malloc/d' parse.tmp @mv parse.tmp parse.c @mv y_tab.h parse.h @rm -f y_tab.c The two lines marked with a plus sign + at the left margin are additions to the distributed Makefile. The file djgpp.sed should be changed accordingly, to produce these lines when configur.bat edits Makefile.in into Makefile.