From: "Thomas J Amato" <Thomas_J_Amato@raytheon.com>
To: nathan@cs.bris.ac.uk
Cc: gcc-help@gcc.gnu.org, nathan@cs.bris.ac.uk
Subject: Re: Stray characters in .o files....
Date: Wed, 19 Jun 2002 09:16:00 -0000 [thread overview]
Message-ID: <OFBE117918.E6E22F3A-ON85256BDD.0058BA34@and.us.ray.com> (raw)
After I submitted this to the message board I realized that I had the -x
c++ (not sure how it got there ;-o ) option on the command line. Pilot
error.
Tom
Nathan Sidwell
<nathan@acm.org> To: Thomas J Amato
Sent by: <Thomas_J_Amato@raytheon.com>
nathan@compsci.br cc: gcc-help@gcc.gnu.org
istol.ac.uk Subject: Re: Stray characters in .o files....
06/19/02 11:30 AM
Please respond to
nathan
Thomas J Amato wrote:
> I'm hoping that someone has seem this. I am getting a large number of
> errors when I go to link my test program (below is a snippet):
>
> .sun_gcc_dbg/test_harness.o:222:107: warning: null character(s) ignored
> .sun_gcc_dbg/test_harness.o:222:110: warning: null character(s) ignored
I'd guess that the .o file is not being recognized for what it is,
and it is being processed as source of some kind.
1) How are you invoking the linker?
2) What does the -v (verbose) flag tell you?
nathan
--
Dr Nathan Sidwell :: Computer Science Department :: Bristol University
The voices in my head told me to say this
nathan@acm.org http://www.cs.bris.ac.uk/~nathan/ nathan@cs.bris.ac.uk
next reply other threads:[~2002-06-19 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-19 9:16 Thomas J Amato [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-19 9:06 Thomas J Amato
2002-06-19 7:55 Thomas J Amato
2002-06-19 8:32 ` Nathan Sidwell
2002-06-19 8:33 ` Zack Weinberg
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=OFBE117918.E6E22F3A-ON85256BDD.0058BA34@and.us.ray.com \
--to=thomas_j_amato@raytheon.com \
--cc=gcc-help@gcc.gnu.org \
--cc=nathan@cs.bris.ac.uk \
/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).