Gregg C Levine wrote:
Hello from Gregg C Levine
Steve, here's something to consider. The folks at the eCos portion of
the site have disavowed the application of Win98, and even Win95 for
the building of their tool chain, despite the fact that Cygwin
normally runs there.
I don't think there is any special magic to the building of GCC under
Cygwin, and on a Win32 system.
There is actually a problem. I don't know how the GCC for x86 that comes
with Cygwin is built, but when I build GCC for Cygwin there is a memory
allocation problem in Cygwin itself. It allocates the same block more
than once, which screws up GCC. I developed a patch to work around this
problem last year, after much nagging from people living in the dark
distant days of Win98 and Win95. It detects when a allocation request
gets a block more than once, and requests again until it gets a
genuinely new one. I think Chris may have forgotten to include it in his
build of mspgcc for Windows.
I think it has to do with the fact that the filesystem is badly
managed there. We should Endeavour to run some tests, and then report
it to the Cygwin crowd. With appropriate data to back it up.
I reported the exact problem last year. I didn't get around to backing
it up with a test case.
Regards,
Steve
