Thread: 8.0.0beta5 fails "make check" on Solaris9/i386
Hello, "make check" failed on my system. See the last line below and the "/./" in the pathname. Ask if you want more information then I have included below. I'm not subscribbed to the list. Send direct e-mail. Thanks for all the hard work. I'm using 7.4 in daily production on same system. wi792:~/postgresql-8.0.0beta5>uname -a SunOS wi792.aero.org 5.9 Generic_117172-11 i86pc i386 i86pc Solaris wi792:~/postgresql-8.0.0beta5/doc>gcc --version gcc (GCC) 3.3.2 wi792:~/postgresql-8.0.0beta5/doc>make --version GNU Make version 3.78.1, by Richard Stallman and Roland McGrath. Built for i386-pc-solaris2.8 wi792:~/postgresql-8.0.0beta5>make check <SNIP> ============== creating temporary installation ============== ============== initializing database system ============== pg_regress: initdb failed Examine ./log/initdb.log for the reason. make[2]: *** [check] Error 2 make[2]: Leaving directory `/home/alberts/postgresql-8.0.0beta5/src/test/regress' make[1]: *** [check] Error 2 make[1]: Leaving directory `/home/alberts/postgresql-8.0.0beta5/src/test' make: *** [check] Error 2 wi792:~/postgresql-8.0.0beta5> cat /home/alberts/postgresql-8.0.0beta5/src/test/regress/log/initdb.log Running in noclean mode. Mistakes will not be cleaned up. The files belonging to this database system will be owned by user "alberts". This user must also own the server process. The database cluster will be initialized with locale C. creating directory /home/alberts/postgresql-8.0.0beta5/src/test/regress/./tmp_check/data ... initdb: failed wi792:~/postgresql-8.0.0beta5> ===== Chris Albertson Home: 310-376-1029 chrisalbertson90278@yahoo.com Cell: 310-990-7550 Office: 310-336-5189 Christopher.J.Albertson@aero.org KG6OMK __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com
Chris Albertson <chrisalbertson90278@yahoo.com> writes: > creating directory > /home/alberts/postgresql-8.0.0beta5/src/test/regress/./tmp_check/data > ... initdb: failed Now that I look at it, the new improved incarnation of initdb seems prone to say no more than that after a lot of different errors :-(. But the question for you is why it couldn't create that directory. Permissions problem maybe? regards, tom lane