Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=2946398
By: gnuwin32

Some work is delegated to M4, simply because that's the way Bison has been 
designed
since 1.875.

M4 is provided with Bison. If you put it in the same folder as Bison, Bison
should be able to find it. I don't know much about Borland, so I cannot tell
why bison halts when called from Borland.

It should not be too difficult to compile your own Bison with Borland, since
its code is fairly standard C. Perhaps you may be forced to provide dummies
for some Unix functions that do not exist in msvcrt.dll. Also, you must find
some way to circumvent fork by using spawn (or use the patches provided with
the sources on GnuWin32).

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=74807


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
GnuWin32-Users mailing list
GnuWin32-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gnuwin32-users

Reply via email to