initdb errors, postgresql-8.0-beta
============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================
Your name : Murthy
Your email address : smk_va@yahoo.com
System Configuration
---------------------
Architecture (example: Intel Pentium) : Intel PIII
DP
Operating System (example: Linux 2.4.18) : Fedora
Core 2, linux 2.6.8.1 smp
PostgreSQL version (example: PostgreSQL-8.0):
PostgreSQL-8.0 (beta), source downloaded from
ftp3.us.postgresql.org
Compiler used (example: gcc 2.95.2) : gcc 3.3.3
Please enter a FULL description of your problem:
------------------------------------------------
I was able to successfully compile
postogresql-8.0-beta (make check reporteed "Passed all
96 tests"). However, it appears that postresql was
compiled with the wrong value of --pkglibdir: rather
than libdir = $PREFIX/lib it was compiled with libdir
= $PREFIX/bin/lib, but make install put "lib/" in
$PREFIX/lib. This might have been as issue with the
"share/" dir as well as I have to give the -L option
to initdb and ln -s ../lib lib in $PREFIX bin, before
initdb returned success.
HTH,
Murthy
Please describe a way to repeat the problem. Please
try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
If you know how this problem might be fixed, list the
solution below:
---------------------------------------------------------------------
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
S Murthy Kambhampaty <smk_va@yahoo.com> writes:
I was able to successfully compile
postogresql-8.0-beta (make check reporteed "Passed all
96 tests"). However, it appears that postresql was
compiled with the wrong value of --pkglibdir: rather
than libdir = $PREFIX/lib it was compiled with libdir
= $PREFIX/bin/lib, but make install put "lib/" in
$PREFIX/lib.
Did you invoke any of the build steps with a relative path (eg,
"../configure")? There are some known problems in beta1 with
reducing relative paths to absolute. I think this probably
explains your issue, though I did not see that specific misbehavior
while investigating the bug. Should be fixed in beta2.
regards, tom lane
--- Tom Lane <tgl@sss.pgh.pa.us> wrote:Did you invoke any of the build steps with a
relative path (eg,
"../configure")?
Yep.
There are some known problems in
beta1 with
reducing relative paths to absolute. I think this
probably
explains your issue, though I did not see that
specific misbehavior
while investigating the bug. Should be fixed in
beta2.
Thanks, and sorry for the belated response.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com