All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Scott Ellis" <jumpnowtek@gmail.com>
To: yocto@lists.yoctoproject.org
Cc: Scott Ellis <scott@jumpnowtek.com>
Subject: Re: [yocto][PATCH] openssl: Fix dependency loop with PACKAGECONFIG cryptodev-linux
Date: Fri, 1 May 2020 09:48:14 -0400	[thread overview]
Message-ID: <CAAAx1o7j=dmhKOm4QKLvShjSikxL4kOk1m6LMXupoBaBtWuttw@mail.gmail.com> (raw)
In-Reply-To: <20200430213705.GW11927@denix.org>

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

Enabled via a bbappend in a custom layer

$ cat openssl_%.bbappend
PACKAGECONFIG_append = " cryptodev-linux"

This was working prior to the openssl_1.1.1f.bb recipe change a few days
ago.

How are you enabling this PACKAGECONFIG?

On Thu, Apr 30, 2020 at 5:37 PM Denys Dmytriyenko <denis@denix.org> wrote:

> On Thu, Apr 30, 2020 at 08:23:11PM +0000, Scott Ellis wrote:
>
> Hi, Scott,
>
> Sorry, I'm not trying to discourage you from submitting patches, but there
> are
> few issues with your patch here - see below and inline.
>
> First of all, patches for OE-core should be sent to:
> openembedded-core@lists.openembedded.org
> https://lists.openembedded.org/g/openembedded-core
>
> Looks like you are building poky-zeus - Poky, as a distro, is composed
> from
> multiple components/layers, such as bitbake, oe-core/meta, meta-poky and
> meta-yocto-bsp. Most of them have own git repos with corresponding mailing
> lists - usually mentioned in corresponding README files, please check
> those.
>
>
> > Applies to both zeus and dunfell
>
> The process to get your change backported to older branches/releases is to
> submit it against master, and once accepted, re-send and ask to backport
> to
> other branches, such as zeus and dunfell with the name of the branch in
> the
> subject. That is because different branches/versions are usually
> maintained
> by different people.
>
>
> > ERROR: Nothing RPROVIDES 'cryptodev-module-native' (but
> virtual:native:/home/scott/poky-zeus/meta/recipes-connectivity/openssl/
> openssl_1.1.1f.bb RDEPENDS on or otherwise requires it)
> > ERROR: Required build target 'openssl' has no buildable providers.
> > Missing or unbuildable dependency chain was: ['openssl', 'rpm-native',
> 'python3-native', 'openssl-native', 'cryptodev-module-native']
>
> Not sure how you were able to set the wrong PACKAGECONFIG for
> openssl-native,
> when it gets explicitly emptied in the recipe below.
>
>
> > diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
> b/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
> > index aa4ef6f48a..a952fae728 100644
> > --- a/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
> > +++ b/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
> > @@ -32,7 +32,7 @@ PACKAGECONFIG ?= ""
> >  PACKAGECONFIG_class-native = ""
> >  PACKAGECONFIG_class-nativesdk = ""
>
> Here, ^^^ PACKAGECONFIG should all be empty for native and nativesdk
> versions
> of openssl.
>
>
> > -PACKAGECONFIG[cryptodev-linux] =
> "enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux,,cryptodev-module"
> > +PACKAGECONFIG[cryptodev-linux] =
> "enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux"
>
> This is not a fix, but rather a workaround for a bad setup. Moreover, it
> actually reverts my recent fix to RDEPENDS on cryptodev-module, which is
> needed to properly support devcryptoeng in openssl.
>
> Maybe if you share with us how you set your environment, we would be able
> to
> help you resolve it properly. Thank you!
>
> --
> Denys
>
>
> >  B = "${WORKDIR}/build"
> >  do_configure[cleandirs] = "${B}"
> > --
> > 2.17.1
> >
>
> >
>
> 
>

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

      reply	other threads:[~2020-05-01 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-30 20:23 [yocto][PATCH] openssl: Fix dependency loop with PACKAGECONFIG cryptodev-linux Scott Ellis
2020-04-30 21:37 ` Denys Dmytriyenko
2020-05-01 13:48   ` Scott Ellis [this message]

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='CAAAx1o7j=dmhKOm4QKLvShjSikxL4kOk1m6LMXupoBaBtWuttw@mail.gmail.com' \
    --to=jumpnowtek@gmail.com \
    --cc=scott@jumpnowtek.com \
    --cc=yocto@lists.yoctoproject.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.