All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <gmane@reliableembeddedsystems.com>
To: poky@pokylinux.org
Subject: Third party toolchain, kernel, bootloader
Date: Fri, 06 May 2011 09:28:42 +0300	[thread overview]
Message-ID: <iq04eq$4qb$1@dough.gmane.org> (raw)

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.

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.

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?

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




             reply	other threads:[~2011-05-06  6:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  6:28 Robert Berger [this message]
2011-05-06 17:09 ` Third party toolchain, kernel, bootloader Darren Hart
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='iq04eq$4qb$1@dough.gmane.org' \
    --to=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.