Cesar Strauss wrote:
> Charles Wilson wrote:
>> Cesar Strauss wrote:
>>> At this time, one still need msysDVLPR to build the MSYS DLL. Even
>>> so, a gcc-2.95 toolchain can still be updated with the new binutils
>>> and msysCORE-dev packages.
>> Hmm. I wonder why that is -- and if it's worth pursuing. We can either
>> a) do a bunch of archeology from the cygwin kernel source code circa
>> 2002 to determine what THEY needed to change in order to build with
>> gcc-3.x, and re-implement them, or
> I'll do a bit of debugging and archeology.
The issue seems to be related to the use of "new" inside the kernel.
Even a harmless simple line like "int * x = new int;" will stop it on
its tracks (no additional output, no stack dump, nothing).
By commenting a few lines which used "new", I managed to get strace
output, and even a bash prompt, but it doesn't get very far until it
gets to a code path that uses "new".