Re: What to do about gnulib libio dependencies?

[Carlos O'Donell <carlos at redhat dot com>]

On 08/20/2018 09:24 AM, Szabolcs Nagy wrote:
> On 20/08/18 13:32, Florian Weimer wrote:
>> gnulib has a few modules which touch libio internals which aren't really exported:
>>
>> fbufmode
>> freadahead
>> freadptr
>> freadseek
>> fseterr
>>
>> This is a problem because it is not apparent from the glibc sources that the implementation details used by these functions are actually used externally.
>>
>> Should we just add these functions to glibc?  In some cases, the interactions with wide oriented streams could be problematic.
>>
> 
> i think it's better to define them in glibc.
> 
> gnulib already checks if these functions are provided by the libc:
> http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=2b14f42b44f04bce5631269ed46cd8be2413ccec

We should define them in glibc only if we have consensus on adding
the API and find it useful, and it doesn't overly restrict the
implementation.

We should certainly disabuse anyone of expecting libio internals
to be available to them. Why is gnulib expecting these internals
to be stable? Is it assuming that because of the libstdc++ support
from gcc 2.95 is going to keep the ABI stable?

-- 
Cheers,
Carlos.