public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19281] file format not recognized; treating as linker script
Date: Thu, 06 Jan 2005 15:42:00 -0000 [thread overview]
Message-ID: <20050106154204.14295.qmail@sourceware.org> (raw)
In-Reply-To: <20050105215329.19281.jeff@connectrf.com>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-06 15:42 -------
(In reply to comment #2)
> (In reply to comment #1)
> > This is not a gcc bug, either this is your bug and the .o file is not an
> object file or this is a binutils bug.
>
> Andrew, then perhaps you can explain why the exact same code compiles, links and
> runs fine in a Microsoft environment? So the only thing that has changed is I
> am using GCC.... Hmmmmm..
But GCC is only the compiler, not the assembler and linker, report this to the binutils project, <http://
sourceware.org/bugzilla/> which controls both the assembler and the linker, yes this is confusing but
correct.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19281
next prev parent reply other threads:[~2005-01-06 15:42 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 [this message]
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
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=20050106154204.14295.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).