From: Darren Hart <dvhart@linux.intel.com>
To: gmane@reliableembeddedsystems.com
Cc: poky@pokylinux.org
Subject: Re: Third party toolchain, kernel, bootloader
Date: Fri, 06 May 2011 10:09:25 -0700 [thread overview]
Message-ID: <4DC42B45.7080504@linux.intel.com> (raw)
In-Reply-To: <iq04eq$4qb$1@dough.gmane.org>
On 05/05/2011 11:28 PM, Robert Berger wrote:
> Hi,
>
> I'm working on a couple of projects trying to use yocto and it boils
> down to the fact, that the packages and the package management (with a
> few tweaks) are very valuable.
>
> On the other hand "just to give it a try" it's a major effort to add
> kernel and bootloader to poky and moreover the gcc which comes with poky
> is not always what I need in terms of stability but also features (need
> e.g. Cortex-A8 support). So I would also need to cook gcc to compile a
> vendor provided kernel and bootloader.
We build for Beagleboard xM, which is a Cortex-A8. Are you missing a
specific feature? Hitting a particular bug?
> What I'm after is to add some packages from poky to some 3rd party
> rootfs. One major problem I have is the dependency on libc6 (>= 2.12)
> Usually I have some older versions of libc6: e.g. libc-2.8.so.
>
> For the projects I'm currently working on kernel and bootloader are
> already compiling/running and tested and I would like to add packages
> like qt-embedded to the various rootfs.
Is the third party rootfs built using an older version of poky or oe?
> To achieve this I would need a mechanism to use a 3rd party toolchain
> with poky (and maybe to skip the build steps for kernel and boot loader).
>
> Is this something yocto/poky was made for, or am I totally off?
> Am I the only one who has such kind of problems?
> How are others tackling these kind of problems?
From the above I'm getting the impressions you're trying to build
package with a recent yocto for a much older image that might have even
been built with something other than yocto (or poky).
I wouldn't expect that to work. The package names, dependency names,
distribution policy, libc version (as you noticed) will fight you the
whole way.
Please elaborate if I'm misinterpreting what you are trying to do.
--
Darren
>
> Please advise,
>
> Regards,
>
> Robert
>
>
> ..."Rules of Optimization: Rule1: Don't do it. Rule 2 (for experts
> only): Don't do it yet." - M.A. Jackson (not the singer)
>
> My public pgp key is available at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x90320BF1
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-05-06 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 6:28 Third party toolchain, kernel, bootloader Robert Berger
2011-05-06 17:09 ` Darren Hart [this message]
2011-05-07 19:42 ` Robert Berger
2011-05-07 22:10 ` Xianghua Xiao
2011-05-08 15:29 ` Robert Berger
2011-05-09 17:39 ` Robert Berger
2011-05-09 17:57 ` Koen Kooi
2011-05-09 20:21 ` Robert Berger
2011-05-09 21:18 ` Darren Hart
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=4DC42B45.7080504@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=gmane@reliableembeddedsystems.com \
--cc=poky@pokylinux.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.