Postgres Pro
Downloads
Home   >   mailing lists

Thread: libssl issue ?

libssl issue ?

From
Peter Roethlisberger
Date:
I was able to configure Postgres Version 8.4.4. Now when I execute the make I get the following:

/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/bin/ld: /usr/local/openssl/lib64/libssl.a(t1_meth.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC
/usr/local/openssl/lib64/libssl.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[3]: *** [libpq.so.5.2] Error 1
make[3]: Leaving directory `/tmp/postgresql-8.4.4/src/interfaces/libpq'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/tmp/postgresql-8.4.4/src/interfaces'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/postgresql-8.4.4/src'
make: *** [all] Error 2


Thansk: Peter

Re: libssl issue ?

From
Craig Ringer
Date:
On 16/09/2010 4:35 PM, Peter Roethlisberger wrote:
> I was able to configure Postgres Version 8.4.4. Now when I execute the make
> I get the following:

It would be helpful if you provided a few basic details, like your OS,
compiler & version, configure command line, etc.

You're clearly on some 64-bit SuSE, but that doesn't really tell anybody
much.

> /usr/local/openssl/lib64/libssl.a: could not read symbols: Bad value

Bad build of OpenSSL? What does:

  nm /usr/local/openssl/lib64/libssl.a

say.

--
Craig Ringer

Tech-related writing at http://soapyfrogs.blogspot.com/

Re: libssl issue ?

From
Tom Lane
Date:
Craig Ringer <craig@postnewspapers.com.au> writes:
> On 16/09/2010 4:35 PM, Peter Roethlisberger wrote:
>> /usr/local/openssl/lib64/libssl.a: could not read symbols: Bad value

> Bad build of OpenSSL? What does:

Well, the real question here is why it's not picking up a shared-library
version of libssl instead.  By and large you don't want libpq linking
to a static version of openssl, so even if this configuration worked
it wouldn't be a good thing to do.

I'd get rid of the /usr/local version of openssl and use the
distro-provided one instead.

            regards, tom lane

Re: libssl issue ?

From
Peter Roethlisberger
Date:
Thanks for the input Tom. Compiling openssl with the shared option did the trick.

On Thu, Sep 16, 2010 at 3:49 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Craig Ringer <craig@postnewspapers.com.au> writes:
> On 16/09/2010 4:35 PM, Peter Roethlisberger wrote:
>> /usr/local/openssl/lib64/libssl.a: could not read symbols: Bad value

> Bad build of OpenSSL? What does:

Well, the real question here is why it's not picking up a shared-library
version of libssl instead.  By and large you don't want libpq linking
to a static version of openssl, so even if this configuration worked
it wouldn't be a good thing to do.

I'd get rid of the /usr/local version of openssl and use the
distro-provided one instead.

                       regards, tom lane



--
___________________________________

Peter Roethlisberger
Suldhaltenstrasse 4
3703 Aeschi
Switzerland
46°39'14" N 7°41'47" E

Mobile: +41 (0)79 785 79 35
Fix:      +41 (0)33 654 04 39
Skype:PeterRoethlisberger
peter.roethlisberger@gmail.com
____________________________________