From: Grant Grundler <grundler@dsl2.external.hp.com>
To: HEISERER DANIEL <Daniel.Heiserer@bmw.de>
Cc: parisc-linux@lists.parisc-linux.org, debian-hppa@lists.debian.org
Subject: Re: [parisc-linux] octave2.1_2.1.35-6_hppa
Date: Tue, 29 Jan 2002 11:59:16 -0700 [thread overview]
Message-ID: <20020129185916.2AE58482A@dsl2.external.hp.com> (raw)
In-Reply-To: Message from HEISERER DANIEL <Daniel.Heiserer@bmw.de> of "Tue, 29 Jan 2002 11:18:01 +0100." <3C5676D9.E4B26D93@bmw.de>
HEISERER DANIEL wrote:
> I am also a little be astonished about the different object files
> existing on PA-Risc. There are
> /usr/local/bin/perl: PA-RISC1.1 shared executable dynamically linked
> -not stripped
> as well as "PA-RISC2" executables.
Also note that "PA-RISC1.1" on HPUX implies the binary is a SOM binary
(not ELF). parisc-linux uses ELF-32 format by default. This was "invented"
for the parisc-linux port.
parisc-linux kernel has support for SOM binaries but it's really only
for HPUX application compatibility.
> Honestly I have no idea what the difference between ELF-64 and PA-RISC-2
> is. Are both 64 bit?
Since PARISC2.0 introduced 64-bit capability, many people equate the two.
(that's not a shooting offense. ;^) While Matthew is correct, in practice
most folks build PA1.1 binaries when they want a 32-bit application.
I was building 32-bit PA-RISC2.0 linux kernels. But the toolchain was using
"reloc" (type 74, iirc) that the kernel dynamic linker couldn't grok.
So I couldn't load any kernel driver modules. I decided it wasn't worth
pursueing and now build PA 1.1 kernels.
grant
next prev parent reply other threads:[~2002-01-29 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-29 10:18 [parisc-linux] octave2.1_2.1.35-6_hppa HEISERER DANIEL
2002-01-29 15:19 ` [parisc-linux] octave2.1_2.1.35-6_hppa Matthew Wilcox
2002-01-29 16:12 ` Christopher C. Chimelis
2002-01-29 18:59 ` Grant Grundler [this message]
2002-01-29 19:58 ` [parisc-linux] octave2.1_2.1.35-6_hppa 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=20020129185916.2AE58482A@dsl2.external.hp.com \
--to=grundler@dsl2.external.hp.com \
--cc=Daniel.Heiserer@bmw.de \
--cc=debian-hppa@lists.debian.org \
--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