From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH next] package/hiawatha: update to 11.6
Date: Tue, 13 Aug 2024 09:19:27 +0200 [thread overview]
Message-ID: <20240813091927.32682ebe@windsurf> (raw)
In-Reply-To: <ZrsED1PkoKznI94O@waldemar-brodkorb.de>
On Tue, 13 Aug 2024 08:58:23 +0200
Waldemar Brodkorb <wbx@openadk.org> wrote:
> > Successful before your bump, fails after your bump.
>
> I only tested with TLS on, sorry.
>
> It seems upstream is broken regarding ENABLE_TLS=OFF.
> I tried to patch CMakeFiles.txt to add the missing sha3.c, but then
> other symbols are missing. I added 5 missing files and still no go.
> Uptream is not very active anymore, he mentions on his website that
> he is doing releases, but no active development anymore.
>
> We could remove TLS off case entirely and still have a small secure
> webserver. What do you think?
Would be OK for me. However, if upstream is not active anymore, should
we drop the package instead?
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:[~2024-08-13 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 5:25 [Buildroot] [PATCH next] package/hiawatha: update to 11.6 Waldemar Brodkorb
2024-08-12 20:14 ` Thomas Petazzoni via buildroot
2024-08-13 6:58 ` Waldemar Brodkorb
2024-08-13 7:19 ` Thomas Petazzoni via buildroot [this message]
2024-08-13 7:23 ` Waldemar Brodkorb
2024-08-13 18:25 ` 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=20240813091927.32682ebe@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@openadk.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 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.