Thread: Beta5 on Linux Alpha
I just have tested your 7.0beta5. My system is RH Linux 6.1 2.2.14 on Alpha. gcc --version says: egcs-2.91.66. I still have two major problems: 1. ./configure doesn't recognize my OS. ./config.guess reports: alphaev5-unknown-linux-gnu so ./configure chooses 'linux' and fails. 2. I compiled and installed all the stuff successfully using ./configure --with-x --with-tcl --with-template=linux_alpha Environment is set as follows: PGDATA=/usr/local/pgsql/data PGLIB=/usr/local/pgsql/lib LD_LIBRARY_PATH=/usr/local/pgsql/lib Running initdb causes the following: > This database system will be initialized with username "postgres". > This user will own all the data files and must also own the server process. > > Creating database system directory /usr/local/pgsql/data > Creating database system directory /usr/local/pgsql/data/base > Creating database XLOG directory /usr/local/pgsql/data/pg_xlog > Creating template database in /usr/local/pgsql/data/base/template1 > > FATAL: s_lock(2030d400) at spin.c:115, stuck spinlock. Aborting. > > FATAL: s_lock(2030d400) at spin.c:115, stuck spinlock. Aborting. > > initdb failed. > Removing /usr/local/pgsql/data. > Removing temp file /tmp/initdb.32548. I faced with exactly the same trouble since PostgreSQL 6.4. Sincerely yours, Denis N. Stepanov. BINP SB RAS, Novosibirsk, Russia.
The following confirmed for your 7.0RC1 (except that spinlock stuck arises at spin.c:116). Please, do smth before the official release comes! > I just have tested your 7.0beta5. My system is RH Linux 6.1 2.2.14 on Alpha. > gcc --version says: egcs-2.91.66. I still have two major problems: > > 1. ./configure doesn't recognize my OS. ./config.guess reports: > alphaev5-unknown-linux-gnu > so ./configure chooses 'linux' and fails. > > 2. I compiled and installed all the stuff successfully using > ./configure --with-x --with-tcl --with-template=linux_alpha > > Environment is set as follows: > PGDATA=/usr/local/pgsql/data > PGLIB=/usr/local/pgsql/lib > LD_LIBRARY_PATH=/usr/local/pgsql/lib > > Running initdb causes the following: > > > This database system will be initialized with username "postgres". > > This user will own all the data files and must also own the server process. > > > > Creating database system directory /usr/local/pgsql/data > > Creating database system directory /usr/local/pgsql/data/base > > Creating database XLOG directory /usr/local/pgsql/data/pg_xlog > > Creating template database in /usr/local/pgsql/data/base/template1 > > > > FATAL: s_lock(2030d400) at spin.c:115, stuck spinlock. Aborting. > > > > FATAL: s_lock(2030d400) at spin.c:115, stuck spinlock. Aborting. > > > > initdb failed. > > Removing /usr/local/pgsql/data. > > Removing temp file /tmp/initdb.32548. > > I faced with exactly the same trouble since PostgreSQL 6.4. > > Sincerely yours, > > Denis N. Stepanov. > BINP SB RAS, Novosibirsk, Russia.
"Denis N. Stepanov" <dstepan@DSGDL.inp.nsk.su> writes: >> 1. ./configure doesn't recognize my OS. ./config.guess reports: >> alphaev5-unknown-linux-gnu >> so ./configure chooses 'linux' and fails. Fixed as of current sources: the first entry of src/template/.similar now reads alpha[a-z0-9]*-unknown-linux-gnu=linux_alpha >>>> FATAL: s_lock(2030d400) at spin.c:115, stuck spinlock. Aborting. Can't help you with that, since I don't have access to a machine like yours. It's fairly likely that the platform-specific code for Alpha in src/include/storage/s_lock.h or src/backend/storage/buffer/s_lock.c is not being compiled or is being compiled wrong. Check whether the right #define symbols are being set on your platform. s_lock.c can be compiled as a stand-alone test program, if you need it. regards, tom lane