public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/14666] Crossing from GNU/Linux to MinGW requires SEVERAL hacks
Date: Mon, 16 Aug 2004 00:00:00 -0000 [thread overview]
Message-ID: <20040816000042.7881.qmail@sourceware.org> (raw)
In-Reply-To: <20040321033350.14666.stl@nuwen.net>
------- Additional Comments From giovannibajo at libero dot it 2004-08-16 00:00 -------
Nat, Stephan, what's the status on this bug? Are the required modifications
already in HEAD?
Stephan, can you test what is the situation at the moment? If the required
hacks are only libstdc++ specific at this point, I can change the component and
let the v3 maintainers take care of this.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |giovannibajo at libero dot
| |it
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2004-08-16 00:00:41
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14666
next parent reply other threads:[~2004-08-16 0:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040321033350.14666.stl@nuwen.net>
2004-08-16 0:00 ` giovannibajo at libero dot it [this message]
[not found] <bug-14666-6097@http.gcc.gnu.org/bugzilla/>
2005-10-09 5:34 ` stl at nuwen dot net
2006-09-20 8:01 ` fxcoudert at gcc dot gnu dot org
2004-03-21 3:33 [Bug target/14666] New: " stl at caltech dot edu
2004-03-21 3:41 ` [Bug target/14666] " pinskia at gcc dot gnu dot org
2004-03-21 3:43 ` ian at wasabisystems dot com
2004-03-21 4:12 ` stl at caltech dot edu
2004-03-21 4:17 ` pinskia at gcc dot gnu dot org
2004-03-21 5:16 ` stl at caltech dot edu
2004-03-21 5:40 ` pinskia at gcc dot gnu dot org
2004-03-21 7:06 ` stl at caltech dot edu
2004-03-21 7:12 ` stl at caltech dot edu
2004-03-29 21:16 ` stl at caltech dot edu
2004-04-04 19:07 ` neroden at gcc dot gnu dot org
2004-04-05 8:21 ` stl at caltech dot edu
2004-04-05 8:57 ` stl at caltech dot edu
2004-04-05 9:57 ` stl at caltech dot edu
2004-04-07 0:58 ` neroden at gcc dot gnu dot org
2004-04-07 2:23 ` ian at wasabisystems 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=20040816000042.7881.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).