From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Markus Volk <f_l_k@t-online.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH 2/4] python3: add libxcrypt-native dependency
Date: Mon, 29 May 2023 08:08:09 +0100 [thread overview]
Message-ID: <7bb5f101af77af3a051a1b049206800aec542ccd.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj_-ptiJqvmf+cU0qV7VkKG0ds=guN9aTU1VirjcG8WjQA@mail.gmail.com>
On Sun, 2023-05-28 at 17:16 +0200, Alexander Kanavin wrote:
> Adding libxcrypt-native to DEPENDS definitely isn't correct, so you
> could check why virtual/crypt dependency isn't working properly for
> adding the needed headers into native variant's sysroot. If all fails,
> adjust DEPENDS:append:class-native.
Alex is right and I should have spotted this, the -native dependency
definitely isn't right. We'll either need to fix things or revert them
and wait for the right fix...
Cheers,
Richard
next prev parent reply other threads:[~2023-05-29 7:08 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 [this message]
[not found] ` <ZG5FVR.L4YKBKAES08S3@googlemail.com>
2023-05-29 12:34 ` Richard Purdie
2023-06-03 17:51 ` Markus Volk
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=7bb5f101af77af3a051a1b049206800aec542ccd.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=f_l_k@t-online.de \
--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 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.