From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/5] libtirpc: Enable des APIs for musl
Date: Wed, 19 Apr 2017 09:57:23 +0100 [thread overview]
Message-ID: <1492592243.15070.1.camel@andred.net> (raw)
In-Reply-To: <20170419015839.1294-3-raj.khem@gmail.com>
On Tue, 2017-04-18 at 18:58 -0700, Khem Raj wrote:
> Use memset() API instead of __bzero()
> Drop the patch removing des_* functions for musl
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> .../0001-replace-__bzero-with-memset-API.patch | 28 +++++
> .../libtirpc/remove-des-functionality.patch | 139 ----------------
> -----
> meta/recipes-extended/libtirpc/libtirpc_1.0.1.bb | 5 +-
> 3 files changed, 31 insertions(+), 141 deletions(-)
> create mode 100644 meta/recipes-extended/libtirpc/libtirpc/0001-replace-
> __bzero-with-memset-API.patch
> delete mode 100644 meta/recipes-extended/libtirpc/libtirpc/remove-des-
> functionality.patch
>
> [...]
>
>
> SRC_URI_append_libc-uclibc = " file://remove-des-functionality.patch \
This patch is being removed with this change, and so uclibc builds will
fail. Is it time to remove all remaining references to uclibc?
Cheers,
Andre'
next prev parent reply other threads:[~2017-04-19 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 1:58 [PATCH 1/5] libtirpc: Backport fixes from 1.0.2rc3 Khem Raj
2017-04-19 1:58 ` [PATCH 2/5] libtirpc: Expose key_secretkey_is_set API Khem Raj
2017-04-19 8:52 ` Burton, Ross
2017-04-19 16:25 ` Khem Raj
2017-04-19 16:36 ` Burton, Ross
2017-04-19 16:37 ` Khem Raj
2017-04-19 1:58 ` [PATCH 3/5] libtirpc: Enable des APIs for musl Khem Raj
2017-04-19 8:57 ` André Draszik [this message]
2017-04-19 12:53 ` Burton, Ross
2017-04-19 16:34 ` Khem Raj
2017-04-19 1:58 ` [PATCH 4/5] rpcbind: Remove uneeded patches Khem Raj
2017-04-19 1:58 ` [PATCH 5/5] libidn: Fix build with gcc7 Khem Raj
2017-04-19 15:06 ` André Draszik
2017-04-19 16:36 ` Khem Raj
2017-04-19 2:01 ` ✗ patchtest: failure for "libtirpc: Backport fixes from ..." and 4 more Patchwork
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=1492592243.15070.1.camel@andred.net \
--to=git@andred.net \
--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