From: Andreas Schwab <schwab@linux-m68k.org>
To: Mack Wallace <mackbw@mapinternet.com>
Cc: binutils@sourceware.org
Subject: Re: Porting binutils to Amiga Unix
Date: Thu, 16 Feb 2017 09:47:00 -0000 [thread overview]
Message-ID: <8737fewjqk.fsf@linux-m68k.org> (raw)
In-Reply-To: <CFEDEDC3-E90C-4048-8141-A6A709B51861@mapinternet.com> (Mack Wallace's message of "Wed, 15 Feb 2017 21:11:45 -0500")
On Feb 15 2017, Mack Wallace <mackbw@mapinternet.com> wrote:
> My understanding has been that Amiga Unix uses the elf format for
> binaries. Looking at some binaries on the system, they begin with the
> magic number 7F. Wondering if the information I require could be gleaned
> by readelf, I downloaded the earliest copy of binutils that has that. I
> was able to compile readelf and its dependencies. Looking at some
> binaries, the âEntry Point Addressâ is something greater than 0x80000000
> (Iâve seen addresses of 0x800000f94, 0x80000117c, 0x8000027d0). This is a
> guess, but using m68kelf.sh in emulparameters as a starting point:
> TEXT_START_ADDR=0x80000000? For both paged and non-paged?
I think you should be able to use m68kelf.sh unchanged. It is also used
on m68k-linux, whose ELF support was based on SVr4 (with a few
peculiarities due to it's heritage which was based on the SunOS a.out
configuration).
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-02-16 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 2:11 Mack Wallace
2017-02-16 9:47 ` Andreas Schwab [this message]
2017-02-16 9:53 ` Andreas Schwab
2017-04-11 0:17 ` Mack Wallace
2017-04-11 7:55 ` Nick Clifton
2017-04-15 0:14 ` Maciej W. Rozycki
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=8737fewjqk.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
--cc=mackbw@mapinternet.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).