From: Chris F. <cg...@cy...> - 2000-10-09 19:59:06
|
On Mon, Oct 09, 2000 at 12:10:34PM -0700, Earnie Boyd wrote: >--- Chris Faylor <cg...@cy...> wrote: >>On Mon, Oct 09, 2000 at 10:19:19AM -0700, Earnie Boyd wrote: >>>It appears that the msvcrt library initialization files aren't setup >>>for some reason. As an alternative you could use the MinGW >>>distribution, see http://www.mingw.org for more information. >> >>I just used whatever Mumit provided back in April. As always, if >>someone wants to maintain the mingw part of things, please contact me. > >We're (mostly Paul S.) working on getting another MinGW package out. >As for fitting MinGW runtime into Cygwin we'll have to consider whether >we're interested. We tend to consider that -mno-cygwin isn't MinGW >since MinGW has it's own GCC/binutils. At one point, Mumit had vowed to keep everything in sync so that we would not suffer from the version skew that you are contemplating. That was why he uploaded everything to sourceware. Do you have a solution in mind for how to deal with this problem? You also asked a question about the w32api stuff which I responded to but you never indicated if you thought it was a good or a bad idea. Are you contemplating version skew there, too? Since you've forwarded this to the mingw-dvlpr mailing list, let me ask a generic question. Is anyone interested in making sure that the mingw tools in cygwin are up-to-date and consistent with your releases? In the last gcc release that I made, I tried to accomodate mingw include files and libraries but apprently I didn't get it right, judging by the complaints I've seen on the cygwin mailing list. So, this probably needs someone who knows the mingw layouts. As always, I'm willing to provide cvs access, web pages, ftp areas, or whatever it takes to accomodate this. I'll provide any assistance that I can, short of doing everything myself. cgf |