All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Heiko Thiery" <heiko.thiery@gmail.com>,
	"Jan Kundrát" <jan.kundrat@cesnet.cz>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libnetconf2: doesn't build with libressl
Date: Sun, 12 Jun 2022 17:50:43 +0200	[thread overview]
Message-ID: <20220612155043.GG427639@scaer> (raw)
In-Reply-To: <20220611145715.879538-1-fontaine.fabrice@gmail.com>

Fabrice, All,

On 2022-06-11 16:57 +0200, Fabrice Fontaine spake thusly:
> libnetconf2 doesn't build with libressl which doesn't provide
> X509_STORE_CTX_get1_certs resulting in the following build failure with
> netopeer2:
> 
> [100%] Linking C executable netopeer2-server
> /home/buildroot/autobuild/instance-3/output-1/host/opt/ext-toolchain/bin/../lib/gcc/microblaze-buildroot-linux-gnu/11.2.0/../../../../microblaze-buildroot-linux-gnu/bin/ld: /home/buildroot/autobuild/instance-3/output-1/host/microblaze-buildroot-linux-gnu/sysroot/usr/lib/libnetconf2.so: undefined reference to `X509_STORE_CTX_get1_certs'
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/7f9a114a477e859dfbc62a53ab66c58eddb2318b
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/libnetconf2/libnetconf2.mk | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/libnetconf2/libnetconf2.mk b/package/libnetconf2/libnetconf2.mk
> index 11a1995ea1..00d2c08f63 100644
> --- a/package/libnetconf2/libnetconf2.mk
> +++ b/package/libnetconf2/libnetconf2.mk
> @@ -23,7 +23,7 @@ else
>  LIBNETCONF2_CONF_OPTS += -DENABLE_SSH=OFF
>  endif
>  
> -ifeq ($(BR2_PACKAGE_OPENSSL), y)
> +ifeq ($(BR2_PACKAGE_LIBOPENSSL), y)

I was wondering if libnetconf2 should instead just select
BR2_PACKAGE_OPENSSL_FORCE_LIBOPENSSL so that it is obvious in the
menuconfig.

I mena, by selecting BR2_PACKAGE_OPENSSL_FORCE_LIBOPENSSL, a user who
enables openssl will see that libressl is not availble, while with your
solution, openssl is enabled with libressl, yet libnetconf2 is not built
with ssl support, which can be a bit confusing to some.

Yet, I am not sure what the proper solution is, and I cold not find a
precedent either way. So, applied to master, thanks.

Regards,
Yann E. MORIN.

>  LIBNETCONF2_CONF_OPTS += -DENABLE_TLS=ON
>  LIBNETCONF2_DEPENDENCIES += openssl
>  else
> -- 
> 2.35.1
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-06-12 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11 14:57 [Buildroot] [PATCH 1/1] package/libnetconf2: doesn't build with libressl Fabrice Fontaine
2022-06-12 15:50 ` Yann E. MORIN [this message]
2022-06-19 13:37 ` Peter Korsgaard

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=20220612155043.GG427639@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=heiko.thiery@gmail.com \
    --cc=jan.kundrat@cesnet.cz \
    /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.