From: "H. Peter Anvin" <hpa@zytor.com>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: klibc@zytor.com, parisc-linux@lists.parisc-linux.org
Subject: Re: [klibc] [parisc-linux] klibc parisc64
Date: Mon, 24 Jul 2006 16:17:13 -0700 [thread overview]
Message-ID: <44C554F9.9020402@zytor.com> (raw)
In-Reply-To: <200607242311.k6ONBMY0004933@hiauly1.hia.nrc.ca>
John David Anglin wrote:
>> H. Peter Anvin wrote:
>>> (k)libc.so isn't a shared library in the ELF sense. It's an executable.
>>>
>> ... specifically, as far as ELF (and the kernel) is concerned, it's the
>> ELF interpreter; it's linked at a fixed address and the application
>> invokes it with usual static jumps.
>
> "Usual static jumps"? There's nothing usual about static jumps on
> the PA ;( However, it should be possible to jump to a static address
> with the right setup.
>
> The 64-bit linker hasn't really been ported to linux. The interpreter
> section is hardcoded to ELF_DYNAMIC_INTERPRETER:
>
> #define ELF_DYNAMIC_INTERPRETER "/usr/lib/pa20_64/dld.sl"
>
> /* Set the contents of the .interp section to the interpreter. */
> if (info->executable)
> {
> s = bfd_get_section_by_name (dynobj, ".interp");
> BFD_ASSERT (s != NULL);
> s->size = sizeof ELF_DYNAMIC_INTERPRETER;
> s->contents = (unsigned char *) ELF_DYNAMIC_INTERPRETER;
> }
>
OK, well then it's probably pointless to try to get 64-bit klibc up and
running on it at this point. That's fine, though; we can just use 32-bit.
-hpa
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2006-07-24 23:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 18:27 [parisc-linux] klibc parisc64 Kyle McMartin
2006-07-24 19:01 ` John David Anglin
2006-07-24 19:28 ` Kyle McMartin
2006-07-24 19:50 ` John David Anglin
2006-07-24 19:35 ` John David Anglin
2006-07-24 22:41 ` [klibc] " H. Peter Anvin
2006-07-24 22:55 ` H. Peter Anvin
2006-07-24 23:11 ` John David Anglin
2006-07-24 23:17 ` H. Peter Anvin [this message]
2006-07-25 1:46 ` Kyle McMartin
2006-07-25 3:09 ` John David Anglin
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=44C554F9.9020402@zytor.com \
--to=hpa@zytor.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=klibc@zytor.com \
--cc=parisc-linux@lists.parisc-linux.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