From: Jeffrey A Law <law@cygnus.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Heiko Nardmann <h.nardmann@secunet.de>,
BinUtils <binutils@sourceware.cygnus.com>
Subject: Re: problem compiling binutils 2.10
Date: Wed, 28 Jun 2000 09:03:00 -0000 [thread overview]
Message-ID: <3441.962207530@upchuck> (raw)
In-Reply-To: <Pine.LNX.4.21.0006281741090.27908-100000@front.linuxcare.com.au>
In message < Pine.LNX.4.21.0006281741090.27908-100000@front.linuxcare.com.au >y
ou write:
> On Wed, 28 Jun 2000, Heiko Nardmann wrote:
>
> > Now I am not sure which header files are needed.
> > As far as I understand it this thing is only targeted for native HPPA
> > systems, isn't it?
>
> Yes. One way to find out which header files are needed is to compile with
> -DHOST_HPPAHPUX added to CFLAGS and see what breaks. I haven't tried this
> sort of this myself, so you'll probably need to do a little work.
It can be done (I've done it in the past to build cross assemblers and such
for SOM tools.
> > Why are some format definitions part of binutils and some not?
>
> I don't know the history behind this, sorry.
Because nobody's felt it important enough to rewrite the necessary header
files so that they could be included in the binutils distribution without
violating the HP copyrights on their headerfiles.
Not a lot of folks care about cross-assemblers and such for SOM.
jeff
prev parent reply other threads:[~2000-06-28 9:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-27 22:30 Heiko Nardmann
2000-06-27 22:43 ` Alan Modra
2000-06-27 23:07 ` Heiko Nardmann
2000-06-27 23:28 ` Alan Modra
2000-06-28 0:37 ` Heiko Nardmann
2000-06-28 0:50 ` Alan Modra
2000-06-28 1:20 ` Heiko Nardmann
2000-06-28 2:12 ` Alan Modra
2000-06-28 7:03 ` Joel Sherrill
2000-06-28 8:30 ` Jeffrey A Law
2000-06-28 9:03 ` Jeffrey A Law [this message]
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=3441.962207530@upchuck \
--to=law@cygnus.com \
--cc=alan@linuxcare.com.au \
--cc=binutils@sourceware.cygnus.com \
--cc=h.nardmann@secunet.de \
/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).