public inbox for bfd@sourceware.org
 help / color / mirror / Atom feed
From: Krister Walfridsson <cato@df.lth.se>
To: bfd@cygnus.com
Subject: a.out questions
Date: Fri, 01 May 1998 13:02:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.96.980501220036.256A-100000@bartlet.df.lth.se> (raw)

I'm in the process of porting binutils to NetBSD's a.out shared library
format, and I have a couple of questions...

In our exec header, there is a flag that tells if the code in the file
is position independent. Should I add this to the flags in BFD, or is 
this attribute obscure enough to keep only as private data in the a.out
backend?

Since I thought that our a.out format was close to sunos, I have based
my version on sunos.c. There are however two differences that are big 
enough to cause problems;

- The nlist pointed to by the dynamic_link structure isn't a nlist in
  NetBSD (it's a nlist with on word appended.) This does unfortunatly
  break (at least) aout_link_add_symbols() in aoutx.h

- Weak symbols are handled by setting a flag in the n_other field (instead
  of handling it in n_type that binutils does). This breaks the conversion 
  functions in aoutx.h.

Are there any hooks I have missed that can solve my problems? As far I can 
see, the hooks are present on a too high level, so I end up duplicating 
nearly the whole aoutx.h. Or should I try to add new hooks?


By the way, are this mailing list the correct place to discuss changes to
ld, or are there a ld list somewhere?

   /Krister



             reply	other threads:[~1998-05-01 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-01 13:02 Krister Walfridsson [this message]
1998-05-01 13:16 ` Ian Lance Taylor

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=Pine.LNX.3.96.980501220036.256A-100000@bartlet.df.lth.se \
    --to=cato@df.lth.se \
    --cc=bfd@cygnus.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).