From: dhazeghi@pacbell.net
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] [Semi OT] SOM Linker
Date: Tue, 14 Nov 2000 18:17:39 -0800 [thread overview]
Message-ID: <3A11F243.4A3625C@pacbell.net> (raw)
In-Reply-To: 3A1037F0.826C9D8C@linuxcare.com
Alex deVries wrote:
> dhazeghi@pacbell.net wrote:
> > However I would like to know what work if any has been done on the SOM
> > linker which HP released to the public last November(?). It seems that
> > as of right now, it has not been touched since February 14, and the FSF
> > binutils snapshots still do not have any SOM support for ld. Has there
> > been any movement in merging this in, or is anybody working on this?
>
> The initial plan was to do our 32-bit userspace with SOM, worrying about
> ELF32 much later in the game. But ELF32 development happened a lot
> quicker than expected, and so nobody's really done much on the SOM
> linker.
That's what it looked like...
>
>
> I suspect it'd be very hard to use the SOM linker code to incorporate it
> into binutils, but I could be wrong.
>
> What are you actually trying to do?
I would like to be able to set up a cross compilation environment for hpux and
32 bit PA-RISC. However without a functional cross linker, this is impossible
to do, and as binutils has not got one yet, I thought perhaps the one that HP
open-sourced might be some use. It would seem logical that with the sources
available, it shouldn't be too difficult to fix the broken bits and get a SOM
linker working in binutils, but that doesn't seem to have happened yet. Oh
well, thanks for the info...
Dara Hazeghi
next prev parent reply other threads:[~2000-11-15 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 5:34 [parisc-linux] [Semi OT] SOM Linker dhazeghi
2000-11-13 18:50 ` Alex deVries
2000-11-15 2:17 ` dhazeghi [this message]
2000-11-15 3:00 ` John David Anglin
2000-11-15 5:23 ` dhazeghi
2000-11-15 16:23 ` 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=3A11F243.4A3625C@pacbell.net \
--to=dhazeghi@pacbell.net \
--cc=parisc-linux@thepuffingroup.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