Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>,
	Charles-Antoine Couret <charles-antoine.couret@essensium.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Split glibc and libcrypt
Date: Fri, 06 Apr 2018 16:42:07 +0100	[thread overview]
Message-ID: <1523029327.2942.18.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1srQLn+7YKX0AeE00Y+r=7PC4R7cFUjGNm9wjEa0kVr8gA@mail.gmail.com>

On Fri, 2018-04-06 at 08:03 -0700, Khem Raj wrote:
> this series is ok. Although dont like the fact its not upstream yet
> but it reduces glibc baggage for future.

Were you able to find out if glibc will definitely do this?

I think applying this nativesdk is the only thing we can do right now
and it does set us up well to migrate this further if glibc do go for
this. After thinking about this a bit, the patch series needs a few
minor tweaks to avoid wider testing failures:

a) libxcrypt needs to SkipRecipe in the target case and be nativesdk 
   only
b) We need an RDEPENDS_${PN}_append_class-nativesdk = " libxcrypto" in 
   glibc-package.inc
c) The override used in glibc-pacjage.inc is wrong suggesting the code 
   can be dropped.

Good news is a few of us tested this on f28, f27, ubuntu 1604 and 1710
and the new uninative built with it seems to work well.

Cheers,

Richard


  reply	other threads:[~2018-04-06 15:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 12:53 [PATCH 0/2] Split glibc and libcrypt Charles-Antoine Couret
2018-04-06 12:53 ` [PATCH 1/2] glibc: split " Charles-Antoine Couret
2018-04-06 12:53 ` [PATCH 2/2] perl: add patch to solve libcrypt incompatibility Charles-Antoine Couret
2018-04-06 13:03 ` ✗ patchtest: failure for Split glibc and libcrypt Patchwork
2018-04-06 15:03 ` [PATCH 0/2] " Khem Raj
2018-04-06 15:42   ` Richard Purdie [this message]
2018-04-06 16:27     ` Khem Raj
2018-04-06 17:15       ` 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=1523029327.2942.18.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=charles-antoine.couret@essensium.com \
    --cc=openembedded-core@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