Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	Mark Hatle <mark.hatle@windriver.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro
Date: Thu, 17 Aug 2017 16:17:32 +0300	[thread overview]
Message-ID: <cdc04bd4-bde2-9e0e-80cb-d93327f7338a@linux.intel.com> (raw)
In-Reply-To: <3d6ca1eb131841adac87ed6bbbe1b769@XBOX02.axis.com>

On 08/17/2017 04:01 PM, Peter Kjellerstedt wrote:

> The problem we have, which caused me to look into this, is:
> 
> We unfortunately have a lot of unversioned libraries, e.g.,
> "libfoo.so" instead of "libfoo.so.1.2.3". There is no problem
> building these (except we need to work around OE's default of
> putting *.so in ${PN}-dev rather than ${PN}). However, when rpm
> creates the packages for the applications linked with these
> libraries, it fails to automatically determine these runtime
> dependencies. However, since there are no errors, what then
> happens is that the image is created, lacking most of our
> libraries, which of course leads to the image failing to boot
> when applications cannot find the libraries they need...

Thanks. The problem with relying on rpm for this discovery is that this 
mechanism is not used anywhere in oe-core. I may update rpm to 4.14 and 
again break this stuff without noticing. I'd say it's better if you fix 
oe-core's code to discover those in the same way versioned libraries are 
discovered.


Alex


  reply	other threads:[~2017-08-17 13:20 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 21:41 [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro Mark Hatle
2017-08-15 21:41 ` [PATCH 1/6 v2] rpm: Add dependencies on bash, perl and python3-core Mark Hatle
2017-08-15 21:41 ` [PATCH 2/6 v2] git: Do not install git cvsserver and git svn by default Mark Hatle
2017-08-15 21:41 ` [PATCH 3/6 v2] texinfo: Avoid a problem with a dependency on perl(Locale::gettext_xs) Mark Hatle
2017-08-15 21:41 ` [PATCH 4/6 v2] package_rpm.bbclass: Filter out unwanted file deps for nativesdk packages Mark Hatle
2017-08-15 21:41 ` [PATCH 5/6 v2] package.bbclass: Restore functionality to detect RPM dependencies Mark Hatle
2017-08-15 21:41 ` [PATCH 6/6 v2] rpm: Disable perl dependency generation Mark Hatle
2017-08-16  5:19 ` [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro akuster808
2017-08-16 13:43   ` Richard Purdie
2017-08-16 20:43     ` Peter Kjellerstedt
2017-08-16 13:34 ` Richard Purdie
2017-08-16 15:18   ` Mark Hatle
2017-08-16 15:37   ` Mark Hatle
2017-08-17 10:53     ` Alexander Kanavin
2017-08-17 13:01       ` Peter Kjellerstedt
2017-08-17 13:17         ` Alexander Kanavin [this message]
2017-08-17 14:41         ` Mark Hatle
2017-08-17 14:37       ` Mark Hatle
2017-08-16 15:32 ` ✗ patchtest: failure for Fix RPM4 regressions based on Pyro (rev2) Patchwork

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=cdc04bd4-bde2-9e0e-80cb-d93327f7338a@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox