curl / Mailing Lists / curl-library / Single Mail


RE: Need to build 32-bit curl on RH Linux 64-bit

From: Robert Sorrells via curl-library <>
Date: Wed, 13 Mar 2019 19:21:56 +0000

Thank you, sir.

I have done everything EXCEPT play with /etc/, which I do not have permission to do. Regardless of whether I use the Intel 32-bit compiler, or gcc with "-m32" flag, GNU "ld" always searches /lib64 and /usr/lib64 first, and rejects incompatible libraries for libssl, libldap, libz and librt. I can fiddle with the command lines in my own separate little scripts and make it work, but "configure" (nicely) builds and attempts compilation of all of these executables. Unfortunately there does not appear to be any environmental variable that will override the search path chosen by "ld".

I found an RHEL6 "rpm" file at the curl download site which hopefully contains 32-bit binary curl libs. I'm trying to get my SA to install it.

Thanks again.

Bob Sorrells
Amdocs IT Services, LLC

-----Original Message-----
From: Daniel Stenberg <>
Sent: Wednesday, March 13, 2019 3:30 AM
To: Robert Sorrells via curl-library <>
Cc: Robert Sorrells <>
Subject: Re: Need to build 32-bit curl on RH Linux 64-bit

On Tue, 12 Mar 2019, Robert Sorrells via curl-library wrote:

> If it isn't possible for a public 64-bit and a private 32-bit version
> to coexist, let me know.

It's certainly possible.

You can build and install any amount of separate curl versions/builds. A build doesn't need nor use any current installation and won't even know its there.

> Or maybe I need to override some pkg-config stuff when I build my
> private version.

Well, if you're not doing a cross-compiled build, the configure script will use pkg-config in order to find and use dependencies in your system. If those are not dependencies you like, then you need to point configure to other ones or disable the use of them.

You can set PKG_CONFIG_PATH to point to a specific directory for where your pkg-config meta data is, you can use --disable-* and --without-* options to configure or you can point out

> If I play with the above environmental variables, I can get around the
> time_t error, but then it always aborts at the "check for runtime"
> section of configure.

That's when the configure script verifies if it can actually run an executable linked to the specified libraries. You can probably fix that by editing /etc/, setting LD_LIBRARY_PATH or adding more LDFLAGS to "hardcode"
library paths into the executable.

This email and the information contained herein is proprietary and confidential and subject to the Amdocs Email Terms of Service, which you may review at <>
Received on 2019-03-13