From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 04/14] gpm: Update to use git src uri
Date: Wed, 8 Mar 2017 11:18:21 +0100 [thread overview]
Message-ID: <20170308101821.GC3279@jama> (raw)
In-Reply-To: <20170307071349.16444-4-raj.khem@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
On Mon, Mar 06, 2017 at 11:13:39PM -0800, Khem Raj wrote:
> Additional patches are upstream to fix build with gcc6 and clang
> Add systemd unit file
And one more error later in do_install:
http://errors.yoctoproject.org/Errors/Details/134813/
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> .../gpm/gpm-1.99.7/eglibc-2.17.patch | 12 -
> .../gpm/gpm-1.99.7/remove_nested_functions.patch | 326 ---------------------
> meta-oe/recipes-support/gpm/gpm/gpm.service.in | 9 +
> .../recipes-support/gpm/{gpm-1.99.7 => gpm}/init | 0
> .../gpm/{gpm-1.99.7 => gpm}/no-docs.patch | 2 +-
> .../gpm/{gpm-1.99.7 => gpm}/processcreds.patch | 0
> meta-oe/recipes-support/gpm/gpm_1.99.7.bb | 52 ++--
> 7 files changed, 31 insertions(+), 370 deletions(-)
> delete mode 100644 meta-oe/recipes-support/gpm/gpm-1.99.7/eglibc-2.17.patch
> delete mode 100644 meta-oe/recipes-support/gpm/gpm-1.99.7/remove_nested_functions.patch
> create mode 100644 meta-oe/recipes-support/gpm/gpm/gpm.service.in
> rename meta-oe/recipes-support/gpm/{gpm-1.99.7 => gpm}/init (100%)
> rename meta-oe/recipes-support/gpm/{gpm-1.99.7 => gpm}/no-docs.patch (93%)
> rename meta-oe/recipes-support/gpm/{gpm-1.99.7 => gpm}/processcreds.patch (100%)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2017-03-08 10:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 7:13 [meta-oe][PATCH 01/14] t1lib: Fix printf format string errors Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 02/14] fftw: Update to 3.3.6 release Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 03/14] libxml++: Update to 2.40.1 Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 04/14] gpm: Update to use git src uri Khem Raj
2017-03-08 10:16 ` Martin Jansa
2017-03-08 10:18 ` Martin Jansa [this message]
2017-03-29 11:05 ` Martin Jansa
2017-03-29 14:06 ` Khem Raj
2017-03-29 14:21 ` Martin Jansa
2017-03-29 14:30 ` Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 05/14] grail: Disable elision warnings for clang Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 06/14] gperftools: Fix build with clang Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 07/14] tbb: Update to 2017 release Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 08/14] irssi: Upgrade to 1.0.1 Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 09/14] a2jmidid: Fix build on aarch64 Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 10/14] log4c: Backport patch to fix security format errors with clang Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 11/14] rapidjson: Update to 1.1.0 + git Khem Raj
2017-03-08 10:19 ` Martin Jansa
2017-03-07 7:13 ` [meta-oe][PATCH 12/14] ltrace: Fix build with aarch64 and bump to latest Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 13/14] iptraf: Fix build with clang Khem Raj
2017-03-07 7:13 ` [meta-oe][PATCH 14/14] libtorrent, rtorrent: Update to 0.13.6+git Khem Raj
2017-03-08 10:17 ` Martin Jansa
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=20170308101821.GC3279@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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