From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | vodhner(at)cox(dot)net |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Pgsql on Solaris |
Date: | 2006-11-01 08:53:29 |
Message-ID: | 45486089.3090507@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
vodhner(at)cox(dot)net wrote:
> Thanks to all who replied.
>
> The reason I wanted to go 64-bit on our Fujitsu sparc-alikes was that
> our sysadmins switched to 64-bit Perl as part of the standard
> package, and that broke our DBD::Pg interface. With no warning, we
> started getting a message about Pg.so, "Wrong ELF Class:
> ELFCLASS32".
>
> My assumption had been that 64-bit was the latest and greatest, so of
> course config should have found the appropriate libraries etc. and
> set me up for a 64-bit make. The answer to my question seems to be
> yes, I could cause 64-bit compilation, but it's not the obvious way
> to go.
You only need the client libraries as 64-bit for this particular problem
. Of course, if server and client are on the same machine then it's
probably simpler to have everything the same.
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2006-11-01 09:03:53 | Re: Trouble with plpgsql generic trigger function using |
Previous Message | Richard Huxton | 2006-11-01 08:45:28 | Re: Compiling/Installing as a non-admin user |