public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm@polyomino.org.uk>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Christopher Faylor <cgf@redhat.com>, overseers@sources.redhat.com
Subject: Re: last days of htdig
Date: Sat, 27 Sep 2003 16:24:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0309271717410.28253@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <Pine.BSF.4.44.0309271208310.6156-100000@dair.pair.com>

On Sat, 27 Sep 2003, Hans-Peter Nilsson wrote:

> I doubt it does, but that's just me.  Maybe it eventually boils
> down to a libstdc++ issue.  Though htdig uses a nice mixture of
> stdio and streams IIRC.

libstdc++ is the sort of external library there are likely to be problems
with - we don't build multiple versions with/without _FILE_OFFSET_BITS=64
(and there'd be the problem of selecting the correct one at link-time,
even if g++ were to force _FILE_OFFSET_BITS=64 like it forces _GNU_SOURCE
for other reasons).  zlib is another library that can often cause problems
in this way.

Libraries where you're expected to use `foolib-config --cflags` (or in
more modern versions `pkg-config --cflags library-name`) by contrast could
avoid that problem - if their authors had taken the initiative to force
large-files mode for that library and its users.

There's a lot to be said for NetBSD's choice of making off_t 64 bits
unconditionally regardless of whether on a 32-bit or 64-bit system.

-- 
Joseph S. Myers
jsm@polyomino.org.uk

  reply	other threads:[~2003-09-27 16:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-27  7:18 Hans-Peter Nilsson
2003-09-27 15:21 ` Christopher Faylor
2003-09-27 15:54   ` Hans-Peter Nilsson
2003-09-27 16:03     ` Christopher Faylor
2003-09-27 16:06     ` Joseph S. Myers
2003-09-27 16:16       ` Hans-Peter Nilsson
2003-09-27 16:24         ` Joseph S. Myers [this message]
2003-09-27 19:45   ` Matthew Galgoci
2003-09-27 21:50     ` Christopher Faylor
2003-09-27 22:05       ` Ulrich Drepper
2003-09-27 22:21         ` Christopher Faylor
2003-09-27 22:29           ` Ulrich Drepper
2003-09-27 22:36           ` Hans-Peter Nilsson
2003-09-28 22:40 ` Hans-Peter Nilsson
2003-09-29 22:04   ` Gerald Pfeifer

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=Pine.LNX.4.58.0309271717410.28253@kern.srcf.societies.cam.ac.uk \
    --to=jsm@polyomino.org.uk \
    --cc=cgf@redhat.com \
    --cc=hp@bitrange.com \
    --cc=overseers@sources.redhat.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).