From: dhazeghi@pacbell.net
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] [Semi OT] SOM Linker
Date: Tue, 14 Nov 2000 21:23:41 -0800 [thread overview]
Message-ID: <3A121DDD.992ECBC8@pacbell.net> (raw)
In-Reply-To: 200011150300.WAA20789@hiauly1.hia.nrc.ca
John David Anglin wrote:
> > 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...
>
> You should be able to build cross compilation tools under hpux for hppa-linux.
> First you should install native versions of binutils and gcc under hpux (this
> assumes that you have the hpux C compiler and linker). The release version of
> gcc (2.95.2) would be a good choice. The standard hpux linker works fine with
> gcc/gas for C compilations. Then follow the directions at www.parisc-linux.org
> for building the cross compilation tools and linux.
This is not precisely what I mean. What I should have said is that I want to create
a cross compiler --host=i686-linux --target=hppa-hpux. I asked this list, because
you folks did some work on the SOM linker, which is at the moment the missing piece
for a cross toolchain which targets hpux.
Thanks,
Dara
P.S. On a different note, is the recipe fully up to date? I tried following it a
few weeks ago, but glibc did not complete building successfully.
next prev parent reply other threads:[~2000-11-15 5:32 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
2000-11-15 3:00 ` John David Anglin
2000-11-15 5:23 ` dhazeghi [this message]
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=3A121DDD.992ECBC8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.