From: Jonathan Liu <net147@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-gnome][PATCH] gnome-keyring: Fix build error due to missing asn1 prototypes
Date: Wed, 12 Jun 2013 23:58:30 +1000 [thread overview]
Message-ID: <51B87E86.9010709@gmail.com> (raw)
In-Reply-To: <1370992564-19617-1-git-send-email-raj.khem@gmail.com>
On 12/06/2013 9:16 AM, Khem Raj wrote:
> This fixes the errors that started to pop up recently
> while building gnome-keyring as part of gnome images
> The error is decribed in patch header
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> .../gnome-keyring/gnome-keyring/egg-asn1x.patch | 55 ++++++++++++++++++++
> .../gnome-keyring/gnome-keyring_2.32.1.bb | 3 +-
> 2 files changed, 57 insertions(+), 1 deletion(-)
> create mode 100644 meta-gnome/recipes-gnome/gnome-keyring/gnome-keyring/egg-asn1x.patch
Signed-off-by: Jonathan Liu <net147@gmail.com>
prev parent reply other threads:[~2013-06-12 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 23:16 [meta-gnome][PATCH] gnome-keyring: Fix build error due to missing asn1 prototypes Khem Raj
2013-06-12 13:58 ` Jonathan Liu [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=51B87E86.9010709@gmail.com \
--to=net147@gmail.com \
--cc=openembedded-devel@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