--- Tom Lane <[EMAIL PROTECTED]> wrote: > Kurt Roeckx <[EMAIL PROTECTED]> writes: > > He seems to have changed this too: > > - typedef uint32 IpcMemoryKey; > > + typedef size_t IpcMemoryKey; > > That really should be a key_t. > > Yeah, I made it key_t in CVS tip. I'm just > wondering what this could > avoid other than possibly a compile warning. > > regards, tom lane
Greetings. Sorry for the late reply. I just re-extracted and compiled the 7.4 release, and recreated the error. $ ls -ld postgresql-7.4.tar.bz2 -rw------- 1 tbaden prd 9999669 Nov 18 12:22 postgresql-7.4.tar.bz2 $ md5 postgresql-7.4.tar.bz2 MD5(postgresql-7.4.tar.bz2)= 9db7432c431d1570b1f605727daf27bc $ ./configure --with-python --with-openssl --without-readline Pertinent environment variables: CC='cc -xtarget=ultra -xarch=v9 -D_XOPEN_SOURCE=500 -D__EXTENSIONS__' CXX='CC -xtarget=ultra -xarch=v9 -D_XOPEN_SOURCE=500 -D__EXTENSIONS__' After compilation, make check fails as follows: make[3]: Leaving directory `/export/home/tbaden/posttemp/postgresql-7.4/contrib/spi' /bin/sh ./pg_regress --temp-install --top-builddir=../../.. --schedule=./parallel_schedule --multibyte=SQL_ASCII ============== creating temporary installation ============== ============== initializing database system ============== pg_regress: initdb failed Examine ./log/initdb.log for the reason. I have attached initdb.log for your perusal. I just went digging through the system include files, and sure enough they do refer to key_t instead of size_t. I don't recall why I used size_t, except that it must have been referenced in either a different .h file or man page. Cheers, -Thomas __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree
initdb.log
Description: initdb.log
---------------------------(end of broadcast)--------------------------- TIP 8: explain analyze is your friend
