On Thu, 27 May 1999, Jim Ridenour wrote:
> Am running on a RedHat Linux 5.0 Intel box. Now have Postgres 6.2
> running on it so I know it works. Have been trying to compile the new
> Postgres 6.4.2 with no success. The configure utility seems to run all
> right, but running gmake all >& make.log & as the doc's call for exits
> immediately with a message [1] 3122. No other information is given.
> Successive attempts to compile will give the same message but with the
> no.'s incrementing, for example [2] 4761.
Gee! Doesn't this sound familiar! I went through several months trying to
get postgres to compile on my RH 5.2 system. At first I had errors in the
config.log, too. Read the log, not just the messages on the screen.
Regardless, I discovered how to get it to compile. Two things: directories
and permissions.
Copy the tarball to /usr/src and run (as root)
gunzip -c postgresql-6.4.2.tar.gz | tar xvf -
You'll find everything in a directory called postgresql-6.4.2. Still logged
in as root, mv postgresql-6.4.2/ pgsql/. Then run chown postgres.postgres -R
pgsql/ to change all file permissions throughout the source tree. Change the
directory's owner to postgres, too.
For whatever reason, postgres doesn't compile (at least, not on my
systems) in any other directory tree than /usr/src/pgsql/src. Go figure.
Even if you have the default, /usr/src/pgsql/postgresql-6.4.2/src it comes
up with errors.
Making the directories exactly match what the Administrator's Guide,
Chapter 4 (Installation) shows did the trick for me. But, it's not the way
the tarball unrolls.
HTH,
Rich
Dr. Richard B. Shepard, President
Applied Ecosystem Services, Inc.
2404 SW 22nd Street
Troutdale, OR 97060-1247 U.S.A.
+ 1 503-667-4517 (voice) | + 1 503-667-8863 (fax)
[EMAIL PROTECTED]
