public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "css20 at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39738] GCC cannot build itself for win64 platform
Date: Mon, 13 Apr 2009 08:12:00 -0000	[thread overview]
Message-ID: <20090413081200.17693.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39738-17562@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from css20 at mail dot ru  2009-04-13 08:11 -------
> Please make sure, that you have in your gcc source root directory the symbolic
> link "winsup" pointing to your prefix directory. Secondly, make sure you have
> the symbolic link "mingw" in your prefix directory, which has to point to
> x86_64-pc-mingw32 directory.

I use Gentoo Linux x64 as build OS with system compiler gcc 4.3.3,
configuration script arguments you can see in my first post. Both symbolic
links were created.. existing stddef.h file in winsup/mingw/include causes
error: 'NULL' was not declared in this scope during libstdc++ building (see my
earlier post).

> Yes, there is already one. But this bug is work-a-round by a temporary hack in
> our crt. So it shouldn't appear anymore.
Alltimes use -O0 is not the solution.. temporary CRT hacks too. Where I can get
more information about this bug ?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738


  parent reply	other threads:[~2009-04-13  8:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-11 15:00 [Bug libstdc++/39738] New: " css20 at mail dot ru
2009-04-11 18:47 ` [Bug libstdc++/39738] " paolo dot carlini at oracle dot com
2009-04-11 19:33 ` [Bug target/39738] " ktietz at gcc dot gnu dot org
2009-04-11 21:09 ` css20 at mail dot ru
2009-04-12  8:50 ` css20 at mail dot ru
2009-04-12 19:36 ` css20 at mail dot ru
2009-04-12 19:49 ` ktietz at gcc dot gnu dot org
2009-04-13  8:12 ` css20 at mail dot ru [this message]
2009-04-13  8:34 ` ktietz at gcc dot gnu dot org
2009-04-13 15:48 ` css20 at mail dot ru
2009-04-13 18:06 ` css20 at mail dot ru
2009-04-13 19:25 ` ktietz at gcc dot gnu dot org
2009-05-23  9:47 ` loaden at gmail dot com
2009-05-24  4:34 ` paolo dot carlini at oracle dot com

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=20090413081200.17693.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).