public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Barker <paul@pbarker.dev>
To: openembedded-core@lists.openembedded.org
Cc: Paul Barker <paul@pbarker.dev>
Subject: [PATCH v2 2/8] curl: Drop arch dependent search paths
Date: Thu, 19 Mar 2026 16:04:40 +0000	[thread overview]
Message-ID: <20260319-fix-checklayer-2-v2-2-38ffe8df4c28@pbarker.dev> (raw)
In-Reply-To: <20260319-fix-checklayer-2-v2-0-38ffe8df4c28@pbarker.dev>

Since the creation of the curl recipe in this repo in 2010, the search
path has been specified relative to STAGING_LIBDIR. This causes the a
dependency from the task hash of do_recipe_qa on baselib, which may be
'lib' or 'lib64' depending on the target architecture. This dependency
trips up yocto-check-layer.

Somewhere between the depths of history and today, the need for this
search path has gone away. Simply using '--with-zlib' now works.

Signed-off-by: Paul Barker <paul@pbarker.dev>
---
 meta/recipes-support/curl/curl_8.19.0.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-support/curl/curl_8.19.0.bb b/meta/recipes-support/curl/curl_8.19.0.bb
index ee9c90846d19..b9251336b8b3 100644
--- a/meta/recipes-support/curl/curl_8.19.0.bb
+++ b/meta/recipes-support/curl/curl_8.19.0.bb
@@ -73,7 +73,7 @@ PACKAGECONFIG[tftp] = "--enable-tftp,--disable-tftp,"
 PACKAGECONFIG[threaded-resolver] = "--enable-threaded-resolver,--disable-threaded-resolver,,,,ares"
 PACKAGECONFIG[verbose] = "--enable-verbose,--disable-verbose"
 PACKAGECONFIG[websockets] = "--enable-websockets,--disable-websockets"
-PACKAGECONFIG[zlib] = "--with-zlib=${STAGING_LIBDIR}/../,--without-zlib,zlib"
+PACKAGECONFIG[zlib] = "--with-zlib,--without-zlib,zlib"
 PACKAGECONFIG[zstd] = "--with-zstd,--without-zstd,zstd"
 
 # Use host certificates for non-target builds. As libcurl doesn't honor any of the env vars (like

-- 
2.43.0



  parent reply	other threads:[~2026-03-19 16:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19 16:04 [PATCH v2 0/8] Further check-layer fixes Paul Barker
2026-03-19 16:04 ` [PATCH v2 1/8] checklayer: Fix regex in get_signatures Paul Barker
2026-03-19 16:04 ` Paul Barker [this message]
2026-03-19 16:04 ` [PATCH v2 3/8] ghostscript: Drop arch dependent search paths Paul Barker
2026-03-19 16:04 ` [PATCH v2 4/8] libssh2: " Paul Barker
2026-03-19 16:04 ` [PATCH v2 5/8] flac: Use arch independent search path Paul Barker
2026-03-19 16:04 ` [PATCH v2 6/8] gettext: Use arch independent search paths Paul Barker
2026-03-19 16:04 ` [PATCH v2 7/8] gnutls: " Paul Barker
2026-03-19 16:04 ` [PATCH v2 8/8] initscripts: Make SRC_URI arch independent Paul Barker
2026-03-21 14:55 ` [OE-core] [PATCH v2 0/8] Further check-layer fixes Peter Kjellerstedt

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=20260319-fix-checklayer-2-v2-2-38ffe8df4c28@pbarker.dev \
    --to=paul@pbarker.dev \
    --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