>Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > ... The patch for
> > pg_regress.sh should be taken out as well. If someone wants to run the
> > parallel regression tests he can install a real shell.
>
>Fine with me (it's a mighty ugly patch) but if we treat it that way
>then FAQ_QNX4 had best mention that the parallel regress tests do not
>work without <some shell>. Compare FAQ_HPUX.

Yes, it is rather ugly but I couldn't come up with something better. Will
change the FAQ accordingly.

> > Postgres on qnx4 should now be operational.
>
>Can you fix the compiler installation so you won't need the weird
>-I/usr/local/lib/gcc-lib/i386-pc-qnx4/egcs-2.91.60/include/g++ option
>anymore?

I believe it's necessary only if you're going to build the libpq++
interface.
I don't have gpp installed, so I can't check it, but from the default
install script I would say it is safe to change this to
/usr/local/include/g++ .

>Also, can you check the comment in src/backend/bootstrap/Makefile, "qnx4's
>wlink currently crashes with bootstrap.o". Is this fixed?

No, effectively support for the Watcom compiler suite has stopped some
time after Watcom was bought by Sybase. Until the OpenWatcom project
releases the open source version of the compiler and QSSL adds their
part of the QNX port we will be stuck with this problem.

Am 14:06 30.04.01 -0400 schrieb Tom Lane:
>Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I looked this over and it looks safe for 7.1.1. Only QNX changes are
> > made. Can someone confirm?
>
>No! It also reverts my 1.91 changes in s_lock.h. Please correct the
>patch to not do that.
Done.

Am 00:36 01.05.01 +0200 schrieb Peter Eisentraut:
>Bruce Momjian writes:
>
> > I looked this over and it looks safe for 7.1.1. Only QNX changes are
> > made. Can someone confirm? If no one confirms it is save, I will keep
> > it for 7.2.
>
>The patch for plpgsql/Makefile is unnecessary.
This is another instance of wlib dying while trying to build the library.
Since plpgsql does not work on QNX anyway I saw no reason to let it
enter that directory at all.

I have added an on_proc_exit function in semget() so that the process which
creates the semaphore shared memory will remove it on exit. This seems to
work but if this is not not The Right Way to do this, please enlighten me.

TIA, Bernd

--
Bernd Tegge mailto:tegge(at)repas-aeg(dot)de
Tel: ++49-511-87449-12 repas AEG Automation GmbH
Fax: ++49-511-87449-20 GS Hannover, Germany