All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: buildroot@buildroot.org, Christian Hitz <christian.hitz@bbv.ch>
Subject: Re: [Buildroot] [PATCH/next v2 1/4] package/libvncserver: bump to version 0.9.15
Date: Sun, 7 Dec 2025 15:27:21 +0100	[thread overview]
Message-ID: <20251207152721.043daf5b@windsurf> (raw)
In-Reply-To: <20251203195640.2297610-1-bernd@kuhls.net>

Hello Bernd, Hello Christian,

Thanks for the patch!

On Wed,  3 Dec 2025 20:56:37 +0100
Bernd Kuhls <bernd@kuhls.net> wrote:

> From: Christian Hitz <christian.hitz@bbv.ch>
> 
> Fixes building with OpenSSL >= 3.0.0.

We have been using OpenSSL >= 3.0.0 in Buildroot for a while, but I
don't seem to see any (recent) libvncserver build issue in our
autobuilders.

Could you clarify this? Is this fixing an actual build issue we are
facing? If not, why?

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

  parent reply	other threads:[~2025-12-07 14:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 19:56 [Buildroot] [PATCH/next v2 1/4] package/libvncserver: bump to version 0.9.15 Bernd Kuhls
2025-12-03 19:56 ` [Buildroot] [PATCH/next v2 2/4] package/libvncserver: enable websocket server Bernd Kuhls
2025-12-03 19:56 ` [Buildroot] [PATCH/next v2 3/4] package/libvncserver: install storepasswd tool Bernd Kuhls
2025-12-03 19:56 ` [Buildroot] [PATCH/next 4/4] package/libvncserver: fix cmake 4 compatibility Bernd Kuhls
2025-12-07 14:28   ` Thomas Petazzoni via buildroot
2025-12-07 14:27 ` Thomas Petazzoni via buildroot [this message]
2025-12-08  7:13   ` [Buildroot] [PATCH/next v2 1/4] package/libvncserver: bump to version 0.9.15 Christian Hitz 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=20251207152721.043daf5b@windsurf \
    --to=buildroot@buildroot.org \
    --cc=bernd@kuhls.net \
    --cc=christian.hitz@bbv.ch \
    --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.