public inbox for
 help / color / mirror / Atom feed
From: Mark Klein <>
Subject: Fwd: Re: BFD for the HP3000
Date: Tue, 30 Mar 1999 14:15:00 -0000	[thread overview]
Message-ID: <> (raw)

>At 01:44 PM 3/30/99 -0800, Ian Lance Taylor wrote:
>>Boy, this sounds like it could get ugly.  What sort of calls do you
>>need to generate?
>There is a binary filecode that needs to get added to the filelabel. The
>fopen() call should be replaced with something called HPFopen(). Alternately,
>I could build an fopen() wrapper that in turn calls HPFopen(), but I still
>need to be able to identify which attribute (relocatable, archive or program)
>needs to be applied to the open through an additional parameter.
>>I don't think that will be right.  Think about using HP3000 as the
>>host for a cross compiler to some other system.
>Good point. My other choice is to build a new BFD for each type, but that
>get ugly too, since bfd_object can apply to both relocatable objects as
well as
>program objects. At least bfd_archive is separate.

Mark Klein                                 DIS International, Ltd.                         415-892-8400
PGP Public Key Available			

                 reply	other threads:[~1999-03-30 14:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).