Poky Project Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@openedhand.com>
To: Wolfgang Denk <wd@denx.de>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/5] Fedora 14 Patches
Date: Thu, 09 Dec 2010 18:46:37 +0000	[thread overview]
Message-ID: <1291920397.6078.39.camel@scimitar> (raw)
In-Reply-To: <20101209160605.0A664D1CAD4@gemini.denx.de>

On Thu, 2010-12-09 at 17:06 +0100, Wolfgang Denk wrote:
> Dear Joshua,
> 
> In message <1291897825.6078.11.camel@scimitar> you wrote:
> > > 
> > > I'm trying to build Poky for some PowerPC and ARM architectures
> > > (PPC6xx, PPC4xx, ARM Kirkwood, etc.), and see a number of build
> > > issues.  I started reportung these:
> > > http://bugzilla.pokylinux.org/show_bug.cgi?id=572
> > > http://bugzilla.pokylinux.org/show_bug.cgi?id=574
> > 
> > I'm not at all familiar with PPC machines and not especially familiar
> > with Arm but I assume these are new machine definitions which you've
> > added? If that is the case can you share the machine configurations,
> > this could help us (or more knowledgeable others) to work out your
> > issue?
> 
> I sent one of the configs (kilauea = PPC405EX) as part of these
> patches, please see
> http://thread.gmane.org/gmane.linux.embedded.poky/942/focus=946
> 
> The other one (tqm5200 = MPC5200) is an attachment to
> http://bugzilla.pokylinux.org/show_bug.cgi?id=574 - please see
> http://bugzilla.pokylinux.org/attachment.cgi?id=78
> 
> > Do you have more success if you use one of the machines we already have
> > in the Poky tree? qemuppc and mpc8315e-rdb for PPC or qemuarm and
> > beagleboard for Arm?
> 
> I didn't try qemuppc yet; I successfully built mpc8315e-rdb for
> laverne on Fedora 13 (but failed on F 14). Did not try current master
> yet.

OK, I have filed an issue in our Bugzilla - we need to pull together a
Laverne point release for F14.
http://bugzilla.pokylinux.org/show_bug.cgi?id=578

Thanks,
Joshua
-- 
Joshua Lock
        Intel Open Source Technology Centre



  reply	other threads:[~2010-12-09 18:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-07 21:13 [PATCH 0/5] Fedora 14 Patches Wolfgang Denk
2010-12-07 21:13 ` [PATCH 1/5] eglibc: fix build issue with make-3.82 Wolfgang Denk
2010-12-07 21:14 ` [PATCH 2/5] gstreamer: " Wolfgang Denk
2010-12-07 21:14 ` [PATCH 3/5] Add support for 40x configuration (kilauea from OE) Wolfgang Denk
2010-12-07 21:14 ` [PATCH 4/5] elfutils-0.148: fix build problem with "ar" Wolfgang Denk
2010-12-07 21:14 ` [PATCH 5/5] elfutils-0.148: fix problems with `ld' not recognizing options Wolfgang Denk
2010-12-07 22:01 ` [PATCH 0/5] Fedora 14 Patches Wolfgang Denk
2010-12-08 11:24 ` Paul Eggleton
2010-12-08 11:35   ` Wolfgang Denk
2010-12-08 22:18     ` Saul Wold
2010-12-09  8:58       ` Wolfgang Denk
2010-12-09 12:30         ` Joshua Lock
2010-12-09 15:43           ` Leon Woestenberg
2010-12-09 16:57             ` Richard Purdie
2010-12-09 16:06           ` Wolfgang Denk
2010-12-09 18:46             ` Joshua Lock [this message]
2010-12-09 22:01               ` Wolfgang Denk
2010-12-09 17:29           ` Wolfgang Denk
2010-12-09 18:40             ` Joshua Lock
2010-12-09 19:58               ` Wolfgang Denk
2010-12-09 19:25         ` Saul Wold
2010-12-08 16:39   ` Wolfgang Denk

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=1291920397.6078.39.camel@scimitar \
    --to=josh@openedhand.com \
    --cc=poky@yoctoproject.org \
    --cc=wd@denx.de \
    /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