From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libwebsock: Fix openssl reporting in header
Date: Tue, 29 Jan 2019 22:14:21 +0100 [thread overview]
Message-ID: <87ef8v415e.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1548448504-49177-1-git-send-email-clayton.shotwell@rockwellcollins.com> (Clayton Shotwell's message of "Fri, 25 Jan 2019 14:35:04 -0600")
>>>>> "Clayton" == Clayton Shotwell <clayton.shotwell@rockwellcollins.com> writes:
> The websock_config.h file currently ends up being installed into the
> sysroot with a #include "config.h" line but the config.h file does not
> get copied into the sysroot. Refactoring the original patch to have the
> configure script properly report whether or not SSL support is enabled
> without using the config.h file.
> Patch has been submitted upstream but may never be merged.
> https://github.com/payden/libwebsock/pull/38
> Signed-off-by: Clayton Shotwell <clayton.shotwell@rockwellcollins.com>
Committed to 2018.02.x and 2018.11.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-01-29 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 20:35 [Buildroot] [PATCH 1/1] libwebsock: Fix openssl reporting in header Clayton Shotwell
2019-01-25 23:51 ` Arnout Vandecappelle
2019-01-29 21:14 ` Peter Korsgaard [this message]
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=87ef8v415e.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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