Im not able to install postgresql-8.1.2 on CentOS 4.1

#uname -a
Linux localhost.localdomain 2.6.9-11.EL #1 Wed Jun 8 16:59:52 CDT 2005
i686 i686 i386 GNU/Linux

Thanks
Danish


---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

Danish Siddiqui wrote:
What's the error you're getting?

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

--=-YuhHzkAgFDEwfJYE7LV9
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, 2006-12-12 at 19:23 +0530, Danish Siddiqui wrote:
"How" it is not working? What is the error message?

--=20
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/





--=-YuhHzkAgFDEwfJYE7LV9
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBFfwmHpme12CBXnxERAhhSAKCvZLNL3Uy7sv0rfLxWyG g648cQEgCgpg88
LGO6CARClQrwAC8lGIdD+44=
=GHob
-----END PGP SIGNATURE-----

--=-YuhHzkAgFDEwfJYE7LV9--

Danish Siddiqui wrote:
Please keep the mailing list cc'd!

I'm no Makefile guru, but that sounds like an issue with modification
timestamps on the files. I'd suggest checking the timestamps on
config.status. I can reproduce that behavior if I run "touch -d
2007-01-01 configure". If that's your problem, "touch configure" should
help.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Heikki Linnakangas <heikki (AT) enterprisedb (DOT) com> writes:
No, just fix your system clock setting. This is the standard behavior
seen when the source files have timestamps "in the future" according
to the system clock --- make keeps trying to generate derived files
that are newer, and yet they still seem to be out of date compared
to the sources ...

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Tom Lane wrote:
Thanks a lot...it worked

I just set the timestamp...the time on my system was 20 March 2000...

Danish

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq