All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Squires" <dan@engineeredarts.co.uk>
To: yocto@lists.yoctoproject.org
Subject: host file contamination with recipes using cmake and find_package
Date: Fri, 27 May 2022 08:07:57 -0700	[thread overview]
Message-ID: <VDCD.1653664077949368330.uKFK@lists.yoctoproject.org> (raw)

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

Hi,
We have an internal source tree, I'll call it libA for brevity here, which uses cmake and find_package to build against openssl as follows:

find_package(OpenSSL REQUIRED)

The recipe for this source runs fine but some subsequent ones that depend on it (libB, libC etc) fail on some systems saying that a library file (libcrypto.so.1.1) required by libA cannot be found. Now it seems that the build for libA is managing to find and link against libcrypto.so.1.1 from the host libraries found under /usr. I have seen issues like this many years ago but not experienced any such issues since then until recently.

Do we need to do something special in the recipe to prevent this happening? At first I thought I was going to find some hardcoded  absolute paths in the CMakeLists.txt file of libA as I have in the past but there is nothing like that.

Many Thanks

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

             reply	other threads:[~2022-05-27 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 15:07 Daniel Squires [this message]
2022-05-27 15:23 ` [yocto] host file contamination with recipes using cmake and find_package Mikko.Rapeli
2022-05-27 15:37   ` Daniel Squires
2022-05-27 15:44     ` Mikko.Rapeli
2022-05-31 15:15       ` Daniel Squires

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=VDCD.1653664077949368330.uKFK@lists.yoctoproject.org \
    --to=dan@engineeredarts.co.uk \
    --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.