[EMAIL PROTECTED] wrote:
> ljb <[EMAIL PROTECTED]> 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
[EMAIL PROTECTED] wrote:
> Yeah, we have seen this before on various platforms. On some,
> LD_LIBRARY_PATH isn't actually anything the dynamic linker pays
> attention to, and on others, it is trumped by the installation rpath
> built into the executables. Not putting an rpath into the executables
[Using PostgreSQL-7.3.4 and -7.4beta5, Tcl-8.4.x.]
Binary data written to a Large Object with libpgtcl's pg_lo_write is
corrupted. Tcl is mangling the data - something to do with UTF-8
conversion. Example: 0x80 becomes 0xc2 0x80, and 0xff becomes 0xc3 0xbf.
The problem with pg_lo_read is more s
[EMAIL PROTECTED] wrote:
> Wolfgang Drotschmann <[EMAIL PROTECTED]> writes:
>> relocation error:
>> /home/drotschm/.Installation/postgresql-7.4RC2/src/test/regress/./tmp_check/install//PostgreSQL//bin/createdb:
>>
>> undefined symbol: get_progname
>> pg_regress: createdb failed
>
> Hmm. get_pro