similar to: curl build system is broken and so is mock

On 08/03/2016 05:33 PM, Thomas Eriksson wrote: > On 08/03/2016 05:23 PM, Alice Wonder wrote: >> On 08/03/2016 05:20 PM, Alice Wonder wrote: >>> On 08/03/2016 05:11 PM, Alice Wonder wrote: >>>> I'm having a major frustration with curl. >>>> >>>> When building curl, if libssl.so.10 is present the curl binary WILL link >>>> against

On 08/03/2016 05:54 PM, Alice Wonder wrote: > On 08/03/2016 05:45 PM, Alice Wonder wrote: >> On 08/03/2016 05:33 PM, Thomas Eriksson wrote: >>> On 08/03/2016 05:23 PM, Alice Wonder wrote: >>>> On 08/03/2016 05:20 PM, Alice Wonder wrote: >>>>> On 08/03/2016 05:11 PM, Alice Wonder wrote: >>>>>> I'm having a major frustration with

On 08/03/2016 06:40 PM, Chris Adams wrote: > Once upon a time, Alice Wonder <alice at domblogger.net> said: >> [alice at pern root]$ ldd builddir/build/BUILDROOT/curl-7.29.0-26.el7_2.awel.libre.0.x86_64/usr/bin/curl >> |grep crypto >> libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007fb6e00a5000) >> libcrypto.so.10 => /lib64/libcrypto.so.10

On 08/03/2016 05:20 PM, Alice Wonder wrote: > On 08/03/2016 05:11 PM, Alice Wonder wrote: >> I'm having a major frustration with curl. >> >> When building curl, if libssl.so.10 is present the curl binary WILL link >> against it. > > *snip* > > Go ahead and ldd on the CentOS curl binary and library - you will see > openssl linked even though the spec

On 08/03/2016 06:13 PM, Chris Adams wrote: > Once upon a time, Alice Wonder <alice at domblogger.net> said: >> Something in the curl build will always link the binary against >> OpenSSL if the openssl-lib package is present, and will always link >> the library against OpenSSL if any TLS option is enabled in the >> configure. > > No, it doesn't. You can

On 08/03/2016 05:45 PM, Alice Wonder wrote: > On 08/03/2016 05:33 PM, Thomas Eriksson wrote: >> On 08/03/2016 05:23 PM, Alice Wonder wrote: >>> On 08/03/2016 05:20 PM, Alice Wonder wrote: >>>> On 08/03/2016 05:11 PM, Alice Wonder wrote: >>>>> I'm having a major frustration with curl. >>>>> >>>>> When building curl, if

On 08/03/2016 06:57 PM, Chris Adams wrote: > Once upon a time, Alice Wonder <alice at domblogger.net> said: >> So when building curl, it links curl against the libcurl in the >> buildroot and not against the libcurl it just compiled? >> >> No other packages I know of do that. > > No, that is not what it does. If you posted the full ldd output like I >

On 08/03/2016 06:30 PM, Chris Adams wrote: > Once upon a time, Alice Wonder <alice at domblogger.net> said: >> [alice at pern ~]$ ldd /usr/bin/curl |grep crypto >> libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f4524390000) >> libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f45234ca000) > > What do the following show: > > ldd /usr/bin/curl

Once upon a time, Alice Wonder <alice at domblogger.net> said: > So when building curl, it links curl against the libcurl in the > buildroot and not against the libcurl it just compiled? > > No other packages I know of do that. No, that is not what it does. If you posted the full ldd output like I asked, rather than grepping out bits, you'd see it loading the system

Once upon a time, Alice Wonder <alice at domblogger.net> said: > Something in the curl build will always link the binary against > OpenSSL if the openssl-lib package is present, and will always link > the library against OpenSSL if any TLS option is enabled in the > configure. No, it doesn't. You can see this by looking at the RPM dependencies; at least on CentOS 7 and

On 08/03/2016 05:23 PM, Alice Wonder wrote: > On 08/03/2016 05:20 PM, Alice Wonder wrote: >> On 08/03/2016 05:11 PM, Alice Wonder wrote: >>> I'm having a major frustration with curl. >>> >>> When building curl, if libssl.so.10 is present the curl binary WILL link >>> against it. >> >> *snip* >> >> Go ahead and ldd on the

On 08/03/2016 05:11 PM, Alice Wonder wrote: > I'm having a major frustration with curl. > > When building curl, if libssl.so.10 is present the curl binary WILL link > against it. *snip* Go ahead and ldd on the CentOS curl binary and library - you will see openssl linked even though the spec file has --disable-ssl and --enable-nss It's clearly broken.

Once upon a time, Alice Wonder <alice at domblogger.net> said: > [alice at pern ~]$ ldd /usr/bin/curl |grep crypto > libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f4524390000) > libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007f45234ca000) What do the following show: ldd /usr/bin/curl ldd /usr/lib64/libcurl.so.4 ldd /usr/lib64/libssh2.so.1 I can only guess

Once upon a time, Alice Wonder <alice at domblogger.net> said: > [alice at pern root]$ ldd builddir/build/BUILDROOT/curl-7.29.0-26.el7_2.awel.libre.0.x86_64/usr/bin/curl > |grep crypto > libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007fb6e00a5000) > libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007fb6df3e8000) Here is your problem - unless you specify an

On Wed, August 3, 2016 22:53, Alice Wonder wrote: > > I didn't realize ldd was recursive. I may have known that at one > point (been using linux since MK Linux DR3 and building RPMs since > 1999), but have a head injury results in memory problems with > pieces of knowledge I don't frequently use. Most of us have that problem; head injuries or not. -- *** e-Mail

> it doesn't do anything with ssl, however it depends on curl for YP and > that can have a dependency on ssl. Either install the ssl lib or > install curl without ssl support. hmmm :-/ ... I'm sure, I've installed the sslib already. How is the name of that file? libssl.a? Did you know the standard location, where to place it? Is it /usr/lib? Greetings Tol <p>---

Hi All. In curl manual: --ciphers -> "(SSL) Specifies which ciphers to use in the connection. The list of ciphers must specify valid ciphers. Read up on SSL cipher list details on this URL:http://www.openssl.org/docs/apps/ciphers.html" In openssl: http://www.openssl.org/docs/apps/ciphers.html#CIPHER_SUITE_NAMES there are names such as "SSL_RSA_WITH_RC4_128_SHA RC4-SHA" but

On Sat, May 30, 2020 at 11:32 PM G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: [...] > Btw. why does this affect openssl? That root cert was published in > 2010, surely openssl should know about it? Maybe libcurl / openssl > only uses the chain provided by the server? Without trying to use an > alternate chain? Yes, indeed it seems that old OpenSSL versions cannot handle

Odd: I just pulled SVN and compiled.. Wonderful new logging code, btw! Now, why in the WORLD would the resolution be failling?! nsswitch.conf / resolv.conf / hosts is all fine.. *shrug* I can obviously put IPs instead of hosts in the URLs, however things still fail.. -- Chris Pickert ldd output-- ldd ./icecast libcurl.so.2 => /usr/lib/libcurl.so.2 (0x4001f000)

Was this resolved upstream or is this something that R should/could fix? If the latter, could this also go into the "emergency release" R 4.0.2 that is scheduled for 2020-06-22? My $.02 /Henrik On Sun, May 31, 2020 at 8:13 AM G?bor Cs?rdi <csardi.gabor at gmail.com> wrote: > > Btw. it would be also possible to create a macOS R installer that > embeds a static or