From: Mark Klein <mklein@dis.com>
To: bfd@cygnus.com
Subject: Fwd: BFD for the HP3000
Date: Tue, 30 Mar 1999 14:14:00 -0000 [thread overview]
Message-ID: <4.1.19990330141337.046ce2c0@garfield.dis.com> (raw)
I'm forwarding this to bfd@cygnus.com to get it into the archives.
In a conversation with Ian Lance Taylor, I wrote:
>I have a need to add certain file attributes to various types of files at
>create time and don't see any "supported" way to do that through BFD.
>For example, relocatable object files contain an attribute that identify
>them as such to the system; archive libraries contain another; and runnable
>programs a third. This is over and above the information contained in the
>SOM header (and really is an attribute kept in the file system directory,
>not in the file itself). However, this must be attached at file create time.
>
>I don't see any means within bfd_openw() or bfd_open_file() that allows me
>to call open() or fopen() and specify machine dependent items. Is there a
>supported way to do so? If not, is it worthwhile to change the machine
>independent code to do something like:
>
>#define FOPEN(filename, flags) (PTR) fopen((filename),(flags))
>
>bfd_open_file (abfd) {
>...
>abfd->iostream = FOPEN (abfd->filename, FOPEN_RB);
>...
>}
>
>and allow the FOPEN define to be overridden in a machine dependent way
>for those that require it?
>
>Is this a subject for the egcs list, or is there another list for binutils
>and other infrastructure?
>
>Regards,
>
>
>M.
>
>
--
Mark Klein DIS International, Ltd.
http://www.dis.com 415-892-8400
PGP Public Key Available
reply other threads:[~1999-03-30 14:14 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:
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=4.1.19990330141337.046ce2c0@garfield.dis.com \
--to=mklein@dis.com \
--cc=bfd@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).