Openembedded Core Discussions
 help / color / mirror / Atom feed
From: <Mikko.Rapeli@bmw.de>
To: <armccurdy@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: How to backport openssl to Sumo
Date: Thu, 21 Nov 2019 08:05:05 +0000	[thread overview]
Message-ID: <20191121080503.GC3527@hiutale> (raw)
In-Reply-To: <CAJ86T=Ucx125+XdRrpnh64km1WypAyyc1fUN5pWbjXzmUSXu3g@mail.gmail.com>

On Wed, Nov 20, 2019 at 03:53:14PM -0800, Andre McCurdy wrote:
> 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.

Or enable buildhistory, build openssl and/or image(s), cd build/buildhistory
and git grep for the binaries needed to find out which binary package
they belong to.

-Mikko

  reply	other threads:[~2019-11-21  8:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 18:18 How to backport openssl to Sumo Ryan Harkin
2019-11-20 18:28 ` Ross Burton
2019-11-20 18:59   ` Ryan Harkin
2019-11-20 18:36 ` Mark Hatle
2019-11-20 19:06   ` Ryan Harkin
2019-11-20 19:09     ` Mark Hatle
2019-11-20 19:27       ` Andre McCurdy
2019-11-20 19:44         ` Ryan Harkin
2019-11-20 19:57           ` Andre McCurdy
2019-11-20 21:29       ` Ryan Harkin
2019-11-20 22:41         ` Ryan Harkin
2019-11-20 23:53           ` Andre McCurdy
2019-11-21  8:05             ` Mikko.Rapeli [this message]
2019-11-22  1:12               ` Ross Burton
2019-11-21 13:15             ` Ryan Harkin
2019-11-21 13:38               ` Nicolas Dechesne
2019-11-21 13:53                 ` Ryan Harkin
2019-11-22  0:11                   ` Andre McCurdy
2019-11-20 21:39 ` Mikko.Rapeli
2019-11-20 23:05   ` Adrian Bunk
2019-11-21  8:01     ` Mikko.Rapeli

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=20191121080503.GC3527@hiutale \
    --to=mikko.rapeli@bmw.de \
    --cc=armccurdy@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox