Mail Archives: djgpp/2001/12/04/13:11:16
On Fri, 30 Nov 2001, JT Williams wrote:
> -: -: This is a port of GNU Bison 1.30 to MSDOS/DJGPP.
> -:
> -: Is it possible to build this out of the box (under bash), using the usual
> -: configure/make/install procedure?
I have never tested the configure/make/install procedure and it was never my
intention to allow this. If only SFN support is available that procedure
will probably fail.
The intention was that the package should be configurable and compilable
under plain DOS as well as under Win9X using the provided files in the
djgpp subdir (config.bat, config.sed and config.site).
The procedure tested by me was djgpp\config/make/install.
I have tested this on plain DOS 7.10 (win98se) using command.com and
on DOS 6.22 using 4dos.com. In both cases it works. Very unfortunately,
I have never tested it on DOS 6.22 with command.com. In this case it fails
as you have reported.
> -: The DOS batch file supplied with the source archive complains
> -: about insufficient environment space, no matter how much environment space
> -: I request at boot time
>
> Only because this error handler is invoked too generally; the actual
> error may well have nothing to do with the size of the environment.
>
> BTW, I could not get the file djgpp/config.bat to run without first
> shortening several of its command lines (plain DOS 5.0). The batch
> file also appears to be sensitive to the _order_ of its arguments,
> and _all_ arguments must be specified, e.g.,
>
> djgpp\config.bat no-nls no-cache no-dep .
I was able to reproduce this on DOS 6.22 using command.com. I still have
not fully understood what is going wrong here and how to solve this problem.
It seems to be that config.bat must be rewritten from scratch, but this time
it must be written completely under DOS 622 or a previuos version using command.com.
IMHO, it is important to realize that the bison package should always compiled
with LFN available. Bison's testsuite is generated by AUTOCONF and the AUTOCONF
macros do not know anything about the file name extension used by bison on
plain DOS. The consequence of this is that around 50% of all tests will fail
if LFN is not available.
IIRC this has been told in the readme file. Of course, bison.exe _will work_
with LFN or without LFN support. It is only the testsuite that fails.
Thank you for calling my attention to this problem. I have no easy solution
handy now but I will update this port as soon as I have rewritten config.bat.
(If you want/need to answer me, please cc to me too. I am only on the
weekly-digest list.)
Regards,
Guerrero, Juan Manuel
- Raw text -