This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.8.1 building fails
- From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- To: Ignas <ignas2526 at gmail dot com>
- Cc: David Kredba <nheghathivhistha at gmail dot com>, gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Sat, 15 Jun 2013 14:49:44 +0100
- Subject: Re: GCC 4.8.1 building fails
- References: <CAD9k0GPqot-6ZTHXiQmfks_-H+6DwzLsyR0SyOfE96=1Xm49nQ at mail dot gmail dot com> <CAH6eHdSXgj6q+8grEv1xOyCRvCfESJweBHBnuS_cimBxv0FG4A at mail dot gmail dot com> <CAD9k0GM0fOc7eES-HCCudMCBUnwB2Z-=C3u604zS4XJs8fvhCQ at mail dot gmail dot com> <CAH6eHdTaA=zQv-Mmz_0XGt_iE-YakPmSM_12VNbBFacJ1f+vJg at mail dot gmail dot com> <CAD9k0GM4e8WdOniU_3jpuAwBWdcWjPYgwYLkmGRBNi6=6nf7nQ at mail dot gmail dot com>
On 15 June 2013 14:18, Ignas wrote:
> Now I'm wondering, what is the most supported and reasonable way to
> compile gcc on windows? without any sdk's, consoles, editors, etc.
> just plain good gcc and its components what would produce native
> windows binaries what do not require some special dlls like cygwin
> does.
MinGW is the best and also the worst way, it's the only way.