public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eilmsteiner Reinhard <r.eilmsteiner@paysafecard.com>
To: "Miguel Ramírez" <mramirez@iua.upf.es>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Linker trouble
Date: Fri, 07 Feb 2003 12:40:00 -0000	[thread overview]
Message-ID: <1044621749.2569.24.camel@vie-nb-eilm2> (raw)
In-Reply-To: <002501c2ce85$c2201590$ab3791c1@mtg171>

Hi!

Nothing what I wrote was true!

I didn't remove the old .o-files.

I apologize!

Thx,
RE

On Fri, 2003-02-07 at 09:49, Miguel Ramírez wrote:
> 
> Hmmm. If it's not an ABI-related issue, the Occam's razor says that
> the symbols are not in the binary for some unknown reason - then the
> library build system could be the culprit... check with 'objdump -t' the
> contents
> of the binaries symbol tables - maybe that gives you some insight.
> 
> Good luck!
> 
> Miguel Ramírez.
> 
> ----- Original Message -----
> From: "Eilmsteiner Reinhard" <r.eilmsteiner@paysafecard.com>
> To: "'Miguel Ramírez'" <mramirez@iua.upf.es>
> Cc: <gcc-help@gcc.gnu.org>
> Sent: Thursday, February 06, 2003 12:14 PM
> Subject: RE: Linker trouble
> 
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Yes, unfortunately they are....
> Do you have other ideas?
> 
> Regards,
> Reinhard.
> 
> - -----Original Message-----
> From: Miguel Ramírez [mailto:mramirez@iua.upf.es]
> Sent: Thursday, February 06, 2003 11:39 AM
> To: Eilmsteiner Reinhard; gcc-help@gcc.gnu.org
> Subject: Re: Linker trouble
> 
> 
> Are the libraries 'classlogging' and 'classgeneral' compiled with the same
> gcc version?
> 
> Remember that 3.2 C++ ABI is incompatible with the one of previous releases,
> so recompiling
> the libraries should do the trick.
> 
> Miguel.
> 
> - ----- Original Message -----
> From: "Eilmsteiner Reinhard" <r.eilmsteiner@paysafecard.com>
> To: <gcc-help@gcc.gnu.org>
> Sent: Thursday, February 06, 2003 9:27 AM
> Subject: Linker trouble
> 
> 
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi!
> >
> > I'm trying to link a program which used to work on a older version of gcc
> > and ld.... Now I have gcc 3.2 and ld 2.13.90.0.2
> > After all has been compiled (including the libraries classlogging and
> class
> > general (the latter uses the former) a do:
> > g++ -ggdb -I../../include -L../../lib -o logserver main.o clogserver.o
> > clogserverexception.o -lclasslogging -lclassgeneral
> > and get:
> > main.o: In function `main':
> > /home/eilmrein/Documents/proj/c/src/logserver/main.cc:27: undefined
> > reference to `CCommandLine::CCommandLine[in-charge](int, char const**)'
> > clogserver.o: In function
> > `CLogServer::GoToLoggingStage(CLogServer::TLogStage, bool, CCommandLine
> > const*)':
> > /home/eilmrein/Documents/proj/c/src/logserver/clogserver.cc:91: undefined
> > reference to `CString::operator()() const'
> > /home/eilmrein/Documents/proj/c/src/logserver/clogserver.cc:91: undefined
> > reference to `CString::~CString [in-charge]()'
> > /home/eilmrein/Documents/proj/c/src/logserver/clogserver.cc:91: undefined
> > reference to `CString::~CString [in-charge]()'
> > /home/eilmrein/Documents/proj/c/src/logserver/clogserver.cc:111: undefined
> > reference to `CString::operator()() const'
> > /home/eilmrein/Documents/proj/c/src/logserver/clogserver.cc:111: undefined
> > reference to `CString::~CString [in-charge]()'
> > /home/eilmrein/Documents/proj/c/src/logserver/clogserver.cc:111: undefined
> > reference to `CString::~CString [in-charge]()'
> >
> > When I do a "nm -C libclassgeneral.a" I can see these member functions
> > however.
> > Does it have anything to do with those [in-charge]/[not-in-charge] tags,
> > which I've not seen on my old version. (Please explain!)
> >
> > How do I get my program linked again?
> >
> > Thx,
> > Reinhard.
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
> >
> > iQA/AwUBPkIceFaO5+5ahqodEQLqhgCg4aUag+SIvqU3sCM0UcpaqpYb6pIAnRnG
> > Hll3+bgudQyOQCQ6enbQtRS0
> > =e2oI
> > -----END PGP SIGNATURE-----
> >
> 
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
> 
> iQA/AwUBPkJDqlaO5+5ahqodEQINvQCdElDZUfq3zyZrVg/ymfytDxaPc1gAoPez
> IZSPbnSBX+Powu2lxbOQLnR4
> =3H8A
> -----END PGP SIGNATURE-----
> 


  parent reply	other threads:[~2003-02-07 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 11:14 Eilmsteiner Reinhard
2003-02-07  8:54 ` Miguel Ramírez
2003-02-07 12:33   ` Eilmsteiner Reinhard
2003-02-07 12:40   ` Eilmsteiner Reinhard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-06  8:27 Eilmsteiner Reinhard
2003-02-06 10:43 ` Miguel Ramírez

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=1044621749.2569.24.camel@vie-nb-eilm2 \
    --to=r.eilmsteiner@paysafecard.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=mramirez@iua.upf.es \
    /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).