Cygwin 32-bit partial fix: memory map

[Vibhu M. <vi...@ho...>]

System: Windows 10, 6 GB RAM, Cygwin (64-bit)
clisp revision: f1aa42219433f019c05e707220538b3634bc233c

I'm now building 32-bit binaries as per INSTALL.windows.
("3. Binaries for the Cygwin environment.")

The build produced this error:
Warning: reserving address range 0x80000000...0x8000ffff that contains 
memory mappings. clisp might crash later!

The attached change to lispbibl.c got past it. But it was guesswork from 
scavenging this list, so I don't know if what I've done is definitely 
right. If I've understood correctly, one must pick a range not shown in 
the log, so I did that. (The range I selected was the same as what a 
neighbouring part of lispbibl.c had specified for win32_native/I80386.)

The build then gets at least as far as producing lisp.exe and 
lispinit.mem that runs in a sane looking way to me.

----
Minor aside:

I haven't thought about this deeply and may be wrong, but it may be 
worth improving the Makefile in one way. I think if make fails with a 
memory map complaint as above and you change no files but simply run 
make again, it continues and produces a spurious lisp.exe . It would be 
better for make to fail on its second invocation just as it did on its 
first. I think the reason for it not failing on second invocation is 
that marc.out has already been created, so it thinks that step 
succeeded. One fix is to break marc.out creation into two steps: 1) 
marc.out.tmp, and if check or whatever succeeded only then to 2) mv 
marc.out.tmp marc.out

----
As a separate matter, the build doesn't get as far as making a base 
directory. I'll post separately about that as it looks unrelated. So 
far, I'm happy enough to have got a lisp.exe and lispinit.mem in the 
build directory itself. Without the attached fix, I wouldn't get a sane 
lisp.exe/lispinit.mem .