[patch] Fix i386-mingw32 build failure
Mark Mitchell
mark@codesourcery.com
Wed Aug 10 22:32:00 GMT 2005
Andreas Schwab wrote:
> Mark Mitchell <mark@codesourcery.com> writes:
>
>
>>The even more correct solution is to not build anything with the
>>compiler (including libgcc) until after it is installed. Then, it will
>>just look where it would normally look, and all will be well.
>
>
> You sure don't want to overwrite a compiler that is known to work with a
> compiler that is incomplete, never tested, and perhaps completely broken.
I certainly didn't mean to suggest that -- but that doesn't mean you
can't install the compiler somewhere. That's part of why people have
worked hard to make it relocatable. We've had this entire discussion
before, and as far as I can tell, there's agreement-in-principle: you
build things, install them in a staging area, and then copy/reinstall
into a final location when you're done. That avoids all the complicated
symlinks/-B/-L/-I options -- which are not only complex, but also have
been known to mask problems in the installed compiler. (Things work at
build time, but not at install time.)
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
More information about the Gcc
mailing list