All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
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:25:30 +0100	[thread overview]
Message-ID: <6800403.eSx3nnyBtB@helios> (raw)
In-Reply-To: <516AC6D3.2030102@communistcode.co.uk>

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

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2013-04-14 15:43 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
2013-04-14 15:25     ` Paul Eggleton [this message]
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=6800403.eSx3nnyBtB@helios \
    --to=paul.eggleton@linux.intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.