All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
	Khem Raj <raj.khem@gmail.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH 2/4] python3: add libxcrypt-native dependency
Date: Sat, 03 Jun 2023 19:51:59 +0200	[thread overview]
Message-ID: <NYUOVR.OW8C8JU503CT2@t-online.de> (raw)
In-Reply-To: <0718565165c8175882355d0674588f71c36b8bb7.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 980 bytes --]

Am Mo, 29. Mai 2023 um 13:34:40 +0100 schrieb Richard Purdie 
<richard.purdie@linuxfoundation.org>:
> I'm going to revert those changes and then we can work out the correct
> fix without any time pressures (and then I won't need to keep this on
> my 'need to do something about' mental checklist!).

I had some time to look at this problem. virtual/crypt-native is not 
installed into recipe-sysroot-native because of this entry in 
bitbake.conf:
ASSUME_PROVIDED = "virtual/crypt-native"

Removing the entry solved the issue for me. I could successfully build 
core-image-minimal for musl and glibc without crypt.h from host machine.

But I don't know the reason why this is ASSUME_PROVIDED, so I'm unsure 
if this should even be touched.

In a second step I created a musl-native recipe to be able to install 
musl crypt.h into recipe-sysroot-native, but I'm not sure if this is 
necessary either.

<https://github.com/MarkusVolk/openembedded-core/commits/virtual/crypt-native>


[-- Attachment #2: Type: text/html, Size: 1343 bytes --]

  reply	other threads:[~2023-06-03 17:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-27 13:32 [oe-core][PATCH 1/4] ell: upgrade 0.56 -> 0.57 Markus Volk
2023-05-27 13:32 ` [oe-core][PATCH 2/4] python3: add libxcrypt-native dependency Markus Volk
2023-05-28 13:39   ` Alexander Kanavin
2023-05-28 13:56     ` Markus Volk
     [not found]   ` <17635252DFD4EDDE.6918@lists.openembedded.org>
2023-05-28 13:41     ` Alexander Kanavin
2023-05-28 14:03       ` Markus Volk
2023-05-28 14:23         ` Alexander Kanavin
2023-05-28 14:53           ` Markus Volk
2023-05-28 15:01             ` Alexander Kanavin
2023-05-28 15:08               ` Markus Volk
2023-05-28 15:16                 ` Alexander Kanavin
2023-05-29  7:08                   ` Richard Purdie
     [not found]                     ` <ZG5FVR.L4YKBKAES08S3@googlemail.com>
2023-05-29 12:34                       ` Richard Purdie
2023-06-03 17:51                         ` Markus Volk [this message]
2023-06-03 18:20                           ` Alexander Kanavin
2023-06-04 19:53                             ` Markus Volk
2023-05-27 13:32 ` [oe-core][PATCH 3/4] ruby: " Markus Volk
2023-05-27 13:32 ` [oe-core][PATCH 4/4] shadow: " Markus Volk

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=NYUOVR.OW8C8JU503CT2@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.