From: Paul G. <pga...@te...> - 2000-11-22 00:18:38
|
Hi folks, On 20 Nov 2000, at 14:34, the Illustrious Earnie Boyd wrote: > --- Paul Sokolovsky <pf...@us...> wrote: > > > > Well, but I found 'i386-mingw...' stuff in some other > > places, for > > example in lib/gcc-lib/mingw32/2.95.2/cpp.exe and in specs - I > > may imagine it gives you those paths. But why I have all ok ;-? > > Well, I will destroy them completely. > > > > Can we drop the 32 from mingw? Or should we consider that > platform specific enough to leave it there? I say drop it. No sense in maintaining it since the expectation was originally to be open to 64bit as well as 32bit mingw. A main reason for the name mingw, as opposed to mingw32 was due to Mumits desire to do just what I outlined above. In fact there are already headers included with mingw that are set up to handle 64bit stuff. > > My preference would be to remove it and identify the 32bit vs > FOObit via a specific directory when needed. E.G.: > lib/gcc-lib/mingw/2.95.2/32bit/, lib/gcc-lib/mingw/2.95.2/64bit/, I agree. Peace, Paul G. > etc. > > Cheers, > > ===== > Earnie Boyd > mailto:ear...@ya... > > --- <http://earniesystems.safeshopper.com> --- > --- Cygwin: POSIX on Windows <http://gw32.freeyellow.com/> --- > --- Minimalist GNU for Windows <http://www.mingw.org/> --- > > __________________________________________________ > Do You Yahoo!? > Yahoo! Calendar - Get organized for the holidays! > http://calendar.yahoo.com/ > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > http://lists.sourceforge.net/mailman/listinfo/mingw-dvlpr > Nothing real can be threatened. Nothing unreal exists. |