Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems? - Mailing list pgsql-hackers

From Andrew Chernow
Subject Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems?
Date
Msg-id 4ADCAC76.9070907@esilo.com
Whole thread Raw
In response to Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems?  (u235sentinel <u235sentinel@gmail.com>)
Responses Re: postgres 8.3.8 and Solaris 10_x86 64 bit problems?
List pgsql-hackers
> # ./pg_ctl
> ld.so.1: pg_ctl: fatal: relocation error: R_AMD64_32: file 
> /usr/local/postgres64/lib/libpq.so.5: symbol (unknown): value 
> 0xfffffd7fff1cf210 does not fit
> Killed
> 

"symbol (unknown)".  Can you turn on debugging symbols?  Knowing the 
symbol may point to a library that was not compiled properly.

> So I run 'ldd pg_ctl' to see if everything is linking ok.
> 
> And I'm wondering if there is a problem with libpq.so.5 as mentioned in 
> the original error
> 
> # file /usr/local/postgres64/lib/libpq.so.5
> 
> 
> /usr/local/postgres64/lib/libpq.so.5:   ELF 64-bit LSB dynamic lib AMD64 
> Version 1 [SSE CMOV], dynamically linked, not stripped
> 
> Ok.  So looking good. Maybe there is a library or header libpq needs 
> that I'm missing in 64 bit?
> 
> # ldd /usr/local/postgres64/lib/libpq.so.5

Are you sure that all pg_ctl referenced libraries and all libpq.so 
referenced libraries were built as 64-bit using PIC?  Are you linking 
with any static library that may contain 32-bit objects?  That error is 
most commonly PIC or arch-mismatch.

-- 
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Controlling changes in plpgsql variable resolution
Next
From: Tom Lane
Date:
Subject: Re: Controlling changes in plpgsql variable resolution