This is the mail archive of the bfd@sourceware.cygnus.com mailing list for the bfd project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
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