From: <dan...@ya...> - 2000-11-21 00:20:44
|
--- Earnie Boyd <ear...@ya...> 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? > > 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/, etc. > Are there any precedents for that in other GCC targets? How would that affect existing configure scripts? Regards Danny _____________________________________________________________________________ http://clubs.yahoo.com.au - Yahoo! Clubs - Join a club or build your own! |