From: Joshua Lock <josh@openedhand.com>
To: poky@yoctoproject.org
Subject: Re: [PATCH 0/5] Fedora 14 Patches
Date: Thu, 09 Dec 2010 12:30:25 +0000 [thread overview]
Message-ID: <1291897825.6078.11.camel@scimitar> (raw)
In-Reply-To: <20101209085846.264F5D301D6@gemini.denx.de>
On Thu, 2010-12-09 at 09:58 +0100, Wolfgang Denk wrote:
> Dear Saul,
>
> In message <4D00042C.6040403@linux.intel.com> you wrote:
> >
> > Thanks for your patches and assistance.
> >
> > Not sure if you saw the Release Notes regarding F14 and building
> > make-native first and installing that locally due to problems with F14's
> > make. See http://bugzilla.pokylinux.org/show_bug.cgi?id=467
> > and http://www.yoctoproject.org/download/yocto-project-4-0-release-notes
>
> Yes, I saw trhis, but decided it made more sense to fix the broken
> Makefiles, especially as this was trivial to do, and in case of eglibc
> I could just apply the corresponding commit from OE.
>
> But actually the make-3.82 issues are the smallest of my problems.
>
> 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?
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?
FWIW I have successfully built and run a minimal image on the
mpc8315e-rdb and the beagleboard using the Laverne tree.
>
> Are there any plans to include PPC and ARM targets for example int he
> autobuilder testing?
We already do, the autobuilder currently tests qemuarm and qemuppc and I
believe we will be adding beagleboard and mpc8315e-rdb.
>
> > Yes, this should build you can see the status of master on our build
> > machine at http://autobuilder.pokylinux.org:8010/waterfall we are
> > working on stabilizing the build (meta-toolchain-sdk is failing currently).
>
> What I cannot see (maybe I just don't know where to look) is if the
> autobuilder includes any PPC and ARM targets at all, and if so, which
> these are.
Yes, fair point - this is not obvious.
Cheers,
Joshua
next prev parent reply other threads:[~2010-12-09 12:30 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 [this message]
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
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=1291897825.6078.11.camel@scimitar \
--to=josh@openedhand.com \
--cc=poky@yoctoproject.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.