Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dexuan Cui <dexuan.cui@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] self-hosted-image: the first set of patch
Date: Thu, 24 Nov 2011 18:08:10 +0800	[thread overview]
Message-ID: <cover.1322128489.git.dexuan.cui@intel.com> (raw)

This is the first patchset for the task Build Applianc: self-hosted-image:
https://wiki.yoctoproject.org/wiki/Build_Appliance_Design

The only notable issue left is:
there is an eglibc_initial do_insall failure that seems be caused by make-3.82.
If we downgrade to make-3.81(the hacking patch is at
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/commit/?h=gzhai/build-appliance&id=981a37e3e031e7c96361c1c170050ab3cdbadf6c),
"bitbake core-image-minimal" in the target can build fine. The built image can
run fine with host's qemu (in target, runqemu doesn't work yet as at least
sudo is absent -- we're fixing this).

The above patchset was done by the Build Appliance development team, including
Saul, Edwin and me.

Though there are still some known issues, now we want to share the patches.
Please review, comment and merge them(if they seem good :-).


Thanks!

-- Dexuan, on behalf of the team


The following changes since commit dc2d701207435b0dbd521a11d152f11d0f18d11e:

  apt: Fix locale header and hardcoded libname issues (2011-11-23 23:41:09 +0000)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib dcui/self-hosted-v2
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dcui/self-hosted-v2

Dexuan Cui (2):
  gcc-package-target.inc: add the symbol link /lib/cpp
  coreutils: build and install hostname

Saul Wold (2):
  runqemu: look for *image* to be more flexible for image names
  Self Hosted Image: Added Task and Images

 .../coreutils/coreutils-8.14/disable_doc_man.patch |   36 ++++
 meta/recipes-core/coreutils/coreutils_8.14.bb      |    9 +-
 meta/recipes-core/images/self-hosted-image.bb      |   11 ++
 meta/recipes-core/tasks/task-self-hosted.bb        |  174 ++++++++++++++++++++
 meta/recipes-devtools/gcc/gcc-4.6.inc              |    2 +-
 meta/recipes-devtools/gcc/gcc-package-target.inc   |    2 +
 scripts/runqemu                                    |    4 +-
 7 files changed, 231 insertions(+), 7 deletions(-)
 create mode 100644 meta/recipes-core/coreutils/coreutils-8.14/disable_doc_man.patch
 create mode 100644 meta/recipes-core/images/self-hosted-image.bb
 create mode 100644 meta/recipes-core/tasks/task-self-hosted.bb

-- 
1.7.6




             reply	other threads:[~2011-11-24 10:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 10:08 Dexuan Cui [this message]
2011-11-24 10:08 ` [PATCH 1/4] runqemu: look for *image* to be more flexible for image names Dexuan Cui
2011-11-24 21:50   ` Richard Purdie
2011-11-24 10:08 ` [PATCH 2/4] gcc-package-target.inc: add the symbol link /lib/cpp Dexuan Cui
2011-11-24 11:21   ` Richard Purdie
2011-11-24 15:37     ` Cui, Dexuan
2011-11-24 16:23       ` Richard Purdie
2011-11-24 23:09         ` Cui, Dexuan
2011-11-24 23:34           ` Richard Purdie
2011-11-24 10:08 ` [PATCH 3/4] Self Hosted Image: Added Task and Images Dexuan Cui
2011-11-24 10:08 ` [PATCH 4/4] coreutils: build and install hostname Dexuan Cui
2011-11-29  8:15   ` Saul Wold

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=cover.1322128489.git.dexuan.cui@intel.com \
    --to=dexuan.cui@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox