All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@cobaltnet.com>
To: Ralf Baechle <ralf@uni-koblenz.de>, linux@cthulhu.engr.sgi.com
Subject: Re: an ld problem? - possibly fixed..
Date: Thu, 29 Jul 1999 22:28:23 -0700	[thread overview]
Message-ID: <37A137F7.91B5AC4A@cobaltnet.com> (raw)
In-Reply-To: 19990729153427.E4730@uni-koblenz.de

Ralf Baechle wrote:

> just in case if you manage to fix this one please drop me a note.

I'm calling in for help on the solution now.

The problem occurs when a segment is found that is not a known name, libbfd
abort()s in mips_elf_relocate_section().  In the case of the egcs libstdc++
link the segments in question are : ".dtors" and ".gcc_except_table".  I assume
since .dtors is trouble, so will .ctors be.

If I add .dtors and .gcc_except_table to mips_elf_dynsym_sec_names[] in
${binutils_src_path}/bfd/elf32-mips.c and rebuild libbfd - ld no longer gets an
abort() when compiling the file in question.  I'm pretty sure this is NOT the
right solution.  There is also a table of sections in
${binutils_src_path}/bfd/syms.c.  What is the "right" solution, and what other
sections can exist that bfd doesn't know about?

Someone with a bit more experience inside libbfd - please help? :)

Tim

  parent reply	other threads:[~1999-07-30  5:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-29  2:27 an ld problem? Tim Hockin
1999-07-29 13:32 ` Ralf Baechle
     [not found] ` <19990729153427.E4730@uni-koblenz.de>
1999-07-30  5:28   ` Tim Hockin [this message]
1999-07-30 21:01     ` an ld problem? - possibly fixed Ralf Baechle

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=37A137F7.91B5AC4A@cobaltnet.com \
    --to=thockin@cobaltnet.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@uni-koblenz.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.