public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jeff at connectrf dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/19281] file format not recognized; treating as linker script
Date: Tue, 11 Jan 2005 20:03:00 -0000 [thread overview]
Message-ID: <20050111200313.6375.qmail@sourceware.org> (raw)
In-Reply-To: <20050105215329.19281.jeff@connectrf.com>
------- Additional Comments From jeff at connectrf dot com 2005-01-11 20:03 -------
Andrew,
If I take the exact same code, and compile it with VC++ it does not complain!
However, gcc the ONLY thing that has changed, will not compile code that works!
Why? Old wise one, must one rewrite entrie working applications just so gcc
understands??
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19281
next prev parent reply other threads:[~2005-01-11 20:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 21:53 [Bug c++/19281] New: " jeff at connectrf dot com
2005-01-05 21:56 ` [Bug c++/19281] " pinskia at gcc dot gnu dot org
2005-01-06 15:33 ` jeff at connectrf dot com
2005-01-06 15:42 ` pinskia at gcc dot gnu dot org
2005-01-10 18:46 ` jeff at connectrf dot com
2005-01-10 19:06 ` [Bug driver/19281] " pinskia at gcc dot gnu dot org
2005-01-10 19:09 ` pinskia at gcc dot gnu dot org
2005-01-11 17:44 ` jeff at connectrf dot com
2005-01-11 18:55 ` pinskia at gcc dot gnu dot org
2005-01-11 19:25 ` jeff at connectrf dot com
2005-01-11 19:31 ` pinskia at gcc dot gnu dot org
2005-01-11 20:03 ` jeff at connectrf dot com [this message]
2005-01-11 20:07 ` pinskia at gcc dot gnu dot org
2005-01-11 20:23 ` jeff at connectrf dot com
2005-01-11 20:26 ` pinskia at gcc dot gnu dot org
2005-01-11 20:29 ` dje at gcc dot gnu dot org
2005-01-11 21:03 ` jeff at connectrf dot com
2005-01-11 21:14 ` pinskia at gcc dot gnu dot org
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=20050111200313.6375.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).