public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland AT frob.com>
To: Ian Lance Taylor <ian AT zembu.com>, binutils AT sourceware.cygnus.com
Subject: Re: strange compile problem
Date: Mon, 13 Sep 1999 12:53:00 -0000	[thread overview]
Message-ID: <199909131953.PAA31985@frob.com> (raw)
In-Reply-To: <199909131939.PAA31675@frob.com>

On the other hand, I see that bfd_stat is the only thing in bfd.h that
incurs the wrath of _FILE_OFFSET_BITS.  The only other related concern is
off_t vs `file_ptr', which has been circumvented already by just always
using `long int' for `file_ptr'.  As long as the internal conversions to
whatever type off_t is happen properly, I think that is fine.  I mean,
anyone on the list wanted to operate on a file >=2GB with BFD so far in life?

That being the case, I'd be most inclined to just punt bfd_stat from the
interface entirely.  If anyone needs to do that, it's much simpler to
provide a function that returns the fd (or FILE *) they can stat themselves.
Naturally that opens the door to people doing stupid things with that fd
behind BFD's back, but I am certainly willing to say "don't do that" (just
as you can't diddle much with an fd behind stdio's back and expect life not
to go to hell).

  reply	other threads:[~1999-09-13 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-13 11:50 John Barry
1999-09-13 11:58 ` Ian Lance Taylor
1999-09-13 12:39   ` Roland McGrath
1999-09-13 12:53     ` Roland McGrath [this message]
1999-09-13 13:13     ` John Barry
  -- strict thread matches above, loose matches on Subject: below --
1999-09-13 10:14 John Barry
1999-09-13 11:23 ` Ian Lance Taylor
1999-09-13  6:54 John Barry
1999-09-13  9:12 ` Ian Lance Taylor

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=199909131953.PAA31985@frob.com \
    --to=binutils@sourceware.org \
    /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).