Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: buildroot@buildroot.org
Cc: Alexander Sverdlin <alexander.sverdlin@gmail.com>
Subject: [Buildroot] [PATCH] package/civetweb: fix underlinked shared library
Date: Sun, 30 Aug 2026 20:07:13 +0200	[thread overview]
Message-ID: <20260830180717.96967-1-alexander.sverdlin@gmail.com> (raw)

The install steps re-link libcivetweb.so but do not pass LIBS, so the link
falls back to the upstream Makefile defaults and loses the OpenSSL flags
added by the package. The correctly linked library produced by the build
step is then overwritten by an underlinked one, leaving SSL_CTX_free,
EVP_Digest and friends undefined and breaking any package linking against
-lcivetweb.

Signed-off-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
---
 package/civetweb/civetweb.mk | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/package/civetweb/civetweb.mk b/package/civetweb/civetweb.mk
index af221e9133..4fdd94ecc7 100644
--- a/package/civetweb/civetweb.mk
+++ b/package/civetweb/civetweb.mk
@@ -93,7 +93,7 @@ define CIVETWEB_INSTALL_STAGING_CMDS
 		PREFIX="$(STAGING_DIR)/usr" \
 		$(CIVETWEB_INSTALL_OPTS) \
 		$(CIVETWEB_CONF_OPTS) \
-		COPT='$(CIVETWEB_COPT)'
+		COPT='$(CIVETWEB_COPT)' LIBS="$(CIVETWEB_LIBS)"
 endef
 
 define CIVETWEB_INSTALL_TARGET_CMDS
@@ -102,7 +102,7 @@ define CIVETWEB_INSTALL_TARGET_CMDS
 		PREFIX="$(TARGET_DIR)/usr" \
 		$(CIVETWEB_INSTALL_OPTS) \
 		$(CIVETWEB_CONF_OPTS) \
-		COPT='$(CIVETWEB_COPT)'
+		COPT='$(CIVETWEB_COPT)' LIBS="$(CIVETWEB_LIBS)"
 endef
 
 $(eval $(generic-package))
-- 
2.55.0

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

                 reply	other threads:[~2026-08-30 18:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260830180717.96967-1-alexander.sverdlin@gmail.com \
    --to=alexander.sverdlin@gmail.com \
    --cc=buildroot@buildroot.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