public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: Mattias Jansson <mattias@realityrift.com>
Cc: binutils@sources.redhat.com
Subject: Re: ld problems
Date: Mon, 13 Sep 2004 00:24:00 -0000	[thread overview]
Message-ID: <20040913002403.GB7854@bubble.modra.org> (raw)
In-Reply-To: <1094913015.8100.9.camel@ithala>

On Sat, Sep 11, 2004 at 04:30:15PM +0200, Mattias Jansson wrote:
> typeinfo for neo::scene::Object: discarded in section
> `.gnu.linkonce.r._ZTIN3neo5scene6ObjectE' from
> build/scons/debug/engine/libneoengine-debug.a(object.o)
> collect2: ld returned 1 exit status

You didn't say the target or the version of ld where you found this
problem which makes it harder to give an answer because we have to
guess these details.  I'll guess x86 and 2.15 or one of HJ's 2.15.x
releases.  You also didn't give the version of gcc.

I expect that if someone analysed this problem properly, you would find
a reference to the typeinfo symbol in a normal section such as .data or
.rodata.  What's more, I'll make a wild guess that the reference is made
inside some function that requires linkonce semantics itself, and most
of the function is defined in sections named .gnu.linkonce.*.  If that's
the case then this is really a g++ code generation error.

However, ld ought to be forgiving in this situation, so this error is
also a ld bug.  I fixed the ld bug on 2004-08-13 for CVS head, so you
might like to try compiling current CVS binutils.  You'll get a warning
instead of an error.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

  reply	other threads:[~2004-09-13  0:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-11 14:43 Mattias Jansson
2004-09-13  0:24 ` Alan Modra [this message]
2004-09-13  9:26   ` Mattias Jansson
  -- strict thread matches above, loose matches on Subject: below --
2003-08-07 12:34 Hylla, Kai
2003-08-07 13:15 ` Alan Modra
2003-08-07 13:36 ` Nick Clifton

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=20040913002403.GB7854@bubble.modra.org \
    --to=amodra@bigpond.net.au \
    --cc=binutils@sources.redhat.com \
    --cc=mattias@realityrift.com \
    /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).