Test build failed due to UCLIBC_INTERNAL header rework
Carmelo AMOROSO
carmelo.amoroso at st.com
Wed Jun 11 16:02:53 UTC 2008
Denys Vlasenko wrote:
> On Wednesday 11 June 2008 09:29, Carmelo AMOROSO wrote:
>
>> Denys Vlasenko wrote:
>>
>>> On Tuesday 10 June 2008 16:27, Carmelo AMOROSO wrote:
>>>
>>>
>>>> Hello,
>>>> recent change on libc_hidden_proto brakes test and utils build.
>>>>
>>>>
>>> Please send your .config
>>>
>>> I never did "make utils" before, possibly because I usually do static builds...
>>> --
>>> vda
>>>
>>>
>> but you should build test at least.. hopefully.
>>
>
> Yes, I do this. It progresses farther than your failure
> point (TEST_LINK crypt/ md5c-test), and eventually fails
> in TEST_EXEC inet/ tst-network_glibc:
>
>
strange.. it should fail when referring to __GI_strcmp...
> ...
>
>
>> So now that string.h has been changed again, how is UCLIBC_INTERNALS
>> maco used ?
>>
>
> It is used whenever you want to have something in a header file to be there
> only when you build the library, but want to physically remove it
> in installed headers (not just logically by #ifdef'ing it out).
>
ok
> The implementation was stolen from linux kernel's "header sanitization step".
>
> libc_hidden_proto was projected to be a big user of it, but then Bernd
> came up with even more maintainable way to deal with that one.
>
yes I've seen
> Now UCLIBC_INTERNALS is used for printf.h (there existed an ad-hoc solution
> which was doing basically the same, but only for this file) and other places.
> --
> vda
>
Thanks for explanation.
Carmelo
More information about the uClibc
mailing list