Re: [PORTS] PostgreSQL 6.5.2 ported to QNX 4

>> The majority of changed files are Makefiles because on QNX it is not
>> possible to generate all the "backend/.../SUBSYS.o" as objects because
>> the -r option is not supported. On QNX I generate archive files now. This
is
>> a general question. I would prefer the archive solution. If the standard
>> distribution will not be changed this way it will be neccessary to patch
the
>> "backend/.../Makefile"s. Furthermore I couldn't include the bootstrap.o
and
>> ipc.o files into the SUBSYS.o archives because the QNX archiver wlib
crashes
>> with them. I don't know why. Therefore I included them directly into
>> backend/Makefile
>
>These are problematic.  Changing $(LD) -r to $(AR) will not work on many
>platforms.  In the current source tree.  I have changed all $(LD) -r to
>$(LD) $(LDREL), and defined LDREL= -r.  The -r can now be overridden in
>Makefile.qnx.  You can now define $LD as 'ar' in qnx.


Good idea.

>Can you tell me what the QNX operating system is?  Is it that real-time
>OS?


Yes, it is. Please refer to http://www.qnx.com

>I am seeing you remove the semicolon here:
>
> @if [ ! -d $(HEADERDIR) ]; then mkdir $(HEADERDIR); fi
>
>                                 ^
>
>That will not work on many platforms.  We need those semicolons.  There
>is another way we could do it, buy using "[ test ] && action", so there
>would be no if...then...fi.  However, that's a lot of tests to change.
>Please let me know why the semicolon is a problem, and whether there is
>an upgraded shell that will allow it on QNX.


With these semicolons "gmake install" always aborts with an error. This is
caused by the original QNX ksh. There is a free shell called pdksh which
could do the job. I haven't tried it yet.
ftp://ftp.qnx.com/usr/free/qnx4/os/shells/pdksh-5.2.3-bin.tgz
But this problem occurs only in about 2 Makefiles on mkdirs.

>I have not added any of the #if QNX code.  My recommendation is that you
>grab a copy of the current tree via cvs, which will have the changes I
>just made, and see if you can get that to work.  You will find that most
>of your stuff will work fine, and that only a few areas now have to be
>modified.

>
>I will then be glad to include all the rest of your changes.  I could
>apply your QNX-specific code, but because I need to get this into
>6.6/7.0 I need your help, I am waiting until you have the current tree
>installed so I know for sure we are going to have QNX as a port.


OK. It  may take a while to organize this because I'm sitting behind a
firewall.

Andreas Kardos