-
-
Notifications
You must be signed in to change notification settings - Fork 6.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
curl-wolfssl.m4: error out if wolfSSL is not usable #9682
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When I explicitly declare, that I would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then I would expect, that either I endup with curl having that support, for example in form of https support or it wouldn't be available at all. Downstream projects like for example OpenWrt build curl wolfSSL variant with `--with-wolfssl` already, but in certain corner cases it does fail: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produces curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt/packages#19005 References: openwrt/packages#19547 Signed-off-by: Petr Štetiar <ynezz@true.cz>
ynezz
added a commit
to ynezz/openwrt-packages
that referenced
this pull request
Oct 10, 2022
When we explicitly declare, that we would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then we should make sure, that we either endup with curl having that support, or it shouldn't be available at all, otherwise we risk, that we end up with regressions like following: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produce curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt#19005, openwrt#19547 Upstream-Status: Submitted [curl/curl#9682] Signed-off-by: Petr Štetiar <ynezz@true.cz>
bagder
approved these changes
Oct 10, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Agreed!
Thanks! |
ynezz
added a commit
to ynezz/openwrt-packages
that referenced
this pull request
Oct 10, 2022
When we explicitly declare, that we would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then we should make sure, that we either endup with curl having that support, or it shouldn't be available at all, otherwise we risk, that we end up with regressions like following: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produce curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt#19005, openwrt#19547 Upstream-Status: Accepted [curl/curl#9682] Signed-off-by: Petr Štetiar <ynezz@true.cz>
stangri
pushed a commit
to stangri/packages
that referenced
this pull request
Oct 10, 2022
When we explicitly declare, that we would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then we should make sure, that we either endup with curl having that support, or it shouldn't be available at all, otherwise we risk, that we end up with regressions like following: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produce curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt#19005, openwrt#19547 Upstream-Status: Accepted [curl/curl#9682] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 9140f36)
stangri
pushed a commit
to stangri/packages
that referenced
this pull request
Oct 10, 2022
When we explicitly declare, that we would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then we should make sure, that we either endup with curl having that support, or it shouldn't be available at all, otherwise we risk, that we end up with regressions like following: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produce curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt#19005, openwrt#19547 Upstream-Status: Accepted [curl/curl#9682] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 9140f36)
stangri
pushed a commit
to stangri/packages
that referenced
this pull request
Oct 10, 2022
When we explicitly declare, that we would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then we should make sure, that we either endup with curl having that support, or it shouldn't be available at all, otherwise we risk, that we end up with regressions like following: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produce curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt#19005, openwrt#19547 Upstream-Status: Accepted [curl/curl#9682] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 9140f36)
stangri
pushed a commit
to stangri/packages
that referenced
this pull request
Oct 10, 2022
When we explicitly declare, that we would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then we should make sure, that we either endup with curl having that support, or it shouldn't be available at all, otherwise we risk, that we end up with regressions like following: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produce curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt#19005, openwrt#19547 Upstream-Status: Accepted [curl/curl#9682] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 9140f36)
obonaventure
pushed a commit
to mptcp-apps/curl
that referenced
this pull request
Oct 12, 2022
When I explicitly declare, that I would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then I would expect, that either I endup with curl having that support, for example in form of https support or it wouldn't be available at all. Downstream projects like for example OpenWrt build curl wolfSSL variant with `--with-wolfssl` already, but in certain corner cases it does fail: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produces curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt/packages#19005 References: openwrt/packages#19547 Signed-off-by: Petr Štetiar <ynezz@true.cz> Closes curl#9682
stangri
added a commit
to stangri/packages
that referenced
this pull request
Oct 30, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL Signed-off-by: Stan Grishin <stangri@melmac.ca>
stangri
added a commit
to stangri/packages
that referenced
this pull request
Oct 30, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL Signed-off-by: Stan Grishin <stangri@melmac.ca>
stangri
added a commit
to stangri/packages
that referenced
this pull request
Oct 30, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
stangri
added a commit
to stangri/packages
that referenced
this pull request
Oct 30, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
stangri
added a commit
to stangri/packages
that referenced
this pull request
Oct 30, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca> (cherry picked from commit 88009b2)
sch-m
pushed a commit
to TDT-AG/packages
that referenced
this pull request
Oct 31, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
stangri
added a commit
to stangri/packages
that referenced
this pull request
Nov 3, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca> (cherry picked from commit 88009b2)
anatolio-deb
pushed a commit
to forestvpn/packages
that referenced
this pull request
Nov 11, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
1582130940
pushed a commit
to 1582130940/OpenWrt-Lean-Packages
that referenced
this pull request
Nov 18, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
1582130940
pushed a commit
to 1582130940/OpenWrt-Lean-Packages
that referenced
this pull request
Nov 18, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
roaldclark
pushed a commit
to qculug/openwrt-packages
that referenced
this pull request
Nov 21, 2022
When we explicitly declare, that we would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then we should make sure, that we either endup with curl having that support, or it shouldn't be available at all, otherwise we risk, that we end up with regressions like following: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produce curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt#19005, openwrt#19547 Upstream-Status: Accepted [curl/curl#9682] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 9140f36)
alexeys85
pushed a commit
to alexeys85/packages
that referenced
this pull request
Nov 23, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
stokito
pushed a commit
to stokito/packages
that referenced
this pull request
Dec 6, 2022
When we explicitly declare, that we would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then we should make sure, that we either endup with curl having that support, or it shouldn't be available at all, otherwise we risk, that we end up with regressions like following: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produce curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt#19005, openwrt#19547 Upstream-Status: Accepted [curl/curl#9682] Signed-off-by: Petr Štetiar <ynezz@true.cz>
stokito
pushed a commit
to stokito/packages
that referenced
this pull request
Dec 6, 2022
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
SibrenVasse
pushed a commit
to SibrenVasse/packages
that referenced
this pull request
Feb 26, 2023
When we explicitly declare, that we would like to have curl built with wolfSSL support using `--with-wolfssl` configure option, then we should make sure, that we either endup with curl having that support, or it shouldn't be available at all, otherwise we risk, that we end up with regressions like following: configure:25299: checking for wolfSSL_Init in -lwolfssl configure:25321: x86_64-openwrt-linux-musl-gcc -o conftest [snip] In file included from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/dsa.h:33, from target-x86_64_musl/usr/include/wolfssl/wolfcrypt/asn_public.h:35, from target-x86_64_musl/usr/include/wolfssl/ssl.h:35, from conftest.c:47: target-x86_64_musl/usr/include/wolfssl/wolfcrypt/integer.h:37:14: fatal error: wolfssl/wolfcrypt/sp_int.h: No such file or directory #include <wolfssl/wolfcrypt/sp_int.h> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. and in the end thus produce curl without https support: curl: (1) Protocol "https" not supported or disabled in libcurl So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case: checking for wolfSSL_Init in -lwolfssl... no configure: error: --with-wolfssl but wolfSSL was not found or doesn't work References: openwrt#19005, openwrt#19547 Upstream-Status: Accepted [curl/curl#9682] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 9140f36)
SibrenVasse
pushed a commit
to SibrenVasse/packages
that referenced
this pull request
Feb 26, 2023
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca> (cherry picked from commit 88009b2)
Tom-Keddie
pushed a commit
to violetatrium/openwrt-packages-minimos
that referenced
this pull request
Mar 17, 2023
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
Tom-Keddie
pushed a commit
to violetatrium/openwrt-packages-minimos
that referenced
this pull request
Mar 17, 2023
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
Beginner-Go
pushed a commit
to coolsnowwolf/packages
that referenced
this pull request
Mar 30, 2023
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
Tom-Keddie
pushed a commit
to violetatrium/openwrt-packages-minimos
that referenced
this pull request
Apr 11, 2023
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
Tom-Keddie
pushed a commit
to violetatrium/openwrt-packages-minimos
that referenced
this pull request
Apr 11, 2023
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
ineedfat
pushed a commit
to ineedfat/rockchip_rk3568_openwrt_packages
that referenced
this pull request
Jun 7, 2024
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
ineedfat
pushed a commit
to ineedfat/rockchip_rk3568_openwrt_packages
that referenced
this pull request
Jun 7, 2024
* update to 7.86.0: https://curl.se/changes.html#7_86_0 * remove 300-curl-wolfssl.m4-error-out-if-wolfSSL-is-not-usable.patch as it was fixed upstream: curl/curl#9682 * update configure options for OpenSSL as --without-ssl is breaking build * remove --without-libidn configure arg as it's no longer recognized Signed-off-by: Stan Grishin <stangri@melmac.ca>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When I explicitly declare, that I would like to have curl built with wolfSSL support using
--with-wolfssl
configure option, then I would expect, that either I endup with curl having that support, for example in form of https support or it wouldn't be available at all.Downstream projects like for example OpenWrt build curl wolfSSL variant with
--with-wolfssl
already, but in certain corner cases it does fail:and in the end thus produces curl without https support:
So fix it, by making the working wolfSSL mandatory and error out in configure step when that's not the case:
References: openwrt/packages#19005
References: openwrt/packages#19547
Signed-off-by: Petr Štetiar ynezz@true.cz