On Tue, Mar 22, 2011 at 7:46 PM, Rob Landley wrote:
> On 03/22/2011 06:01 PM, Khem Raj wrote:
>> On (22/03/11 16:42), Rob Landley wrote:
>>> On 03/20/2011 01:02 AM, Khem Raj wrote:
>>>> On 3/19/2011 10:17 PM, Rob Landley wrote:
>>>>> I'm running my Linux From Scratch 6.7 build under a uClibc root
>>>>> filesystem, and building m4 1.14.4 has this error:
>>>>>
>>>>> gcc -std=gnu99  -I.     -g -O2 -MT execute.o -MD -MP -MF
>>>>> .deps/execute.Tpo -c -o execute.o execute.c
>>>>> In file included from execute.c:47:
>>>>> ./spawn.h:112: error: field '_sp' has incomplete type
>>>>> distcc[23848] ERROR: compile execute.c on localhost failed
>>>>> make[3]: *** [execute.o] Error 1
>>>>> make[3]: Leaving directory `/home/m4/lib'
>>>>
>>>> Apply the fixes e.g.
>>>> http://git.openembedded.org/cgit.cgi/openembedded/tree/recipes/bison/bison-2.4.3/uclibc-sched_param-def.patch
>>>
>>> Translation: uClibc is permanently broken, we have no choice but to
>>> start crapping #ifdef uClibc all over other packages to get them to work
>>> with special cases just for us, when in the previous version we could
>>> actually fix uClibc.
>>>
>>
>> heh so you mean whatever glibc does is right ?
>
> If the package is expecting something specifically because we're
> exporting _GLIBC_?  Yes.

which is a compatibility hack intended to go away.  if you want to
actually *fix* things, start building packages without uClibc
exporting those compat defines.
-mike
_______________________________________________
uClibc mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/uclibc

Reply via email to