Op 14 apr. 2013, om 13:57 heeft Paul Eggleton <paul.eggle...@linux.intel.com> 
het volgende geschreven:

> On Saturday 13 April 2013 20:35:11 Henning Heinold wrote:
>> From: Henning Heinold <hein...@inf.fu-berlin.de>
>> 
>> * fixes
>> In file included from
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/libfdt.h:55:0, from
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/work/x86_64-linux/qem
>> u-native/1.4.0-r0/qemu-1.4.0/hw/arm/../../device_tree.c:28:
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:58:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:59:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:60:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:61:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:62:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:63:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:64:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:67:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:70:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:73:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:77:2: error: unknown type name 'fdt64_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:78:2: error: unknown type name 'fdt64_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:82:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:87:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:88:2: error: unknown type name 'fdt32_t'
>> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-linux
>> /usr/include/fdt.h:89:2: error: unknown type name 'fdt32_t'
> 
> I still can't reproduce this issue on F18 with dtc-native built. What 
> triggers 
> it exactly?

Updating dtc-native to current git will trigger it. I have a patch to do that, 
but haven't sent it yet due to the qemu breakage above.
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to