public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ignas <ignas2526@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: GCC 4.8.1 building fails
Date: Sat, 15 Jun 2013 08:12:00 -0000	[thread overview]
Message-ID: <CAD9k0GPJYTBauFxBUK8w9KMDOcYMUfzXH=FWsuQ=2oE5WU1Akw@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdSXgj6q+8grEv1xOyCRvCfESJweBHBnuS_cimBxv0FG4A@mail.gmail.com>

No, I have fine and working installation of MinGW what has stdio.h and
assert.h files in the include folder. Is there a way to perhaps
explicitly tell where is MinGW's include folder is?

On Fri, Jun 14, 2013 at 2:10 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On 14 June 2013 10:31, Ignas wrote:
>> Hello,
>> I've tried to build GCC 4.8.1 numerous times without any luck.
>> Build, host, and target system: i686-pc-mingw32.
>> I'm using MinGW Shell, gcc -v 4.6.2 ; g++ -v 4.7.2
>
> It looks as though you don't have basic files like <stdio.h> and
> <assert.h> installed where GCC can find them.  I don't know how to
> install them for mingw, but would guess they should be provided by the
> mingw-runtime or win32api packages.

  reply	other threads:[~2013-06-15  8:12 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 [this message]
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
     [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='CAD9k0GPJYTBauFxBUK8w9KMDOcYMUfzXH=FWsuQ=2oE5WU1Akw@mail.gmail.com' \
    --to=ignas2526@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    /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).