On Sunday 14 April 2013 16:10:11 Jack Mitchell wrote: > On 04/14/13 12:57, Paul Eggleton wrote: > > 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-lin > >> ux > >> /usr/include/libfdt.h:55:0, from > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/work/x86_64-linux/q > >> em > >> 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-lin > >> ux > >> /usr/include/fdt.h:58:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:59:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:60:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:61:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:62:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:63:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:64:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:67:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:70:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:73:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:77:2: error: unknown type name 'fdt64_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:78:2: error: unknown type name 'fdt64_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:82:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:87:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /usr/include/fdt.h:88:2: error: unknown type name 'fdt32_t' > >> /home/oe/setup-scripts/build/tmp-angstrom_next-uclibc/sysroots/x86_64-lin > >> ux > >> /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? > > > > Cheers, > > Paul > > I can confirm that I am also blocked by this error at the moment. I > haven't had time to try the patch yet but I see no reason why it > wouldn't work. Will feedback on Monday if deliberation is still on going.
FWIW, the reason I asked is not because I think the fix is wrong, but to try to determine - given that I couldn't reproduce the issue and the lack of information about what might cause it given in the patch header - whether this fix ought to be merged into the dylan branch immediately or not. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
