This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PING][PATCH] Warn about using _ino_t without -D_FILE_OFFSET_BITS=64.
- From: Paul Eggert <eggert at cs dot ucla dot edu>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Fri, 21 Mar 2014 16:04:33 -0700
- Subject: Re: [PING][PATCH] Warn about using _ino_t without -D_FILE_OFFSET_BITS=64.
- Authentication-results: sourceware.org; auth=none
- References: <1393521776-1102-1-git-send-email-reprofy at etersoft dot ru> <530F79C1 dot 2040508 at cs dot ucla dot edu> <20140305091331 dot GA6031 at domone dot podge> <5239512 dot EEmGNsN1rx at vapier> <20140317174452 dot GA10644 at domone> <20140321112938 dot GA15232 at domone dot podge> <Pine dot LNX dot 4 dot 64 dot 1403211228420 dot 1911 at digraph dot polyomino dot org dot uk> <532CADFB dot 6000409 at cs dot ucla dot edu> <20140321220412 dot A5CA3744A7 at topped-with-meat dot com>
Roland McGrath wrote:
the first question is if perhaps we shouldn't just deprecate fts entirely and not support a new one in libc.
That would be easier, yes.
we should see what the current versions of 4.4BSD-derived
systems are doing for fts.
It's in the latest versions of FreeBSD (10.0), NetBSD (6.1.3), and
OpenBSD (5.4). FreeBSD has some minor extensions that the others
(including glibc) lack.
You didn't list elfutils ({-libelf,{-devel}}).
That package is free of the problem; my script gave its include files a
clean bill of health. In fact I'm puzzled why you mentioned it, as its
include files don't use off_t, off64_t, or any of the other types (with
or without "64") affected by the problem.
Here's a list of elfutils-devel's include files on Fedora 20:
dwarf.h
elfutils/elf-knowledge.h
elfutils/libasm.h
elfutils/libdwfl.h
elfutils/libdw.h
elfutils/libebl.h
elfutils/version.h