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

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: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 Thu, 2016-08-04 at 09:46 -0400, James B. Byrne wrote: > 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

Processing Conflict: speexdsp-1.2-0.9.rc3.el6.x86_64 conflicts speex <= 1.2-0.21.rc1 I am loath to replace things on my primary workstation as I have far too much to do as it is without dealing with self-inflicted injuries. However, I do use Jitsi as a softphone and the latest version has a dependency on a package in EPEL which replaces something from the base distro. Can someone inform me

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

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

Question: If I use mock to build package rpmA from tarballA but rpmA has a dependency that can only be satisfied by package rpmB which must also be built from tarballB then how does the rpmB built from the tarballB get pulled into mock when building rpmA? I am trying to build httpd-2.4.7 from Apache and that needs apr-devel and apr-util-devel > 1.4. I can build apr and apr-utils in mock but

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 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 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

I'm having a major frustration with curl. When building curl, if libssl.so.10 is present the curl binary WILL link against it. If curl is configured with an ssl option - the library WILL link against it. If you change the curl configuration options to use a different TLS library (e.g. nss like CentOS does) the curl binary and library will still link against the OpenSSL library.

I am trying to build an rpm package for iaxmodem-1.2.0. At the moment I am still trying to get a working spec file put together. I have managed to get an SRPM produced but the binary build from this fails due to there being no install task in the Makefile.in provided with the source. I have found a spec file from opensuse that provides this in the install portion: %build [

On Fri, February 13, 2015 12:52, Les Mikesell wrote: > On Fri, Feb 13, 2015 at 11:39 AM, Valeri Galtsev > <galtsev at kicp.uchicago.edu> wrote: >> >>> Otherwise it accept junk that your primary rejects >> >> Not exactly. If greylisting on primary is set, but on backup MX >> is not, still what is killed by greylisting by primary MX, >> almost

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: > 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

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

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 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.

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 Tue, March 31, 2009 13:03, James B. Byrne wrote: > Found it. No etc/at.allow and no etc/at.deny means only root can > submit jobs. > Well, that was not it. I still get the same errors after adding my user id to /etc/at.allow. I tested whether job control was enabled by moving top into the background using ctrl-z and fg to return and that worked. Any suggestions as to what I am