From: | Brian Macy <bmacy(at)macykids(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Pg 7.2.3 int8 value out of range |
Date: | 2002-10-18 20:49:44 |
Message-ID: | 3DB073E8.5060805@macykids.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Yeah, weird... Steve Dunham narrowed the problem down to libssl and
posted it to the debian-sparc list, Ben Collins, and appended the info
to the postgres bug report. Hopefully it will be resolved for Debian
unstable shortly.
Brian Macy
Tom Lane wrote:
> Brian Macy <bmacy(at)macykids(dot)net> writes:
>
>>The config.log wasn't very useful but I hacked configure to not send
>>compile/run errors to /dev/null and got this:
>
>
>>checking whether long long int is 64 bits... ./conftest: relocation
>>error: ./conftest: undefined symbol: __muldi3
>
>
>>Apparrently something is whacked when running from configure. I can take
>>the exact code (minus the confdefs.h) and run it from the command-line
>>and it compiles, links, and executes fine (returns 0).
>
>
> Bizarre. Did your manual test include the same library options (-lssl
> etcetera) that configure was using?
>
> If memory serves, __muldi3 is a subroutine in libgcc, which ought to be
> automatically included in any link performed by gcc. It seems on this
> evidence that one or more of the libraries being linked is somehow
> interfering with libgcc ... but I'm darned if I see the problem ...
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2002-10-18 22:11:04 | Re: Bug #799: configure does not check for -lodbcinst |
Previous Message | Tom Lane | 2002-10-18 18:59:55 | Re: Pg 7.2.3 int8 value out of range |