This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [RFC] Make _FILE_OFFSET_BITS=64 default.
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: Florian Weimer <fweimer at redhat dot com>, OndÅej BÃlka <neleai at seznam dot cz>, Paul Eggert <eggert at cs dot ucla dot edu>, Denis Obrezkov <reprofy at etersoft dot ru>, GNU C Library <libc-alpha at sourceware dot org>
- Date: Thu, 13 Mar 2014 15:26:22 -0700 (PDT)
- Subject: Re: [RFC] Make _FILE_OFFSET_BITS=64 default.
- 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> <5316FF9F dot 1060301 at redhat dot com> <20140311181727 dot A269674472 at topped-with-meat dot com> <CA+=Sn1mgSy-+68-D0WARm1ySTzkWDrf+kCuVqZ_CbbJHUbFXRw at mail dot gmail dot com>
> It can be an ABI change to other people's sources as if they used
> off_t, now they have a different type.
Yes, that is part of what an API change means: recompiling might produce a
different ABI. That is one of the reasons why API changes require careful
consideration. When we talk about an ABI change on this list, we are
talking about the ABIs of libraries our package installs.