From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: New Flex versions
Date: Thu, 10 Apr 2003 21:23:27 +0200
Message-ID: <000c01c2ff96$a96b1620$2302a8c0@dualzastai>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.3416
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Reply-To: djgpp-workers AT delorie DOT com

Flex is currently in a run up to 2.6 (currently at 2.5.31).

In trying to build it under windows (MSVC.NET, not cygwin),
I found portability issues that also apply to DJGPP.
Flex (like bison) now runs M4 in a subprocess to (pre)process
the skeleton - it uses fork/exec/wait/pipe to use this, which
will not work under DJGPP - what's worse, it seems it does not
always exec() in a fork, so popen() probably won't solve this.

I'll be spending a little time looking into this for my windows
build this weekend, but whoever maintains flex for DJGPP should
probably take a look as well at some point (loking for yet
another project Richard? :-) ) - I'm sure we'll want a working
flex 2.6 if and when it is released.

Sources are at lex.sourcefourge.net.