This is the mail archive of the cygwin-apps@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Christopher Faylor wrote:
So, maybe I should rename the old version to gcc2 or release a version of 2.95.3 that names the binaries (i686-pc-cygwin-gcc2) differently. Any thoughts?
2) I'm trying to remove most of the spec file magic that dealt with
mingw and I think I've actually been pretty successful. However,
my new scheme relies on changing the machine name from i686-pc-cygwin
to i686-pc-mingw.
4) Since mingw is becoming so logically separated from gcc, it is possible that it could become a separate package. So, if "someone" was willing to supply a gcc-mingw package, it would actually be helpful. I don't think I could stand the pain of making this optional, so the gcc package would rely on the gcc-mingw package rather than the other way around. This would allow updating libgcc.a and libstdc++.a without requiring a new release of gcc. Hmm. I wonder if I should break libstdc++.a out of the gcc package. Urgh. Any suckers (cough) want to contribute a separate package?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |