There are 2 new binary packages on
https://sourceforge.net/projects/qnxfree
Those are famous Apache and less famous but very nice FTP server. See
Release Notes for each package for details.
Patches will be submitted to main line. Both packages have been
extensively tested and are being used in real environment. I don’t know
of any Neutrino-specific bugs. If you find any, let me know.
Andrew wrote:
Hi Igor,
Love to see a port of Python 2.0c,
Python I thought is in packages repository already, isn’t it?
PHP and Postgres if you find you have a
PHP yes, I could do that easy but it only makes good sense if a good
database is available. I thought about Postgres, but had no time to look
closely. Looked at Berkeley DB too, the problem there is not even
mmap(), it is that it needs SYSV IPC, blast it. Not only it is used in
implementation, it is tied into API.
So now I see that it is needed by: xfree86, KDE, libDB and who knows
what else. I probably will start working on s5ipc server/library then 
spare five minutes to apply your porting skills
It takes much more time if you want to be sure that port is correct,
whatever skills you have
Hi Igor,
Love to see a port of Python 2.0c, PHP and Postgres if you find you have a
spare five minutes to apply your porting skills
Cheers
Andrew
Hi Andrew,
Andrew wrote:
Hi Igor,
Love to see a port of Python 2.0c,
Python 2.0 is already released. I did the ‘port’
today.
At first you have to execute ‘configure’ … the
next step
is to remove in the compile.c and marshall.c
modules (subdir Python) a few strange 'extern
double atof() declarations. (non ANSI C … IMHO)
You have then to disable the mmap module in
Setup.in and to execute make, that’s all for the
standard version.
If you need thread support … enable the thread
module in
Setup.thread. ( → makesetup )
‘make install’ installs Python in /usr/local/lib
by default.
That’s all … but it tooks 15 minutes 
Armin
PHP and Postgres if you find you have a
spare five minutes to apply your porting skills
Cheers
Andrew
Good one Armin,
I’ll try to get it compile on my system.
You should let Kim Bigelow kbigelow@qnx.com at QSSL know that you have done
this because these instructions should be included somehow in the QDN as a
HOWTO or something. It may also be worth feeding your experience back to
the Python dev team so they can include your experience in their install
documentation.
Thanks for lending your expertise on this one. I’ve been really keen to get
V2.0 Python going.
Cheers
Andrew
Python I thought is in packages repository already, isn’t it?
Yeah but an old version (1.5) and it doesn’t work anyway!
PHP yes, I could do that easy but it only makes good sense if a good
database is available.
I’m keen to get PHP to run as a CGI so it is usable from the QNX Slinger web
server.
I thought about Postgres, but had no time to look closely.
Postgres already includes some instructions for compiling under QNX 4 I
think but I haven’t had a close look.
spare five minutes to apply your porting skills
It takes much more time if you want to be sure that port is correct,
whatever skills you have >
I was just being cheeky. I know it takes much longer than five minutes and
much more expertise than I have.
Cheers
Andrew
Hi Armin,
what is the impact of making these changes?
aren’t the bits needed (the ones that you say must be removed)?
forgive my noviceness.
cheers
andrew
“Armin Steinhoff” <A-Steinhoff@web_.de> wrote in message
news:39F0A1CA.1A1AE2B3@web_.de…
Hi Andrew,
Andrew wrote:
Hi Igor,
Love to see a port of Python 2.0c,
Python 2.0 is already released. I did the ‘port’
today.At first you have to execute ‘configure’ … the
next step
is to remove in the compile.c and marshall.c
modules (subdir Python) a few strange 'extern
double atof() declarations. (non ANSI C … IMHO)
You have then to disable the mmap module in
Setup.in and to execute make, that’s all for the
standard version.If you need thread support … enable the thread
module in
Setup.thread. ( → makesetup )‘make install’ installs Python in /usr/local/lib
by default.That’s all … but it tooks 15 minutes >
Armin
PHP and Postgres if you find you have a
spare five minutes to apply your porting skills
Cheers
Andrew
Andrew wrote:
Hi Armin,
what is the impact of making these changes?
aren’t the bits needed (the ones that you say must be removed)?
No … they aren’t neccessary because the
prototype of atof() is already included in the
standard headers.
Cheers
Armin