cvs.gedasymbols.org/archives/browse.cgi   search  
Mail Archives: djgpp/1997/03/19/04:53:50

Date: Wed, 19 Mar 1997 12:40:58 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Lee Simons <lee AT dialin DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: DJGPP C++ Compile problems...
In-Reply-To: <199703182117.VAA12391@post.dialin.co.uk>
Message-ID: <Pine.SUN.3.91.970319124034.19845H-100000@is>
MIME-Version: 1.0

On Tue, 18 Mar 1997, Lee Simons wrote:

> > > I'm having problems compiling c++ progs with DJGPP.  I've unzipped the
> > > necesary binary execs and libraries etc with the -d option, set the
> correct
> > > path and looked through the faq's.  I'm stuck.  Here is the error
> message,
> > > my path, and also my dir listing.  Thanks.
> > 
> > You didn't post the command line that you used to compile, and in this 
> > case it is a crucial info.  Judging by the error message, your command 
> > line was dead wrong.
> 
> Thanks for replying, the command lineI used is:
> 
> gcc man.exe -o man.cc -lgpp

Sure, that's backwards.  The correct command line is this:

	gcc -o man.exe man.cc -lgpp

The string immediately after -o is the file where you want your
output; you don't want the output to overwrite the source in man.cc,
do you?

Also, please read the file v2/readme.1st (available at the same site
where you get DJGPP): it includes some examples of compilation command
lines.  In particular, when linking C++ programs, it recommends using
gxx instead of gcc, because gxx searches all the relevant C++
libraries (-lgpp is only one of them) and will prevent you from
getting error messages from the linker saying that it didn't find some
functions.

- Raw text -


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