From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Adam Duskett <aduskett@gmail.com>
Cc: Angelo Compagnucci <angelo.compagnucci@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 3/4] package/mender-artifact: bump version to 3.9.0
Date: Thu, 6 Oct 2022 21:42:57 +0200 [thread overview]
Message-ID: <20221006214257.47c453f5@windsurf> (raw)
In-Reply-To: <20221005212150.1384370-3-aduskett@gmail.com>
On Wed, 5 Oct 2022 14:21:49 -0700
Adam Duskett <aduskett@gmail.com> wrote:
> mender-artifact now requires OpenSSL, and is incompatible with OpenSSL3.
> As such, the host-pkgconf and host-libopenssl packages are now dependencies to
> prevent linking errors against OpenSSL3 on newer distributions such as
> Fedora 35.
Even if mender-artifact was compatible with OpenSSL3, it would be a bug
to rely on the system-provided OpenSSL library.
> +# Mender-artifact requires OpenSSL, and is not yet compatible with OpenSSL3.
> +# Mender-artifact also uses pkgconf to find the OpenSSL library.
> +# Use host-pkgconf to force mender-artifact to use Buildroots host-openssl, as
> +# newer distributions, such as Fedora, are starting to use OpenSSL3.
> +HOST_MENDER_ARTIFACT_GO_ENV = \
> + GOFLAGS="-mod=vendor" \
> + PKG_CONFIG_PATH="$(HOST_DIR)/lib/pkgconfig"
Why is -mod=vendor needed here?
Also for pkg-config, I would prefer if we were to use the same
variables as defined in HOST_MAKE_ENV (in package/Makefile.in), i.e:
HOST_MAKE_ENV = \
PATH=$(BR_PATH) \
PKG_CONFIG="$(PKG_CONFIG_HOST_BINARY)" \
PKG_CONFIG_SYSROOT_DIR="/" \
PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 \
PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 \
PKG_CONFIG_LIBDIR="$(HOST_DIR)/lib/pkgconfig:$(HOST_DIR)/share/pkgconfig"
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-10-06 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 21:21 [Buildroot] [PATCH 1/4] package/mender: bump version to 3.4.0 Adam Duskett
2022-10-05 21:21 ` [Buildroot] [PATCH 2/4] package/mender-connect: bump version to 2.1.0 Adam Duskett
2022-10-06 19:41 ` Thomas Petazzoni via buildroot
2022-10-05 21:21 ` [Buildroot] [PATCH 3/4] package/mender-artifact: bump version to 3.9.0 Adam Duskett
2022-10-06 19:42 ` Thomas Petazzoni via buildroot [this message]
2022-10-05 21:21 ` [Buildroot] [PATCH 4/4] package/mender-grubenv: bump version to 2ac898f5924d5870f8394ad8ecd3ef1ab1422e3b Adam Duskett
2022-10-06 19:46 ` Thomas Petazzoni via buildroot
2022-10-06 19:41 ` [Buildroot] [PATCH 1/4] package/mender: bump version to 3.4.0 Thomas Petazzoni via buildroot
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=20221006214257.47c453f5@windsurf \
--to=buildroot@buildroot.org \
--cc=aduskett@gmail.com \
--cc=angelo.compagnucci@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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.