Broken source tree

a couple of days ago, the problem you have seen was caused
by a re-naming of the libpq.so shared library (if my memory
doesn't fool me, from libpq.so.1.1 to libpq.so.1). Due
to an old link to the former name, the new shared lib was not
found; removing the link and installing a proper one to the
new library solved the curse...

OK, all entries in the lib directory refer to libpq.so.1 . So where is
the "old link" you are referring to? Do I need to rerun ldconfig??

- Tom

On Wed, 5 Aug 1998, Thomas G. Lockhart wrote:

a couple of days ago, the problem you have seen was caused
by a re-naming of the libpq.so shared library (if my memory
doesn't fool me, from libpq.so.1.1 to libpq.so.1). Due
to an old link to the former name, the new shared lib was not
found; removing the link and installing a proper one to the
new library solved the curse...

OK, all entries in the lib directory refer to libpq.so.1 . So where is
the "old link" you are referring to? Do I need to rerun ldconfig??

I had this Monday evening. I ran ldconfig (with the /usr/local/pgsql/lib
directory in /etc/ld.so.conf), and initdb ran - but it's still failing
about half way through :-(

--
Peter T Mount peter@retep.org.uk or petermount@earthling.net
Main Homepage: http://www.retep.org.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres

I did a CVSup a few minutes ago, and tried to do a clean install.
configure seemed to do the right thing, but initdb was not
happy. Looks

Seems linux users have been experiencing problems with initdb, and I
decided to make another challenge of installing PostgreSQL to my
RedHat 4.0 box from scratch. (I did cvs up a few hours ago). So far no
problem was found.

like (perhaps) the recent changes to initdb to allow non-interactive use

~~~~~~~~~~~~~~~~~~~~~~~~~

might have broken things?

I didn't know about this. Maybe you mean the patches I have sent
recently?

Regarding specific symptoms:
1) libpq.so.1 did get made and is in the right place afaik. Don't know
why pg_id is complaining.

don't know too.

2) initdb has a syntax error in the script.

maybe due to pg_id returning null string?
--
Tatsuo Ishii
t-ishii@sra.co.jp

I did a CVSup a few minutes ago, and tried to do a clean install.
configure seemed to do the right thing, but initdb was not
happy. Looks

Seems linux users have been experiencing problems with initdb, and I
decided to make another challenge of installing PostgreSQL to my
RedHat 4.0 box from scratch. (I did cvs up a few hours ago). So far no
problem was found.

like (perhaps) the recent changes to initdb to allow non-interactive use

~~~~~~~~~~~~~~~~~~~~~~~~~

might have broken things?

I didn't know about this. Maybe you mean the patches I have sent
recently?

Regarding specific symptoms:
1) libpq.so.1 did get made and is in the right place afaik. Don't know
why pg_id is complaining.

don't know too.

2) initdb has a syntax error in the script.

maybe due to pg_id returning null string?
--
Tatsuo Ishii
t-ishii@sra.co.jp

Multi-byte pg_class_mb.h and others had duplicate copies of the file in
them. I am committing a fix now.

As far as I am concerned, if you want to just add the endcoding field to
various tables, go ahead. It is easier than maintaining two copies of
the files, and should make your job easier.

-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

Multi-byte pg_class_mb.h and others had duplicate copies of the file in
them. I am committing a fix now.

Thanks.

As far as I am concerned, if you want to just add the endcoding field to
various tables, go ahead. It is easier than maintaining two copies of
the files, and should make your job easier.

Thanks again! If there's no objection, I will go ahead.
--
Tatsuo Ishii
t-ishii@sra.co.jp

OK, all entries in the lib directory refer to libpq.so.1 . So where
is the "old link" you are referring to? Do I need to rerun
ldconfig??

The wrong link (that is, on my Linux box...) resided in
/usr/local/lib;
I had made it some time ago as a link to
/usr/local/pgsql/src/interfaces/libpq/libpq.so.1.1 (or something)

Thanks for the clue Ernst. I reran ldconfig and the source tree is now
happy. I have my system configured to have the ld database point to
/opt/postgres/current/lib/ so it wasn't just a softlink change.

So the story is that the name of libpq.so.xx has changed. But why bother
with .1 or .1.1 in the first place? Shouldn't the numbering either
change for each new version of libpq interface, or be omitted
altogether? Has anyone thought about having it match the Postgres
release number?

- Tom