Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <poky@yoctoproject.org>, <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/3] Fix zypper integration
Date: Wed, 30 Mar 2011 15:29:11 -0500	[thread overview]
Message-ID: <cover.1301516765.git.mark.hatle@windriver.com> (raw)

Fix the zypper integration on Bernard (Poky).  This is also be necessary 
in master/OE-core as well!  (I have not verified that the C++ workaround 
is needed on OE-Core, but the same change for MIPS -is- needed due to 
namespace collision.)

Fixes [YOCTO #827] Zypper not working on ARM.  (Note, one of the issues 
resolved actually affects all host types..)

Pull URL: git://git.pokylinux.org/poky-contrib.git
  Branch: mhatle/bernard/zypper
  Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=mhatle/bernard/zypper

Thanks,
    Mark Hatle <mark.hatle@windriver.com>
---


Mark Hatle (3):
  Fix sat-solver & RPM5 integration issue
  Fix integration of zypper and sat-solver
  Workaround for Global C++ Constructor problem on ARM

 .../libzypp/libzypp/archconf.patch                 |   15 -
 .../arm-workaround-global-constructor.patch        |   68 +++
 .../libzypp/libzypp/builtin-arch.patch             |  122 -----
 .../libzypp/libzypp/libzypp-pokyarch.patch         |  498 ++++++++++++++++++++
 .../libzypp/libzypp/no-builtin-arch.patch          |  128 -----
 meta/recipes-extended/libzypp/libzypp_git.bb       |  120 ++++-
 .../sat-solver/sat-solver/builtin-arch.patch       |   28 --
 .../sat-solver/sat-solver/no-builtin-arch.patch    |   29 --
 .../sat-solver/sat-solver_obsolete.patch           |   20 +
 .../sat-solver/sat-solver/sat-solver_poky.patch    |  106 +++++
 meta/recipes-extended/sat-solver/sat-solver_git.bb |   43 +-
 11 files changed, 820 insertions(+), 357 deletions(-)
 delete mode 100644 meta/recipes-extended/libzypp/libzypp/archconf.patch
 create mode 100644 meta/recipes-extended/libzypp/libzypp/arm-workaround-global-constructor.patch
 delete mode 100644 meta/recipes-extended/libzypp/libzypp/builtin-arch.patch
 create mode 100644 meta/recipes-extended/libzypp/libzypp/libzypp-pokyarch.patch
 delete mode 100644 meta/recipes-extended/libzypp/libzypp/no-builtin-arch.patch
 delete mode 100644 meta/recipes-extended/sat-solver/sat-solver/builtin-arch.patch
 delete mode 100644 meta/recipes-extended/sat-solver/sat-solver/no-builtin-arch.patch
 create mode 100644 meta/recipes-extended/sat-solver/sat-solver/sat-solver_obsolete.patch
 create mode 100644 meta/recipes-extended/sat-solver/sat-solver/sat-solver_poky.patch

-- 
1.7.3.4




             reply	other threads:[~2011-03-30 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 20:29 Mark Hatle [this message]
2011-03-30 20:29 ` [PATCH 1/3] Fix sat-solver & RPM5 integration issue Mark Hatle
2011-03-30 20:29 ` [PATCH 2/3] Fix integration of zypper and sat-solver Mark Hatle
2011-03-30 20:29 ` [PATCH 3/3] Workaround for Global C++ Constructor problem on ARM Mark Hatle
2011-03-31 14:35 ` [PATCH 0/3] Fix zypper integration Richard Purdie

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.1301516765.git.mark.hatle@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox