|
From: Earnie B. <ear...@ya...> - 2001-01-04 13:27:09
|
Dan Egnor wrote: > Well, I can answer some of my own questions. You're right that many > components in Mumit's patch have not been applied to the gcc tree. > (Why not? It's been a year. Maybe they've only been rolled into the > development version which is heading for 3.0?) > > However, the patch does not apply cleanly to 2.95.3-prerelease -- far from > it. Dozens upon dozens of hunks are rejected. Some small parts of the > patch *have* been applied, apparently. A lot of this can be fixed by a > manual application process, but a few things look a little trickier. > > I don't think I'm qualified to sort out the mess (though I can try, but I > am not a gcc hacker), so I'm back where I started, asking the questions: > > * Will mingw32 support gcc 2.95.3 any time soon? (No, I don't mean binaries!) > That requires someone who can actively submit patches to the GCC source. I think that Paul Sokolovsky is sending patches for binutils but we haven't started looking at GCC yet. Anyone wishing to do so please speak up. > > * Can I accelerate this process by doing work myself, or by paying someone > else (in cash or beer or ...) to do this work? Yes. We would be willing to add you or anyone you deem to pay as a developer. MinGW has no commercial interest backing it so what little spare time the three or four of us have currently are all that gets put into it. The more spare time parts the faster we can work. > > * Is it easier to try to selectively apply the sjlj-exceptions patch > from 2.95.3 to the 2.95.2 source tree which *is* supported by mingw32? We would like to see any major stable release of GCC supported by MinGW. Adding the missing patches to the 2.95.3 source would be best. Mumit who was the active GCC win32 maintainer for a good period of time suddenly became quiet. He is well missed. No one has stepped up to fill is big shoes yet. If you're willing then please, go for it. > > * Is there some Master Documentation somewhere that I'm missing which > explains the current state of mingw32, how it relates to the various > versions of gcc (2.95.2 stable, 2.95.3 prerelease, various Cygwin > releases, development snapshots, ...), what patches are necessary, etc.? The only documentation can be found at the website. I am currently updating it, parts of it you can't see yet without special revelation. I'm creating a new FAQ for instance which you can view at http://www.mingw.org/trial/htdocs/mingwfaq_new.shtml. Warning, this may be in constant change as I work on it so click the Reload icon to be sure you see the changes. > > The "ate my balls" bug in question is a showstopper for us (without it, > exceptions are pretty much worthless), and we rely on mingw32 to generate > code for Windows that isn't burdened by the cygwin nightmare. If you are serious about paying someone, I suggest posting on the SourceForge jobs page as well as the http://www.gnujobs.com/ page. Cheers, Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |