Re: 7.4beta4: make check broken?

From: ljb <ljb220(at)mindspring(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: 7.4beta4: make check broken?
Date: 2003-10-07 01:47:50
Message-ID: blt606$pe0$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support pgsql-bugs

tgl(at)sss(dot)pgh(dot)pa(dot)us wrote:
> ljb <ljb220(at)mindspring(dot)com> writes:
>> I got the same error with beta1, but the symbol was "get_progname"
>> not "get_proname". Perhaps the above is a typo.
>
> "get_progname" would make sense, because that's a symbol defined in
> libpgport in 7.4 that did not exist in 7.3. So if the dynamic linker
> was finding your 7.3 PG library directory instead of 7.4, you'd likely
> get this error.

Confirmed. Perhaps this should be looked into. On my system, "make check"
works fine if there is no existing PostgreSQL installation. But if there
is, we seem to prefer the existing installation's libraries over what
pg_regress sets LD_LIBRARY_PATH to (the newly built software). This means
that "make check" will either fail in createdb (if the existing install is
7.3, for example) or work but actually be testing the newly built programs
using the existing version's run-time libpq library.

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Tom Lane 2003-10-07 04:01:58 Re: 7.4beta4: make check broken?
Previous Message attilio drei 2003-10-07 01:36:07 Os x link problem

Browse pgsql-bugs by date

  From Date Subject
Next Message Ara Anjargolian 2003-10-07 03:34:08 Odd Foreign Key Bug
Previous Message Tom Lane 2003-10-06 20:10:27 Re: Domain Implicit Casting Trouble