public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Sébastien ZINSIUS" <sebastien.zinsius@ersa-france.com>
To: <gcc-help@gcc.gnu.org>
Subject: Undefined reference : very strange linking problem...
Date: Mon, 06 Sep 2004 10:06:00 -0000	[thread overview]
Message-ID: <1E58066E82C558488E7F316C6D6B34DF01081E@srv1.ersa-france.com> (raw)

Hello all!

I have a very strange linking problem... I'm working on a quite complex project written in C++ and compiled/linked with g++.

This project includes a lot of libraries. I recently added 3 new classes (one base class and two classes inheriting the first) to the A library. This library is used by library B. Finally, application is linked with both libraries.

Everything worked sofar but this times I got strange undefined references when linking (only with the two classes inheriting the third, but I don't know if it is related). I checked header files (#ifdef, class names, method names...), libraries linking order (but that always worked...) and everything is OK. Compilation also succeeds and when I use classes directly (not through libraries) or when I use them through library A it works!!

That's why I suspect something with library B. It seems that there is an overflow somewhere (to many symbols defined in library)... Is this possible? Is there any solution? Any other idea?

Thanks in anticipation!

Sébastien

             reply	other threads:[~2004-09-06 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-06 10:06 Sébastien ZINSIUS [this message]
     [not found] ` <1E58066E82C558488E7F316C6D6B34DF01081E@srv1.ersa-france.co m>
2004-09-07 12:36   ` Eljay Love-Jensen

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=1E58066E82C558488E7F316C6D6B34DF01081E@srv1.ersa-france.com \
    --to=sebastien.zinsius@ersa-france.com \
    --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).