Maintaining libio (was: Re: [PATCH v2 1/2] libio: Multiple fixes for open_{w}memstram (BZ#18241 and BZ#20181))

Zack Weinberg zackw@panix.com
Thu Apr 20 15:44:00 GMT 2017


On Wed, Apr 19, 2017 at 5:17 AM, Florian Weimer <fweimer@redhat.com> wrote:
>
> I'm leaning towards a clean break: Stop installing <libio.h>.  Remove all
> symbols related to external vtable support (i.e., an ABI break, so that
> affected programs fail in a clean manner).  Do this now, and revisit it for
> glibc 2.27 if someone actually has an application that breaks due to this.

If you pull branch zack/no-libio-h you will get a libc that does not
install libio.h.  I didn't convert any of the currently-exposed _IO_
symbols into compat symbols, and I strongly suspect that I broke
support for the old (GLIBC_2.0) FILE object, but this should be good
enough to do archive rebuilds against.

For convenience, the changes are attached.  However, the branch is
built on top of a bunch of my other header cleanup work (_ISOMAC
testsuite and several bits/types/ conversions) so do not expect the
attached patch to apply to trunk.

zw
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Don-t-install-libio.h-or-_G_config.h.patch
Type: text/x-patch
Size: 82752 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20170420/1a5442c5/attachment.bin>


More information about the Libc-alpha mailing list