public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Ignas <ignas2526@gmail.com>
Cc: David Kredba <nheghathivhistha@gmail.com>,
	gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GCC 4.8.1 building fails
Date: Sat, 15 Jun 2013 13:51:00 -0000	[thread overview]
Message-ID: <CAH6eHdTGRwhDxej7-X7qyLHNM7bVAerwD++v1fJT36bJUaEdyQ@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRMPqeYzRmxNmt++1Q6v+rsr7yH51X3A_sTxcmOH=6mDg@mail.gmail.com>

On 15 June 2013 14:49, Jonathan Wakely wrote:
> 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.

But unless you really need to compile it yourself just install a
pre-built version and save yourself all the trouble of building it.

  reply	other threads:[~2013-06-15 13:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14  9:31 Ignas
2013-06-14 11:10 ` Jonathan Wakely
2013-06-15  8:12   ` Ignas
2013-06-15  8:45   ` Ignas
2013-06-15 11:54     ` Jonathan Wakely
2013-06-15 13:18       ` Ignas
2013-06-15 13:49         ` Jonathan Wakely
2013-06-15 13:51           ` Jonathan Wakely [this message]
     [not found]           ` <CAF1jjLs=o8=BmirCS6S-e_Qn_y5paJxC7YuTyc66enmtQZVBXg@mail.gmail.com>
2013-06-15 17:11             ` Jonathan Wakely
2013-06-15 17:41               ` NightStrike
2013-06-15 23:31                 ` Ignas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAH6eHdTGRwhDxej7-X7qyLHNM7bVAerwD++v1fJT36bJUaEdyQ@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=ignas2526@gmail.com \
    --cc=nheghathivhistha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).