[oe] uclibc and uclibc-locale support in gcc 4.3.1
Koen Kooi
k.kooi at student.utwente.nl
Wed Aug 20 22:33:44 UTC 2008
Khem Raj wrote:
> Hi Koen
>
> Thanks for looking at it. While I see that what you mention is
> logical. The construct I have worked ok on uclibc and eglibc angstrom
> builds. But I will change to what you suggested and do builds again.
I suspect we've hit a feature of bitbake again:
FOO = "bar"
FOO_xyz ?= "baz"
=> FOO is now baz
FOO_xyz = "bar"
FOO_xyz ?= "baz"
=> FOO is now bar
I still think this is a bug and depending on it would not be a good idea :)
regards,
Koen
>
> Thanks
>
> -Khem
>
> On Wed, Aug 20, 2008 at 2:08 AM, Koen Kooi<k.kooi at student.utwente.nl> wrote:
>> Khem Raj wrote:
>>> Hi
>>>
>>> I was trying to use gcc 4.3 for some uclibc stuff and found it broken.
>>> This patch fixes it.
>>>
>>> 1. Fix target gcc build. The earlier patch I did to fix SDK build was
>>> insufficient so I enhanced it.
>>>
>>> 2. uclibc Locale patches needed a facelift to be able to work with gcc 4.3
>>>
>>> 3. Fix uclibc 0.9.29 to get build using gcc 4.3
>>>
>>> 4. Disable libobjc for arm uclibc. If someone really needs some
>>> packages on uclibc which need objc support then you better fix gcc
>>> first :)
>>>
>>> I intend to apply it on .dev. comments are welcome
>>>
>>> I have tested it on arm uclibc and arm eglibc doing bitbake gcc
>> Your patch has
>>
>> +OBJC ?= ",objc"
>> +OBJC_linux-uclibcgnueabi ?= ""
>> +OBJC_avr ?= ""
>>
>> That probably needs to be:
>>
>> +OBJC_avr32 ?= ""
>> +OBJC_linux-uclibcgnueabi ?= ""
>> +OBJC ?= ",objc"
>>
>> Note the '32' in avr32 and the order of weak assignments.
>>
>> regards,
>>
>> Koen
>>
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel at lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
More information about the Openembedded-devel
mailing list