public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: lrtaylor@micron.com
To: <eje4@cornell.edu>, <gcc-help@gcc.gnu.org>
Subject: RE: Help, zillions of undefined references
Date: Thu, 04 Mar 2004 21:34:00 -0000	[thread overview]
Message-ID: <363801FFD7B74240A329CEC3F7FE4CC4015F3A1C@ntxboimbx07.micron.com> (raw)

It looks like you're actually using GCC 2.96 (since your command is
g++296).  Try changing CC and CXX in your Makefile to be gcc and g++,
respectively.  That should get you using the right compiler that came
with the system.  You're probably actually just using a version of GCC
added to the system for backward compatibility.

Cheers,
Lyle

-----Original Message-----
From: gcc-help-owner@gcc.gnu.org [mailto:gcc-help-owner@gcc.gnu.org] On
Behalf Of Eric Evans
Sent: Thursday, March 04, 2004 2:18 PM
To: gcc-help@gcc.gnu.org
Subject: Re: Help, zillions of undefined references


> > I have a problem with a make I'm trying to do that is resulting in
> > lots and lots of undefined reference errors (see excerpt from error
> > output at end of message).  The programmer who wrote the program has
> > no idea why all the functions are not being linked in.  He says it
> > ought to work, and he's basically washed his hands of the thing and
> > tells me that it is up to me to deal with the problem.  In my web
> > searching I came across a message from a guy who said that the
> > __gxx_personality_v0 reference error could be fixed by using
LD=$(CXX)
> > in the Makefile, but I tried that and it didn't work.  I am using
gcc
> > 3.2.2 on RH linux version 9.  I'm using the default make program
that
> > comes with RH 9.  Is this a problem that could be fixed by switching
> > to a different version of gcc or a different version of make?  Is
> > there some linker option in the Makefile that I need to set in order
> > to get this thing to work?  Unfortunately I have little knowledge of
> > gcc and make.  Any advice I could get on how to proceed to
> > troubleshoot this problem would be greatly appreciated.  Thanks very
> > much.
>
>Start by posting the exact command line which causes the error.

OK, here it is:
/usr/bin/g++296 -o tsnake -g       -L/usr/local/tsnake_new/lib
-L/usr/X11R6/lib
  main.o xwindow.o make_pulldown.o  snaxel.o 
contour.o               tsnake.o dymprog.o io.o image.o lmesqCC.o 
fileDialogs.o InterestingArea.o              parameterDialogs.o 
minimization.o bSpline.o cutting.o   liblimin.a   -ltiff  -lm -lXm -lXt
-lX11

If anybody has any ideas about how I should proceed to try to eliminate
all 
these undefined references, I'd appreciate hearing them.  Thanks very
much.

Eric  

             reply	other threads:[~2004-03-04 21:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 21:34 lrtaylor [this message]
     [not found] <363801FFD7B74240A329CEC3F7FE4CC4015F3A1C@ntxboimbx07.micro n.com>
2004-03-05 14:29 ` Eric Evans
2004-03-05 14:37   ` Ian Lance Taylor
2004-03-05 15:18     ` Eric Evans
2004-03-05 15:44       ` Eljay Love-Jensen
2004-03-05 14:39   ` Eljay Love-Jensen
  -- strict thread matches above, loose matches on Subject: below --
2004-03-04 20:15 Eric Evans
2004-03-04 20:17 ` Ian Lance Taylor
     [not found] ` <5.2.1.1.2.20040304160333.00b778e8@postoffice9.mail.cornell .edu>
2004-03-04 21:16   ` Eric Evans

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=363801FFD7B74240A329CEC3F7FE4CC4015F3A1C@ntxboimbx07.micron.com \
    --to=lrtaylor@micron.com \
    --cc=eje4@cornell.edu \
    --cc=gcc-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).