public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Thomas Singleton [Eidos]" <singleton@skynet.be>
To: help-gcc@gnu.org
Subject: error message : linker input file unused since linking not done
Date: Fri, 31 Dec 1999 22:24:00 -0000	[thread overview]
Message-ID: <843j8g$len$1@news0.skynet.be> (raw)
Message-ID: <19991231222400.uG_bBZJCLWCLX1Rq5mBdQV3D7asIwo8AP3DSFu347mA@z> (raw)

hello,
in order to follow a book's test procedure to see if the compiling/linking
of C programs work, i created a hello.c
file with the famous 'printf("Hello World!");' then (always following the
instructions) did :
$gcc -c -Wall -D_GNU_SOURCE hello.c -o hello.o
then
$gcc -c hello.o hello.c
which reported :
gcc: hello.o : linker input file unused since linking not done

i made a search for that message on gcc.gnu.org, and found a few linked
messages but they were all about merging two or more source into the same
object which is not my case, so i decided to post this

Thank you for any advices
Thomas

i'm using RH 6.0 with kernel 2.2.5-15 and gcc --version reported :
egcs-2.91.66


             reply	other threads:[~1999-12-31 22:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-25 15:19 Thomas Singleton [Eidos] [this message]
1999-12-25 23:38 ` Peter A. Friend
1999-12-25 23:43   ` Peter A. Friend
1999-12-31 22:24     ` Peter A. Friend
1999-12-31 22:24   ` Peter A. Friend
1999-12-26  1:42 ` error message : linker input file unused since linking not done SOLVED Thomas Singleton [Eidos]
1999-12-31 22:24   ` Thomas Singleton [Eidos]
1999-12-31 22:24 ` error message : linker input file unused since linking not done Thomas Singleton [Eidos]

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='843j8g$len$1@news0.skynet.be' \
    --to=singleton@skynet.be \
    --cc=help-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).