Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] V2: Fix rpm2cpio segment fault
Date: Mon, 15 Apr 2013 11:21:05 +0800	[thread overview]
Message-ID: <516B7221.5010409@windriver.com> (raw)
In-Reply-To: <cover.1365995348.git.kai.kang@windriver.com>

On 2013年04月15日 11:17, Kang Kai wrote:
> Hi Mark,
>
> As my last mail on Apr 12 mentioned, not only macro "_dbpath" need to be defined. Macros "_dbi_config*" are needed too, and they can't be simply assigned some value.
>
> I think parse config files first could be a workaround to fix rpm2cpio segment fault error for now.

Update:
If parse config files fails, just give warning.

>
> Thanks,
> Kai
>
>
> The following changes since commit 4c02dd5f6432c6e683a57d47b610f56433e9ca0d:
>
>    kern-tools: fix conditional configuration items (2013-04-11 08:27:41 +0100)
>
> are available in the git repository at:
>    git://git.pokylinux.org/poky-contrib kangkai/rpm2cpio-segfault
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/rpm2cpio-segfault
>
> Kang Kai (1):
>    rpm: fix rpm2cpio segmentation fault
>
>   .../rpm/rpm/rpm2cpio-fix-segmentation-fault.patch  |   28 ++++++++++++++++++++
>   meta/recipes-devtools/rpm/rpm_5.4.9.bb             |    1 +
>   2 files changed, 29 insertions(+), 0 deletions(-)
>   create mode 100644 meta/recipes-devtools/rpm/rpm/rpm2cpio-fix-segmentation-fault.patch
>


-- 
Regards,
Neil | Kai Kang




      parent reply	other threads:[~2013-04-15  3:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15  3:17 [PATCH 0/1] V2: Fix rpm2cpio segment fault Kang Kai
2013-04-15  3:17 ` [PATCH 1/1] rpm: fix rpm2cpio segmentation fault Kang Kai
2013-04-15  3:21 ` Kang Kai [this message]

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=516B7221.5010409@windriver.com \
    --to=kai.kang@windriver.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