Mail Archives: djgpp/2000/09/21/12:22:40
On 21 Sep 2000, Esa A E Peuha wrote:
> pavenis AT lanet DOT lv writes:
>
> > Another idea could be trying --enable-c-cpplib when configuring gcc.
> > I tried this with egcs-1.1.2 and got binaries where cpp is integrated into
> > cc1, cc1plus, etc. I don't know how it lives together with Pascal and
> > I also haven't tried it with gcc-2.95.X.
>
> It could be possible, but I don't see why it should be done. Having a
> separate cpp executable doesn't cause any problems that could be solved
> by cpplib (at least AFAIK), and since djgpp doesn't support dynamical
> linking, that would just waste disk space. (Yes, cpp.dxe would be a
> possibility, but I doubt it would be worth the trouble.)
>
Original message stated that adding GNU Pascal to gcc-2.95.2 sources
makes number of processes for 'make all-gcc ...' too large for Win9X
DPMI server to handle (each process leaks 4 descriptors, so after about
2000 processes we'll have crash). Integrating cpp into cc1, cc1plus,
etc will make number of processes perhaps 20-30% less so it would be
possible to finish build but of course it's only a temporary cure
Ather possible workarounds:
- changing DJGPP to use v2load.c for loading and starting
DJGPP programs instead of asking DOS to run them (similary as
it is being done for DJGPP debugging support). But I think it's
rather serious change and requres much work .... . I hope it
could also at least partially solve DJGPP problems with Win2000
(maybe, but I'm not sure ...)
- for gcc only: we could try building DJGPP port of gcc with
Canadian-cross type build for example under Linux. I myself
am using gcc-2.95.2 binaries for DJGPP I build such way in
end of March. In this way we could avoid such M$ bugs
Andris
- Raw text -