mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Effert Sascha (CM/EBV3)" <Sascha.Effert@se.bosch.com>
To: Alexander Dahl <ada@thorsis.com>,
	"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] curl does not compile with SSL support
Date: Mon, 23 Mar 2020 10:48:59 +0000	[thread overview]
Message-ID: <5999b0e6ebfa421d924d4c3e028fe73b@se.bosch.com> (raw)
In-Reply-To: <2263958.67Rj0McoCF@ada>

Hello Alexander,

I replaced libcurl.in and libcurl.make with the actual master containing that commit. But it ends up with the same error.

Even before ptxdist has set --with-default-ssl-backend=ssl already. I printed out all parameters passed to configure and I got following call (sorry, it is quite long):

configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --libdir=/usr/lib --build=x86_64-host-linux-gnu --host=arm-v7a-linux-gnueabihf --disable-debug --enable-optimize --disable-warnings --disable-werror --disable-curldebug --enable-symbol-hiding --enable-hidden-symbols --disable-ares --enable-rt --disable-code-coverage --enable-largefile --enable-http --enable-ftp --disable-file --disable-ldap --disable-ldaps --disable-rtsp --enable-proxy --disable-dict --disable-telnet --disable-tftp --disable-pop3 --disable-imap --disable-smb --disable-smtp --disable-gopher --disable-manual --enable-libcurl-option --disable-libgcc --disable-ipv6 --enable-openssl-auto-load-config --disable-versioned-symbols --enable-threaded-resolver --enable-pthreads --disable-verbose --disable-sspi --disable-crypto-auth --disable-ntlm-wb --enable-tls-srp --enable-unix-sockets --disable-cookies --enable-http-auth --disable-doh --disable-mime --enable-dateparse --enable-netrc --enable-progress-meter --disable-dnsshuffle --disable-alt-svc --with-zlib=/home/vagrant/repositories/DAIMLER_CTP_19.01.S.033/platform/bsp/daimler_ctp/platform-acup/sysroot-target --without-brotli --without-gssapi --with-default-ssl-backend=ssl --without-winssl --without-schannel --without-darwinssl --without-secure-transport --without-amissl --with-ssl=/home/vagrant/repositories/DAIMLER_CTP_19.01.S.033/platform/bsp/daimler_ctp/platform-acup/sysroot-target/usr --with-random=/dev/urandom --without-gnutls --without-mbedtls --without-cyassl --without-wolfssl --without-mesalink --without-nss --with-ca-bundle=/etc/ssl/certs/ca-certificates.crt --with-ca-path=no --without-ca-fallback --without-libpsl --without-libmetalink --without-libssh2 --without-libssh --without-librtmp --without-winidn --without-libidn2 --without-nghttp2 --without-zsh-functions-dir --without-fish-functions-dir

Mit freundlichen Grüßen / Best regards

 Sascha Effert

Car Multimedia, Engineering BBM   CM VC 3 (CM/EBV3)
Robert Bosch GmbH | Postfach | 31132 Hildesheim | GERMANY | www.bosch.com
Tel. +49 5121 49-4512 | Mobil +49 1522 2560174 | Sascha.Effert@se.bosch.com

Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HRB 14000;
Aufsichtsratsvorsitzender: Franz Fehrenbach; Geschäftsführung: Dr. Volkmar Denner, 
Prof. Dr. Stefan Asenkerschbaumer, Dr. Michael Bolle, Dr. Christian Fischer, Dr. Stefan Hartung,<br/>Dr. Markus Heyn, Harald Kröger, Christoph Kübel, Rolf Najork, Uwe Raschke, Peter Tyroller


-----Ursprüngliche Nachricht-----
Von: Alexander Dahl <ada@thorsis.com> 
Gesendet: Montag, 23. März 2020 11:01
An: ptxdist@pengutronix.de
Cc: Effert Sascha (CM/EBV3) <Sascha.Effert@se.bosch.com>
Betreff: Re: [ptxdist] curl does not compile with SSL support

Hello Sascha,

Am Montag, 23. März 2020, 09:35:58 CET schrieb Effert Sascha (CM/EBV3):
> Hi,
> 
> I am using ptxdist 2019.01.0 in a project. In the project we currently 
> use libcurl without SSL support. I changesd this using menuconfig, so 
> libcurl should now compile with http, ftp and ssl support (use ca-certificates).
> Openssl is also available. Compiling fails thereafter in target 
> libcurl.prepare with following error:
 
> checking for OpenSSL headers version... 1.0.2 - 0x1000211fL checking 
> for OpenSSL library version... 1.0.2 checking for OpenSSL headers and 
> library versions matching... yes checking for SRP_Calc_client_key in 
> -lcrypto... yes
> configure: built with one SSL backend
> configure: error: Default SSL backend ssl not enabled!
> /usr/local/lib/ptxdist-2019.01.0/rules/post/ptxd_make_world_prepare.make:21:
> recipe for target
> '/home/vagrant/repositories/DAIMLER_CTP_19.01.S.033/platform/bsp/daiml
> er_ct p/platform-acup/state/libcurl.prepare' failed
 make: ***
> [/home/vagrant/repositories/DAIMLER_CTP_19.01.S.033/platform/bsp/daiml
> er_ct p/platform-acup/state/libcurl.prepare] Error 1
> 
> 
> Can someone give me a hint what I can do? I searched google and the 
> mailing list, but without any success. To give more information here 
> the output of configure regarding SSL:

I would try looking at changes to rules/libcurl.* in later versions of ptxdist. This commit looks promising: 0d75d1ce80e3e8f5fe66934c0b945e4aad53c45b

 
> 
> checking if GSS-API support is requested... no checking whether to 
> enable Windows native SSL/TLS (Windows native builds only)... no
 checking whether to enable Secure Transport... no
> checking whether to enable Amiga native SSL/TLS (AmiSSL)... no
> configure: PKG_CONFIG_LIBDIR will be set to 
> "/home/vagrant/repositories/DAIMLER_CTP_19.01.S.033/platform/bsp/daiml
> er_ct p/platform-acup/sysroot-target/usr/lib/pkgconfig"
 checking for openssl
> options with pkg-config... found
> configure: pkg-config: SSL_LIBS: "-lssl -lcrypto"
> configure: pkg-config: SSL_LDFLAGS: ""
> configure: pkg-config: SSL_CPPFLAGS: ""
> checking for HMAC_Update in -lcrypto... yes checking for SSL_connect 
> in -lssl... yes checking openssl/x509.h usability... yes checking 
> openssl/x509.h presence... yes checking for openssl/x509.h... yes 
> checking openssl/rsa.h usability... yes checking openssl/rsa.h 
> presence... yes checking for openssl/rsa.h... yes checking 
> openssl/crypto.h usability... yes checking openssl/crypto.h 
> presence... yes checking for openssl/crypto.h... yes checking 
> openssl/pem.h usability... yes checking openssl/pem.h presence... yes 
> checking for openssl/pem.h... yes checking openssl/ssl.h usability... 
> yes checking openssl/ssl.h presence... yes checking for 
> openssl/ssl.h... yes checking openssl/err.h usability... yes checking 
> openssl/err.h presence... yes checking for openssl/err.h... yes 
> checking for RAND_egd... yes checking for SSLv2_client_method... yes 
> checking for OpenSSL_version... no checking for BoringSSL... no 
> checking for libressl... no checking for OpenSSL headers version... 
> 1.0.2 - 0x1000211fL checking for OpenSSL library version... 1.0.2 
> checking for OpenSSL headers and library versions matching... yes 
> checking for SRP_Calc_client_key in -lcrypto... yes
> configure: built with one SSL backend
> configure: error: Default SSL backend ssl not enabled!
> make: ***
> [/home/vagrant/repositories/DAIMLER_CTP_19.01.S.033/platform/bsp/daiml
> er_ct p/platform-acup/state/libcurl.prepare] Error 1
> /usr/local/lib/ptxdist-2019.01.0/rules/post/ptxd_make_world_prepare.ma
> ke:21
> : recipe for target
> '/home/vagrant/repositories/DAIMLER_CTP_19.01.S.033/platform/bsp/daiml
> er_ct p/platform-acup/state/libcurl.prepare' failed

Same error as above. Perhaps curl needs to have --with-default-ssl-backend= passed to ./configure ?

HTH & Greets
Alex


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2020-03-23 10:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23  9:35 Effert Sascha (CM/EBV3)
2020-03-23 10:01 ` Alexander Dahl
2020-03-23 10:48   ` Effert Sascha (CM/EBV3) [this message]
2020-03-24  6:51     ` Michael Olbrich

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=5999b0e6ebfa421d924d4c3e028fe73b@se.bosch.com \
    --to=sascha.effert@se.bosch.com \
    --cc=ada@thorsis.com \
    --cc=ptxdist@pengutronix.de \
    /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