From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qemu: define fdt_t types in libfdt_env.h from qemu
Date: Sun, 14 Apr 2013 16:10:11 +0100 [thread overview]
Message-ID: <516AC6D3.2030102@communistcode.co.uk> (raw)
In-Reply-To: <2868224.qKIdN0gebe@helios>
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.
next prev parent reply other threads:[~2013-04-14 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 18:35 [PATCH] qemu: define fdt_t types in libfdt_env.h from qemu Henning Heinold
2013-04-13 19:01 ` Koen Kooi
2013-04-14 11:57 ` Paul Eggleton
2013-04-14 13:50 ` Koen Kooi
2013-04-14 15:10 ` Jack Mitchell [this message]
2013-04-14 15:25 ` Paul Eggleton
2013-04-14 17:49 ` Henning Heinold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=516AC6D3.2030102@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox