Ok folks, as many of you likely already know we are putting together a
new 3rd party CD to be released simultaneously with the next major
release of QNX (the current plan is end of Jan for this release…but
you know how schedules are, it could be later . What we are planning
on putting on this CD is updates to packages that were on the last CD
(either because of a bug in our port or a new version of the software
has been released), as well as some new content.
I’ve already done a scan of the various projects out there as well and
looked to see what needs to be updated and created a list of what we
would like to do. I’ve attached this list to this posting.
What I’m looking for is a few things:
Eyes to go over this list and make any corrections (as well as fill
me in on what needs to be done on the things that don’t have anything
beside them…ie: is there a New cogent package to go out?)
New content that exists out there already for QNX that I have missed
Suggestions for new content that may not already exist but will
likely prove to be an easy port.
New projects that are currently being developed that will likely be
ready in time for this cd’s release (and the author wishes it to appear
here).
Volunteers to help with the porting/packaging effort.
Any other suggestions as to what could make this cd better.
For those of you that don’t know already, the 3rd party CD is an
unsupported cd that QSSL distributes, and is a volunteer based project.
Not everything on this list may make it to the CD. It will depend
entirely on the number of people working on it and the amount of time we
have. Right now I’m looking at the middle of January (17th?) as the
cut-off date for new content to be submitted. We’ll be testing the
various packages before then, but I think we’ll need at least a couple
of weeks to test the final distribution, fix any bugs that we can, and
pull stuff that doesn’t work and we aren’t going to be able to fix.
Status:
N = New
U = Needs Update (new stable/release version has been released)
C = In unsupported CVS tree
P = In a Package
x = Version on the previous 3rd party cd is to be used
B = Needs bug fix update (bugs specific to the QNX port/package only)
D = Done (it’s in the 3rd party cd repository and there are no known
issues)
Source:
x = Source code is available, it is legal to put it on the cd, and we
intend to do so.
D = Source tarball is on the unsupported cd’s filesystem
We would like to submit new packages for all of these, along with an
improved
demo. Where do we send them, and by what date?
GNUEmacs
This is status: PBx
The version on the the current 3rd-party CD does not run. It depends on
being
able to dump a running process to memory, and then reload it to the same
memory addresses again. Emacs dumps for previous versions of QNX6 tend
not to work on newer versions due to some change in memory layout.
There is also a behaviour in the malloc library where a free() call could
cause
the application to release memory back to the OS, thereby creating a “hole”
in the virtual memory address space of the application. While this is
legal,
it causes emacs to fail while attempting to dump. I submitted a patch that
would add a flag to mallopt() allowing programs to turn off this behaviour
(the patch is trivial), but I do not see it in the on-line QNX CVS. Without
this change, Emacs cannot be compiled and run for QNX6. In order to make
it work, I hacked the library, but that’s not a good solution for the longer
term, or for the handful of other UN*X programs out there that also dump
to disk.
If you can ensure that I have a up-to-date OS kernel before you cut the
3rd-party disk, then I’ll make sure that Emacs will run on it. I have a
QNX-PE license here, if that helps in getting me the correct OS version.
Status:
N = New
U = Needs Update (new stable/release version has been released)
C = In unsupported CVS tree
P = In a Package
x = Version on the previous 3rd party cd is to be used
B = Needs bug fix update (bugs specific to the QNX port/package only)
D = Done (it’s in the 3rd party cd repository and there are no known
issues)
Source:
x = Source code is available, it is legal to put it on the cd, and we
intend to do so.
D = Source tarball is on the unsupported cd’s filesystem
When you have them ready on a website somewhere just send the url to
Dave and myself via email. It would be really great to have things
before Christmas, but mid-Januaray will be the cutoff.
Status:
N = New
U = Needs Update (new stable/release version has been released)
C = In unsupported CVS tree
P = In a Package
x = Version on the previous 3rd party cd is to be used
B = Needs bug fix update (bugs specific to the QNX port/package only)
D = Done (it’s in the 3rd party cd repository and there are no known
issues)
Source:
x = Source code is available, it is legal to put it on the cd, and we
intend to do so.
D = Source tarball is on the unsupported cd’s filesystem
I would like to add MySQL to that list:
MySQL NP x
\
–
Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll – http://qnx.wox.org/
This is a multi-part message in MIME format.
--------------020601030602060407050009
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Ok folks, as many of you likely already know we are putting together a
new 3rd party CD to be released simultaneously with the next major
release of QNX (the current plan is end of Jan for this release…but
you know how schedules are, it could be later > > . What we are planning
on putting on this CD is updates to packages that were on the last CD
(either because of a bug in our port or a new version of the software
has been released), as well as some new content.
What about ‘pstree’?
I made a quick port of v19.3, which seems to be fully functional
(highlighting, args, VT100 chars, etc) and which I hereby offer.
(‘quick’ means: I never used this ‘autoconfigure’ stuff to do a real
portable patch).
Ok folks, as many of you likely already know we are putting together a
new 3rd party CD to be released simultaneously with the next major
release of QNX (the current plan is end of Jan for this release…but
you know how schedules are, it could be later > > . What we are planning
on putting on this CD is updates to packages that were on the last CD
(either because of a bug in our port or a new version of the software
has been released), as well as some new content.
I’ve already done a scan of the various projects out there as well and
looked to see what needs to be updated and created a list of what we
would like to do. I’ve attached this list to this posting.
What I’m looking for is a few things:
Eyes to go over this list and make any corrections (as well as fill
me in on what needs to be done on the things that don’t have anything
beside them…ie: is there a New cogent package to go out?)
New content that exists out there already for QNX that I have missed
For the NC guys:
cscope-15.x
cbrowser-0.x (needs Tcl/Tk )
For the integration of QNX4 and QNX6(LINUX, MS-Windows):
Pyrex (for convenient development of C extensions)
Psyco (specialization compiler)
PyQt-3.1
In general:
SQLite 2.x
Empress?
other free CORBA ORBs
Hope this is not too much
Armin
Suggestions for new content that may not already exist but will
likely prove to be an easy port.
New projects that are currently being developed that will likely be
ready in time for this cd’s release (and the author wishes it to appear
here).
Volunteers to help with the porting/packaging effort.
Any other suggestions as to what could make this cd better.
For those of you that don’t know already, the 3rd party CD is an
unsupported cd that QSSL distributes, and is a volunteer based project.
Not everything on this list may make it to the CD. It will depend
entirely on the number of people working on it and the amount of time we
have. Right now I’m looking at the middle of January (17th?) as the
cut-off date for new content to be submitted. We’ll be testing the
various packages before then, but I think we’ll need at least a couple
of weeks to test the final distribution, fix any bugs that we can, and
pull stuff that doesn’t work and we aren’t going to be able to fix.
Please respond here in this news group.
Thanks for you time.
Dave Rempel
Status:
N = New
U = Needs Update (new stable/release version has been released)
C = In unsupported CVS tree
P = In a Package
x = Version on the previous 3rd party cd is to be used
B = Needs bug fix update (bugs specific to the QNX port/package only)
D = Done (it’s in the 3rd party cd repository and there are no known issues)
Source:
x = Source code is available, it is legal to put it on the cd, and we intend to do so.
D = Source tarball is on the unsupported cd’s filesystem
– blank on status means unknown
Title Status Source
AbuseDemo CPx
CascConnect
CascDataHub
CascHist
CascTextLog
CogentAPI
GNUEmacs
Gamma
GammaGTK
JFSolitaire CPx
KiPhoton
PGLib U
PhAlarm
PhCam
Phumb
a2ps CPx x
alienwave UC x
allegro audio driver x
alsa_utils CPx x
apache1 x
autoconf U x
automake U x
bash U x
bitchx U x
blackbox U x
centericq U x
cpio U x
ctags UC x
curl U x
db U x
ddd U x
dia U x
doxygen U x
elib x
fetchmail U x
fvwm U x
gaim U x
gcal B x
gdbm U x
gdk U x
gettext U x
gimp B x
glib U x
gnuchess CPx x
gnudiff U x
gnugo CPx x
gnutextutils U x
groff U x
gtk U x
indent CPx x
ipaq_columns CPx
ipfbin U x
ircii U x
jed U x
jikes U x
lesstif U x
libIDL CPx x
libart U x
libaudiofile Px x
libiconv U x
libmikmod U x
libpng U x
libsigc++ U x
libtiff U x
libtool U x
libxml2 U x
links U x
lopan CPx x
lynx CPx x
m4 CPx x
maestro audio driver x
mailplugin U
man U
mkdepend CPx x
mpg123 – licensing issues with new patent treatment?
mqc
mutt U x
nail U x
nano CPx x
ncftp U x
ncurses U x
openldap U x
openssh U x
openssl U x
patch CPx x
pcl
perl UC x
phPostal
phSambaChat
phViewer
Abiword (Photon version) U x
ph_ipaqxmp
phaster
phdiff
phftp
phhotkey
phirc
phmame x
phmine_02
photon3d CPx
pine U x
pkgconfig x
pkiphoton
pocket_phumb
postgresql U x
psgml
pureftpd U x
python U x
readline U x
rogue CPx x
rsync CPx x
ruby CPx x
samba U x
screen CPx x
seatris CPx x
sendmail U x
snes9x CPx x
soundtracker Px x
spin
stow
t1lib U x
tcpdump U x
tin U x
tspc
uuencdec CPx x
vim U x
wget U x
workspace U
xchat U x
xfree86 x
xpdf U x
zebra U x
zsh U x
libungif N x
freeciv N x
libSDL N x
libSDL-mixer N x
libSDL-image N x
lbreakout N x
maelstrom SDL N x
liballegro N x
tetris queen (Allegro) N x
bluefish N x
euler N x
distributed net client N x
PhNetLoad N
FreePascal N x
PhAmp N
figlet NC x
figlet contributed fonts NC NA
Bochs N x
mkisofs N x
elm N x
uae (SDL) N x
c-scope N x
nedit N x
aview N
phchess N x
Ok folks, as many of you likely already know we are putting together a
new 3rd party CD to be released simultaneously with the next major
release of QNX (the current plan is end of Jan for this release…but
you know how schedules are, it could be later > > . What we are planning
on putting on this CD is updates to packages that were on the last CD
(either because of a bug in our port or a new version of the software
has been released), as well as some new content.
I’ve already done a scan of the various projects out there as well and
looked to see what needs to be updated and created a list of what we
would like to do. I’ve attached this list to this posting.
[snip]
distributed net client N x
Although there will be new dnetc clients for both QNX4 and QNX6
available with the next release, according to Distributed.net’s terms
they can only be distributed through their web site. You can read about
it here: http://www.distributed.net/download/clients.html
On the good news side, we are the current maintainers for this and plan
to keep the qnx clients up to date.
Ok folks, as many of you likely already know we are putting together a
new 3rd party CD to be released simultaneously with the next major
release of QNX (the current plan is end of Jan for this release…but
you know how schedules are, it could be later > > . What we are planning
on putting on this CD is updates to packages that were on the last CD
(either because of a bug in our port or a new version of the software
has been released), as well as some new content.
I’ve already done a scan of the various projects out there as well and
looked to see what needs to be updated and created a list of what we
would like to do. I’ve attached this list to this posting.
What I’m looking for is a few things:
Eyes to go over this list and make any corrections (as well as fill
me in on what needs to be done on the things that don’t have anything
beside them…ie: is there a New cogent package to go out?)
New content that exists out there already for QNX that I have missed
Suggestions for new content that may not already exist but will
likely prove to be an easy port.
New projects that are currently being developed that will likely be
ready in time for this cd’s release (and the author wishes it to appear
here).
Volunteers to help with the porting/packaging effort.
Any other suggestions as to what could make this cd better.
For those of you that don’t know already, the 3rd party CD is an
unsupported cd that QSSL distributes, and is a volunteer based project.
Not everything on this list may make it to the CD. It will depend
entirely on the number of people working on it and the amount of time we
have. Right now I’m looking at the middle of January (17th?) as the
cut-off date for new content to be submitted. We’ll be testing the
various packages before then, but I think we’ll need at least a couple
of weeks to test the final distribution, fix any bugs that we can, and
pull stuff that doesn’t work and we aren’t going to be able to fix.
Ok folks, as many of you likely already know we are putting together a
new 3rd party CD to be released simultaneously with the next major
release of QNX (the current plan is end of Jan for this release…but
you know how schedules are, it could be later > > . What we are planning
on putting on this CD is updates to packages that were on the last CD
(either because of a bug in our port or a new version of the software
has been released), as well as some new content.
I’ve already done a scan of the various projects out there as well and
looked to see what needs to be updated and created a list of what we
would like to do. I’ve attached this list to this posting.
What I’m looking for is a few things:
Eyes to go over this list and make any corrections (as well as fill
me in on what needs to be done on the things that don’t have anything
beside them…ie: is there a New cogent package to go out?)
New content that exists out there already for QNX that I have missed
For the NC guys:
cscope-15.x
cbrowser-0.x (needs Tcl/Tk )
For the integration of QNX4 and QNX6(LINUX, MS-Windows):
Pyrex (for convenient development of C extensions)
Psyco (specialization compiler)
PyQt-3.1
In general:
SQLite 2.x
Empress?
other free CORBA ORBs
Hope this is not too much >
Armin
It’s not too much if you provide the qpr’s
I don’t anyone currently on the 3rd party cd has enough experience with
most of these to tell if they actually work right or not (hence the
python issue with the last one). Since you seem to know alot about
these then it would be great if you could supply the qpr’s and source.
Otherwise we’ll just do our best. I’ve added them to the list though.
Ok, it’s been removed from the list. We’ll just have to use other
methods to let new and current users about it’s existence then.
Dave
Rick Duff wrote:
Dave Rempel wrote:
Ok folks, as many of you likely already know we are putting together a
new 3rd party CD to be released simultaneously with the next major
release of QNX (the current plan is end of Jan for this release…but
you know how schedules are, it could be later > > . What we are planning
on putting on this CD is updates to packages that were on the last CD
(either because of a bug in our port or a new version of the software
has been released), as well as some new content.
I’ve already done a scan of the various projects out there as well and
looked to see what needs to be updated and created a list of what we
would like to do. I’ve attached this list to this posting.
[snip]
distributed net client N x
Although there will be new dnetc clients for both QNX4 and QNX6
available with the next release, according to Distributed.net’s terms
they can only be distributed through their web site. You can read about
it here: http://www.distributed.net/download/clients.html
On the good news side, we are the current maintainers for this and plan
to keep the qnx clients up to date. >
This is a multi-part message in MIME format.
--------------020601030602060407050009
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Ok folks, as many of you likely already know we are putting together a
new 3rd party CD to be released simultaneously with the next major
release of QNX (the current plan is end of Jan for this release…but
you know how schedules are, it could be later > > . What we are planning
on putting on this CD is updates to packages that were on the last CD
(either because of a bug in our port or a new version of the software
has been released), as well as some new content.
What about ‘pstree’?
I made a quick port of v19.3, which seems to be fully functional
(highlighting, args, VT100 chars, etc) and which I hereby offer.
(‘quick’ means: I never used this ‘autoconfigure’ stuff to do a real
portable patch).
We would like to submit new packages for all of these, along with an
improved
demo. Where do we send them, and by what date?
cdm already answered this…
GNUEmacs
This is status: PBx
The version on the the current 3rd-party CD does not run. It depends on
being
able to dump a running process to memory, and then reload it to the same
memory addresses again. Emacs dumps for previous versions of QNX6 tend
not to work on newer versions due to some change in memory layout.
There is also a behaviour in the malloc library where a free() call could
cause
the application to release memory back to the OS, thereby creating a “hole”
in the virtual memory address space of the application. While this is
legal,
it causes emacs to fail while attempting to dump. I submitted a patch that
would add a flag to mallopt() allowing programs to turn off this behaviour
(the patch is trivial), but I do not see it in the on-line QNX CVS. Without
this change, Emacs cannot be compiled and run for QNX6. In order to make
it work, I hacked the library, but that’s not a good solution for the longer
term, or for the handful of other UN*X programs out there that also dump
to disk.
Yeah, I remember that now…I’ll try and find out it your patch was
applied (what was the flag? I can check libc in our internal cvs)
If you can ensure that I have a up-to-date OS kernel before you cut the
3rd-party disk, then I’ll make sure that Emacs will run on it. I have a
QNX-PE license here, if that helps in getting me the correct OS version.
If you get accepted to the beta for the next release you should have
what you need. If not then we’ll have to work something else out…
Status:
N = New
U = Needs Update (new stable/release version has been released)
C = In unsupported CVS tree
P = In a Package
x = Version on the previous 3rd party cd is to be used
B = Needs bug fix update (bugs specific to the QNX port/package only)
D = Done (it’s in the 3rd party cd repository and there are no known
issues)
Source:
x = Source code is available, it is legal to put it on the cd, and we
intend to do so.
D = Source tarball is on the unsupported cd’s filesystem
I would like to add MySQL to that list:
MySQL NP x
\
Ok, added. Just don’t forget to tell me or cdm where it is
Ok, it’s been removed from the list. We’ll just have to use other
methods to let new and current users about it’s existence then.
I agree. I just compiled the current release candidates today, they
should appear soon and will compile client for other arch’s if there is
demand. Once the Rc5-72 contest starts, I was going to announce it on qnxzone.com and openqnx.com websites as well as post it in comp.os.qnx.
Ok, I’ve added it to the list. Did it compile pretty much out of the
box or did you have to do anything special to it?
No, I had to add a special routine, that scans the /proc-tree.
But that was pretty much straight forward (every supported OS
has it’s own process specialities in this utility).
Shall I post it to somebody (as I said: actually without autoconf
stuff, so it might run only on the x86 platform) ?
I would like to add MySQL to that list:
MySQL NP x
Ok, added. Just don’t forget to tell me or cdm where it is >
I compiled mysql for qnxzone last week, not much changes in the code,
pretty much a straight compile. you can find it here http://www.qnxzone.com/~fliu
. What we are planning