From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-f178.google.com (mail-qt1-f178.google.com [209.85.160.178]) by mail.openembedded.org (Postfix) with ESMTP id 2714F6C3E1 for ; Thu, 21 Nov 2019 13:15:41 +0000 (UTC) Received: by mail-qt1-f178.google.com with SMTP id n4so3629147qte.2 for ; Thu, 21 Nov 2019 05:15:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nuHqm8ncWslqAyygXu3xyIJjKFauC83sWUv/8M9QBTU=; b=ck2gLAX/dRSbIAOUHP9kdaosiTGGOVTOeyghoxITzSsGYWeN7OW2L1VgGIuJNYDlJo YzF+gJdbbKyDcjxFofnICn+N5g67QWKywRM1MGq0B5IywllwvdA8jsxk7Spbk7AQO6eu RybndcXues64oSFS+746iKonkclWNCUHN7P/3HAd0gd1x9wxGk8fyFrxcNk5zhipHu+z 7X8iXkRiKuWKHETEAGwhA3i/8bRcvImG8iS7XCt1z5L4qndPOxovGS0RRmRPKFcOloPr bzX69zd1J03L/E7lkUimvFIPBD6AnqcuR75aptL/O0kItNLSWrN/XaX9lXRKDu3YTeJ5 HZZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=nuHqm8ncWslqAyygXu3xyIJjKFauC83sWUv/8M9QBTU=; b=IjS2CT2cJ3EwS0NFVxiU+zoEpqKuw34rSZh3MA2ajOouClGGFcllET0SPpCnCG4liu xV0+mz01cesxJj8KXk67hpawgdf8exk9fLCTkvsveqezWNz+8VtKffoTXL5Cvad638v1 mvJn91kwmTTE0I1H1+XK7gXtb/uFj6jFJipN2XHWedsspzJAngC2H2SxFXGfOBXthXEx w946vpYXGyJCybTSbGevkQmJnUDnBzEGkaQV9cDzFCHG4AFbECknIZ8Yqt7dvhByNf7t GLYY3em63/T+Cx1QJphm7m6ZuZweoWcbMsDksCTTpkW5s4/vhOUBw00qokDqEbA+pOWh 4tKg== X-Gm-Message-State: APjAAAWXZkhPZU5GIfLJS+Zx11E76zQ0y0OrocZW9QEKLqc63JrfKr9E kl4taLnBbkWuK//QEGEkmarGbnXV3o+31QniuxOp9g== X-Google-Smtp-Source: APXvYqyQSESK8vQe/hzZdwNz4JUB1WsUEXne3QN9A9ykMllGTZjpTRBRWRwmapuGAw2UatTWAfBxoJ3NhAJaOCh2VZQ= X-Received: by 2002:ac8:2bd1:: with SMTP id n17mr1657820qtn.382.1574342142873; Thu, 21 Nov 2019 05:15:42 -0800 (PST) MIME-Version: 1.0 References: <5c9cb09a-e0b3-f43b-36cd-bc9a7df2dd6c@kernel.crashing.org> <31b224ae-8e1a-943c-0554-684557ef33bc@kernel.crashing.org> In-Reply-To: From: Ryan Harkin Date: Thu, 21 Nov 2019 13:15:31 +0000 Message-ID: To: Andre McCurdy Cc: Patches and discussions about the oe-core layer Subject: Re: How to backport openssl to Sumo X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Nov 2019 13:15:42 -0000 Content-Type: multipart/alternative; boundary="0000000000002e677d0597db18b2" --0000000000002e677d0597db18b2 Content-Type: text/plain; charset="UTF-8" On Wed, 20 Nov 2019 at 23:53, Andre McCurdy wrote: > On Wed, Nov 20, 2019 at 2:41 PM Ryan Harkin > wrote: > > On Wed, 20 Nov 2019 at 21:29, Ryan Harkin > wrote: > >> > >> I pulled the whole openssl dir from your repo, added the layer.conf > changes to my layer.conf and rebuilt openssl and my image. > >> > >> Unfortunately, I still have no /usr/bin/openssl in my disk image. So > I've added the RPROVIDES from Andre's in a vain attempt to get it to work: > >> > >> RPROVIDES_${PN} += "openssl-bin" > >> > >> ... although I'm not hopeful it'll do the trick... > > > > It didn't work. Once thing that's puzzling me: where is the package > "openssl-bin"? I can only find references to it, but no package. > > The "openssl-bin" package is created by the openssl 1.1.x recipe. > > Adding "openssl-bin" to RPROVIDES in the openssl 1.0.2 recipe is a > solution for users who are switching from openssl 1.1.x back to 1.0.2 > and have an image which is tries to include the new openssl-bin > package. I don't think that's what you are trying to do (?). > Correct. I only tried it because the 1.0.2t recipe wasn't working. To be clear - I have /usr/bin/openssl in my image when using 1.0.2p from the Poky Sumo branch. When I add the 1.0.2t recipe to my own layer, openssl builds without errors, but I don't get the binary. > If you are using openssl 1.0.2 then the openssl command line tool is > in the openssl package... so to include the openssl command line tool, > add the "openssl" package to your image. > > If you are using openssl 1.1.x then the openssl command line tool is > in the openssl-bin package... so to include the openssl command line > tool, add the "openssl-bin" package to your image. > > But anyway, in all cases, the way to debug what's going on isn't to > try random recipe changes and then rebuild the final image. Instead > you should build your chosen version of openssl, look in the > packages-split directory to see which package includes the openssl > command line tool and then add that package to your image. > I don't have a packages-split. I was unaware of it, and reading the manual, it seems I should have one. But I don't. Running 'bitbake -e openssl | grep "PKGDEST="' tells me I should have one, but there are no instances in a directory called "packages-split" in my tmp dir. Anyway, I'm giving up for now. I'll come back to another time... or more likely, get someone smarter than me to sort it out ;-) --0000000000002e677d0597db18b2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, 20 Nov 2019 at 23:53, Andre M= cCurdy <armccurdy@gmail.com&g= t; wrote:
On Wed= , Nov 20, 2019 at 2:41 PM Ryan Harkin <ryan.harkin@linaro.org> wrote:
> On Wed, 20 Nov 2019 at 21:29, Ryan Harkin <ryan.harkin@linaro.org> wrote: >>
>> I pulled the whole openssl dir from your repo, added the layer.con= f changes to my layer.conf and rebuilt openssl and my image.
>>
>> Unfortunately, I still have no /usr/bin/openssl in my disk image. = So I've added the RPROVIDES from Andre's in a vain attempt to get i= t to work:
>>
>> RPROVIDES_${PN} +=3D "openssl-bin"
>>
>> ... although I'm not hopeful it'll do the trick...
>
> It didn't work. Once thing that's puzzling me: where is the pa= ckage "openssl-bin"? I can only find references to it, but no pac= kage.

The "openssl-bin" package is created by the openssl 1.1.x recipe.=

Adding "openssl-bin" to RPROVIDES in the openssl 1.0.2 recipe is = a
solution for users who are switching from openssl 1.1.x back to 1.0.2
and have an image which is tries to include the new openssl-bin
package. I don't think that's what you are trying to do (?).

Correct. I only tried it because the 1.0.2t r= ecipe wasn't working.

To be clear - I have /us= r/bin/openssl in my image when using 1.0.2p from the Poky Sumo branch. When= I add the 1.0.2t recipe to my own layer, openssl builds without errors, bu= t I don't get the binary.


If you are using openssl 1.0.2 then the openssl command line tool is
in the openssl package... so to include the openssl command line tool,
add the "openssl" package to your image.

If you are using openssl 1.1.x then the openssl command line tool is
in the openssl-bin package... so to include the openssl command line
tool, add the "openssl-bin" package to your image.

But anyway, in all cases, the way to debug what's going on isn't to=
try random recipe changes and then rebuild the final image. Instead
you should build your chosen version of openssl, look in the
packages-split directory to see which package includes the openssl
command line tool and then add that package to your image.
=

I don't have a packages-split. I was unaware of it,= and reading the manual, it seems I should have one. But I don't. Runni= ng 'bitbake -e openssl | grep "PKGDEST=3D"' tells me I sh= ould have one, but there are no instances in a directory called "packa= ges-split" in my tmp dir.
=C2=A0
Anyway, I'm g= iving up for now. I'll come back to another time... or more likely, get= someone smarter than me to sort it out ;-)
--0000000000002e677d0597db18b2--