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

I uninstalled MinGW and installed it again with all the latest stuff.
I tried to compile gcc 2 more times, without any luck. I defined
constants with paths to MinGW's include and lib folder, I tried to use
configure closely resembling the one used to compile gcc what came
with MinGW:
configure --disable-sjlj-exceptions --enable-shared --enable-libgomp
--disable-win32-registry --enable-lib-stdcxx-debug
--enable-version-specific-runtime-libs --build=mingw32 --prefix=/mingw
It always fails when it gets to a part of making things inside a build
folder, previously it was [objdir]/i686-pc-mingw32, this time it was
[objdir]/mingw32. Second time, I've tried to compile with binutils
source inside [srcdir].


Based on all that, I conclude, that it is a bug with gcc in area
related to Windows, MinGW, or compiling itself.
As I've said in my first email, gcc configures and makes all
libraries(gmp, mpfr, mpc, etc.) successfully, I've checked
[objdir]/[library name], they have .a, .o, etc. sometimes .exe and
.dll files, indicating what my MinGW installation is working fine, I'm
pretty sure it would have never compiled all that successfully if it
was broken. I've also checked [objdir]/gcc , it was also compiled
successfully.
Problem always starts somewhere when it tries to make the
[objdir]/[build folder], it appears to me, that at this point, gcc is
using its own compiled binaries to compile further, and that's when it
crashes.

  parent reply	other threads:[~2013-06-15  8:45 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 [this message]
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='CAD9k0GM0fOc7eES-HCCudMCBUnwB2Z-=C3u604zS4XJs8fvhCQ@mail.gmail.com' \
    --to=ignas2526@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@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).