Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Thu, 9 Oct 2003 21:11:21 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: "Kai Xu (Kevin)" <kaixu AT itee DOT uq DOT edu DOT au>
cc: cygwin AT cygwin DOT com
Subject: Re: undefined reference to 'class::function' error
In-Reply-To: <02dd01c38eca$d093a1e0$db406682@itee.uq.edu.au>
Message-ID: <Pine.GSO.4.56.0310092107570.20462@slinky.cs.nyu.edu>
References: <028301c38e65$3d4a5ab0$db406682 AT itee DOT uq DOT edu DOT au>
 <Pine DOT GSO DOT 4 DOT 56 DOT 0310090904550 DOT 15176 AT slinky DOT cs DOT nyu DOT edu>
 <028901c38e6a$a028eca0$db406682 AT itee DOT uq DOT edu DOT au>
 <Pine DOT GSO DOT 4 DOT 56 DOT 0310090950450 DOT 15176 AT slinky DOT cs DOT nyu DOT edu>
 <02af01c38ec7$9c29d850$db406682 AT itee DOT uq DOT edu DOT au>
 <Pine DOT GSO DOT 4 DOT 56 DOT 0310092053140 DOT 20462 AT slinky DOT cs DOT nyu DOT edu>
 <02dd01c38eca$d093a1e0$db406682 AT itee DOT uq DOT edu DOT au>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Kevin,

"Please do not Cc: me" meant that all communication should go to the list
(hence the Reply-To:) and that I will read your messages on the list.
Please do not send personal e-mail with Cygwin questions unless
specifically requested.  All Cygwin questions (and answers, hopefully)
should go to the Cygwin list -- the questions to address a larger
audience, and the answers to help others avoid asking the same questions
over and over.
	Igor

On Fri, 10 Oct 2003, Kai Xu (Kevin) wrote:

> Yes, indeed! I get it working and thank you so much! That's what I used to
> do when program c++ under windows, but seems not the right way for UNIX. I
> will send email to list after this one :-)
>
> Kevin
>
> ----- Original Message -----
> From: "Igor Pechtchanski" <pechtcha AT cs DOT nyu DOT edu>
> To: "Kai Xu (Kevin)" <kaixu AT itee DOT uq DOT edu DOT au>
> Cc: <cygwin AT cygwin DOT com>
> Sent: Friday, October 10, 2003 10:57 AM
> Subject: Re: undefined reference to 'class::function' error
>
>
> > Kevin,
> >
> > Please don't Cc: me, I read the list (I set the Reply-To: for a reason).
> > More below.
> >
> > On Fri, 10 Oct 2003, Kai Xu (Kevin) wrote:
> >
> > > As I am not good at c++, I am not sure what you mean by "link the file
> that
> > > defines this function into the resulting executable". I just include the
> .h
> > > file that defines the function in the main .cpp file. The compile
> command I
> > > used is:
> > >
> > > g++ sp.cpp (the main cpp file)
> > >
> > > I guess there could be some problem here.
> > >
> > > Kevin
> >
> > Aha, so you aren't linking the file in.  This is a general C/C++ question,
> > not Cygwin specific, and thus off-topic for this list.  For more details,
> > read up on "separate compilation" and "multiple source files" in any C/C++
> > book.  For a short term solution, simply add the cpp file that defines the
> > missing function to the compile command, but if you need further help on
> > similar issues, please try a C/C++ user support list/newsgroup or read
> > an intro to programming book.
> > Igor

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/