public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "loaden at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39738] GCC cannot build itself for win64 platform
Date: Sat, 23 May 2009 09:47:00 -0000 [thread overview]
Message-ID: <20090523094652.10603.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39738-17562@http.gcc.gnu.org/bugzilla/>
------- Comment #12 from loaden at gmail dot com 2009-05-23 09:46 -------
(In reply to comment #2)
> (In reply to comment #1)
> > Are you sure your entire compiler is up to date, not just the library? And the
> > build and install directories are clean? Because your first lines of failure
> > involve bits of the library which *require* a consistent simultaneous change in
> > the C++ front-end, and well, nobody is experiencing similar problems anywhere.
> > Not that this code is target-independent.
> >
> > CC-ing Jason, the author of such code, to be sure.
> >
>
> Well, on 4.4 branch there was a patch introducing the winsup link, which got
> necessary for building libstdc++. We solve this by setting up in gcc's source
> tree a symbolic link "winsup" pointing to the sysroot (prefix) directory.
>
> Cheers,
> Kai
>
Hi, I have same question when build MinGW on Ubuntu, i use Cross compiler.
and, can you tell me: where is the "winsup" patch? and how to create a link to
gcc's source?
Thanks!
--
loaden at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |loaden at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738
next prev parent reply other threads:[~2009-05-23 9:47 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
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 [this message]
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=20090523094652.10603.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).