--- Brian Dessent <brian@...> escribió:
> David Lucena wrote:
> > And other thing. I could use the stock version of gcc from mingw, but I suposse that I could
> > use the latest version of gcc and that I'll have no problem using gcc under a mingw32
> > will I?
> You mean compiling a stock FSF version? Well, first of all, that will
> have no effect on the Vista issue that this thread ostensibly relates
> to. That is entirely determined by whether or not you build gcc with
> the updated MinGW io.h, it has nothing to do with gcc itself.
> As far as having "no problems", that's a matter of personal taste and
> pain threshold. If you follow FSF gcc you get the latest features and
> optimizations, but win32 is still sort of a second class citizen and so
> often times you will find that some features are poorly tested, or that
> some languages (especially Ada and Java) won't even build. Heck, even
> getting a successfull build of just the default languages (C, C++,
> Fortran) can be extremely tricky, and is most definitely not something
> I'd suggest for a newbie.
> If you stick to just C or C++ the pain would be minimal, assuming you
> get past any build blockers. However, there are still outstanding
> issues that are fixed only with MinGW-local patches, not upstream. So,
> in general, no, if you want a stable and reliable gcc you must use the
> patched MinGW releases.
So I will have to download the latest mingw from its svn server, change the io.h, get the latest
gcc also from svn server and build it using for example stock binary version of gcc 3.4.5 adding
the spoken preprocessor defines to the corresponding flags. That would be enough for C, C++?
LLama Gratis a cualquier PC del Mundo.
Llamadas a fijos y móviles desde 1 céntimo por minuto.