Patchwork qemu: define fdt_t types in libfdt_env.h from qemu

login
register
mail settings
Submitter Henning Heinold
Date April 13, 2013, 6:35 p.m.
Message ID <1365878111-23737-1-git-send-email-heinold@inf.fu-berlin.de>
Download mbox | patch
Permalink /patch/48131/
State Accepted
Commit ea6e7975964c75e0c8224205e0c1fd04ba37ed4a
Headers show

Comments

Henning Heinold - April 13, 2013, 6:35 p.m.
From: Henning Heinold <heinold@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/qemu-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'

Signed-off-by: Henning Heinold <heinold@inf.fu-berlin.de>
---
 meta/recipes-devtools/qemu/files/fdt_header.patch |   39 +++++++++++++++++++++
 meta/recipes-devtools/qemu/qemu_1.4.0.bb          |    4 ++-
 2 files changed, 42 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-devtools/qemu/files/fdt_header.patch
Koen Kooi - April 13, 2013, 7:01 p.m.
Op 13 apr. 2013, om 20:35 heeft Henning Heinold <heinold@inf.fu-berlin.de> het volgende geschreven:

> From: Henning Heinold <heinold@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/qemu-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'
> 
> Signed-off-by: Henning Heinold <heinold@inf.fu-berlin.de>



Tested-by: Koen Kooi <koen@dominion.thruhere.net>
Paul Eggleton - April 14, 2013, 11:57 a.m.
On Saturday 13 April 2013 20:35:11 Henning Heinold wrote:
> From: Henning Heinold <heinold@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?

Cheers,
Paul
Koen Kooi - April 14, 2013, 1:50 p.m.
Op 14 apr. 2013, om 13:57 heeft Paul Eggleton <paul.eggleton@linux.intel.com> het volgende geschreven:

> On Saturday 13 April 2013 20:35:11 Henning Heinold wrote:
>> From: Henning Heinold <heinold@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.
ml@communistcode.co.uk - April 14, 2013, 3:10 p.m.
On 04/14/13 12:57, Paul Eggleton wrote:
> On Saturday 13 April 2013 20:35:11 Henning Heinold wrote:
>> From: Henning Heinold <heinold@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?
>
> 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.
Paul Eggleton - April 14, 2013, 3:25 p.m.
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 <heinold@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
Henning Heinold - April 14, 2013, 5:49 p.m.
On Sun, Apr 14, 2013 at 04:25:30PM +0100, Paul Eggleton wrote:
> 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

Hi Paul,

okay now I see the problem, why you do not see the problem.

meta-beagleboard overrides dtc/libdtc for the latest git version.

dtc changed the following 3 headers

libenv_fdt.h
fdt.h
libfdt.h

to typedef fdt16_t, fdt32_t and fdt64_t. The typedef happens in libenv_fdt.h.
Now qemu ships its own version of libenv_fdt.h, which does not have the typedefs.

The right solution would have been letting meta-beagleboard append the patch for qemu.

On the other hand the typedefs now in qemu's version of libenv_fdt.h does not
hurt something and Richard already applied it.

Bye Henning

Patch

diff --git a/meta/recipes-devtools/qemu/files/fdt_header.patch b/meta/recipes-devtools/qemu/files/fdt_header.patch
new file mode 100644
index 0000000..dccfe53
--- /dev/null
+++ b/meta/recipes-devtools/qemu/files/fdt_header.patch
@@ -0,0 +1,39 @@ 
+Upstream-Status: Pending 
+
+qemu: define fdt types in libfdt_env.h from qemu
+    
+    * 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/qemu-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'
+
+Index: qemu-1.4.0/include/libfdt_env.h
+===================================================================
+--- qemu-1.4.0.orig/include/libfdt_env.h	2013-02-15 23:05:35.000000000 +0000
++++ qemu-1.4.0/include/libfdt_env.h	2013-04-13 14:17:27.918885225 +0000
+@@ -21,6 +21,10 @@
+ 
+ #include "qemu/bswap.h"
+ 
++typedef uint16_t fdt16_t;
++typedef uint32_t fdt32_t;
++typedef uint64_t fdt64_t;
++
+ #ifdef HOST_WORDS_BIGENDIAN
+ #define fdt32_to_cpu(x)  (x)
+ #define cpu_to_fdt32(x)  (x)
diff --git a/meta/recipes-devtools/qemu/qemu_1.4.0.bb b/meta/recipes-devtools/qemu/qemu_1.4.0.bb
index e705a03..d968782 100644
--- a/meta/recipes-devtools/qemu/qemu_1.4.0.bb
+++ b/meta/recipes-devtools/qemu/qemu_1.4.0.bb
@@ -3,7 +3,9 @@  require qemu.inc
 LIC_FILES_CHKSUM = "file://COPYING;md5=441c28d2cf86e15a37fa47e15a72fbac \
                     file://COPYING.LIB;endline=24;md5=c04def7ae38850e7d3ef548588159913"
 
-SRC_URI += "file://3f08ffb4a4741d147634761dc053ed386243a0de.patch"
+SRC_URI += "file://3f08ffb4a4741d147634761dc053ed386243a0de.patch \
+            file://fdt_header.patch \
+           "
 
 SRC_URI_prepend = "http://wiki.qemu.org/download/qemu-${PV}.tar.bz2"
 SRC_URI[md5sum] = "78f13b774814b6b7ebcaf4f9b9204318"