www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/02/04/17:39:23

From: jlouwere AT galaxy DOT csc DOT calpoly DOT edu (Jan Louwerens)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: [Q] C++ linking: Should I be worried?
Date: 4 Feb 1997 18:51:50 GMT
Organization: Cal Poly Computer Science Dept.
Lines: 23
Message-ID: <5d80g6$6qa@waldorf.csc.calpoly.edu>
References: <854975234 DOT 266917 AT red DOT parallax DOT co DOT uk>
NNTP-Posting-Host: galaxy.csc.calpoly.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

John Eccleston (johne AT parallax DOT co DOT uk) wrote:
: Hi All,

: -----> Messages <-----
: gxx -c -O2 demo.cc
: gcc.exe: -lgpp: linker input file unused since linking not done
: gcc.exe: -lstdcx: linker input file unused since linking not done
: gcc.exe: -lm: linker input file unused since linking not done

: Could someone please explain what 'linker input file unused since linking
:  not done' means.

This is working just fine. In the make file, it first compiles each file 
seperately (gxx -c -O2 demo.cc). The '-c' option comples that file to an 
object file (demo.o), not to an executable file (demo.exe). Only after all 
the files all compiled into object files are they linked together into an 
executable file. The messages (above) that you are getting are just 
telling you that the linker isn't being used for that particular 
compilation (whenever the '-c' option is used). They are not error 
messages and are nothing to worry about. In fact, that is what should happen.

JL

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019