RTP 6.2 3rd Party...

…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing, they
say the can’t resolve dependancies. For example it can’t find Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post more
simptoms later if I no one else has seen this problem.

Thanks
Pete Eddy

the subject says “RTP 6.2 3rd Party”.
are you sure you are running RTP 6.2 that was released few days ago?

frank

Pete Eddy <peter.w.eddy@lmco.com> wrote:

…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing, they
say the can’t resolve dependancies. For example it can’t find Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post more
simptoms later if I no one else has seen this problem.

Thanks
Pete Eddy

Yeah I just installed it, and it seems to fix a couple compatability
issues, and automatically reconise my video card. All the QNX stuff seems
to work so far. So I was happy with that.

I just seem to be having some trouble with the 3rd party apps. They are
all completely separate from the 6.2 OS install image in this version. It
seems like the X windows support from the 3rd party disk is have problems.
I think I may need to install something I’m missing. The package manager
shows XFree86 installed, but I can’t run anything that requires the X
windows shared libraries. I think maybe the Xwindows package is messed up.

HELP!!! Any body who has any Idea what’s wrong, I’d appreciate any help I
could get. DDD may not be the slickest debugger interface, but it beats the
gdb command line.

Pete Eddy


“Frank Liu” <liug@mama.indstate.edu> wrote in message
news:ae2nmt$ck4$1@inn.qnx.com

the subject says “RTP 6.2 3rd Party”.
are you sure you are running RTP 6.2 that was released few days ago?

frank

Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing,
they
say the can’t resolve dependancies. For example it can’t find
Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post
more
simptoms later if I no one else has seen this problem.

Thanks
Pete Eddy

Yep. I think this is an NC packaging bug. Regardless, tell the install
to continue, disregarding the error, and manually symlink /lib/libcpp.so.2 to
/lib/libcpp.so.2a and everything should work fine.

chris

Pete Eddy <peter.w.eddy@lmco.com> wrote:

…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing, they
say the can’t resolve dependancies. For example it can’t find Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post more
simptoms later if I no one else has seen this problem.

Thanks
Pete Eddy
\


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Thanks, I’ll give it a try.
Ok, on the other front is there something screwy with the X Windows support?
I can’t get any X apps to run? No DDD, no Emacs, no Dia, no nothing!
I can’t seem to find hardly any X window shared libraries. I was going to
try and install over a 6.1 installation and see if that picked up the old X
windows support, but I none of the notes I read mention how to upgrade a
installation. It’s probally really easy and I’ll kick myself after you tell
me, but what are you going to do?

Pete Eddy


“Chris McKillop” <cdm@qnx.com> wrote in message
news:ae2sof$hen$2@nntp.qnx.com

Yep. I think this is an NC packaging bug. Regardless, tell the install
to continue, disregarding the error, and manually symlink /lib/libcpp.so.2
to
/lib/libcpp.so.2a and everything should work fine.

chris

Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing,
they
say the can’t resolve dependancies. For example it can’t find
Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post
more
simptoms later if I no one else has seen this problem.

Thanks
Pete Eddy



\

Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Frank Liu <liug@mama.indstate.edu> wrote:

the subject says “RTP 6.2 3rd Party”.

It really means “RTP 6.2SE or above”.
My guess is you have 6.2NC but all the applications on the 3rd party
CD were compiled on the 6.2SE installation.
they may or may not run on the 6.2NC though rumors said 6.2NC would
include the runtime libs from 6.2SE. There may be bugs here and there
that prevent you from running 6.2SE binaries on 6.2NC.
I will recompile XFree, DDD, etc on a 6.2NC machine and release it.
I hope the next release of 3rd party CD will be based on 6.2NC.
In the meantime, you can download XFree, DDD, etc from
http://www.sourceforge.net/projects/openqnx
those were compiled on 6.1A and will work fine on 6.2NC.

Frank



are you sure you are running RTP 6.2 that was released few days ago?

frank

Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing, they
say the can’t resolve dependancies. For example it can’t find Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post more
simptoms later if I no one else has seen this problem.

Thanks
Pete Eddy

One of the other guys here just gave me a note,
ipfilter is looking for npm_tcpip_v6.so and he says
that npm_tcpip_v4.so is all that’s avaliable on his installation.

Any suggestions?

Pete Eddy


“Chris McKillop” <cdm@qnx.com> wrote in message
news:ae2sof$hen$2@nntp.qnx.com

Yep. I think this is an NC packaging bug. Regardless, tell the install
to continue, disregarding the error, and manually symlink /lib/libcpp.so.2
to
/lib/libcpp.so.2a and everything should work fine.

chris

Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing,
they
say the can’t resolve dependancies. For example it can’t find
Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post
more
simptoms later if I no one else has seen this problem.

Thanks
Pete Eddy



\

Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Yes, that is something we didn’t realize until it was too late. You can
use the ipfilter from my 6.1 repository, http://qnx.wox.org/repository/6.1/,
and when the next release of the Public CDROM is made (when, no idea) it will
include both ipfilter packages.

chris


Pete Eddy <peter.w.eddy@lmco.com> wrote:

One of the other guys here just gave me a note,
ipfilter is looking for npm_tcpip_v6.so and he says
that npm_tcpip_v4.so is all that’s avaliable on his installation.

Any suggestions?

Pete Eddy


“Chris McKillop” <> cdm@qnx.com> > wrote in message
news:ae2sof$hen$> 2@nntp.qnx.com> …
Yep. I think this is an NC packaging bug. Regardless, tell the install
to continue, disregarding the error, and manually symlink /lib/libcpp.so.2
to
/lib/libcpp.so.2a and everything should work fine.

chris

Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing,
they
say the can’t resolve dependancies. For example it can’t find
Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post
more
simptoms later if I no one else has seen this problem.

Thanks
Pete Eddy



\

Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

\


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Chris McKillop <cdm@qnx.com> wrote:

Yes, that is something we didn’t realize until it was too late. You can
use the ipfilter from my 6.1 repository, > http://qnx.wox.org/repository/6.1/> ,

Bottom line is:
As I mentioned in another post, if you find something on the CD not work,
grab a version compiled for 6.1 from somewhere should normally work.
Let’s hope the next release of the CD will be 6.2NC based.

Frank

and when the next release of the Public CDROM is made (when, no idea) it will
include both ipfilter packages.

chris



Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
One of the other guys here just gave me a note,
ipfilter is looking for npm_tcpip_v6.so and he says
that npm_tcpip_v4.so is all that’s avaliable on his installation.

Any suggestions?

Pete Eddy


“Chris McKillop” <> cdm@qnx.com> > wrote in message
news:ae2sof$hen$> 2@nntp.qnx.com> …
Yep. I think this is an NC packaging bug. Regardless, tell the install
to continue, disregarding the error, and manually symlink /lib/libcpp.so.2
to
/lib/libcpp.so.2a and everything should work fine.

chris

Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing,
they
say the can’t resolve dependancies. For example it can’t find
Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post
more
simptoms later if I no one else has seen this problem.

Thanks
Pete Eddy



\

Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/




\

Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Frank Liu <liug@mama.indstate.edu> wrote:

Chris McKillop <> cdm@qnx.com> > wrote:

Yes, that is something we didn’t realize until it was too late. You can
use the ipfilter from my 6.1 repository, > http://qnx.wox.org/repository/6.1/> ,

Bottom line is:
As I mentioned in another post, if you find something on the CD not work,
grab a version compiled for 6.1 from somewhere should normally work.
Let’s hope the next release of the CD will be 6.2NC based.

Just to be clear - the intention was always to have everything run on NC
without issue. Besides ipftiler and the ipv6 utilities, everything will
RUN without any issues. As for installing, you can safely ignore the
warnings about libcpp and install the packages. In fact, there are even
some applications (like phplay) that are included in NC that won’t work
under NC without setting the symlink from libcpp.so.2 to libcpp.so.2a.

chris


Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Chris McKillop <cdm@qnx.com> wrote:

Yep. I think this is an NC packaging bug. Regardless, tell the install
to continue, disregarding the error, and manually symlink /lib/libcpp.so.2 to
/lib/libcpp.so.2a and everything should work fine.

I believe libcpp.so.2 is the old Dinkum lib that was included
in 6.1 and libcpp.so.2a is the new Dinkum lib that is included in 6.2.
On 6.2SE, you will see both /lib/libcpp.so.2 and /lib/libcpp.so.2a
so that you can run apps that were compiled in 6.1 and 6.2.

Now if you ask me what changes between old and new Dinkum lib,
you got me. I don’t think QSSL ever released a ChangLog on this.
While porting mozilla several months, I noticed some changes in libc.so
from 6.1 and 6.2, I asked for a ChangLog for the libc.so in qdn.private.bmw
but never got an reply for that either.

Whether symlink /lib/libcpp.so.2 to /lib/libcpp.so.2a is safe
is unknown to me. It all depends on what are the changes.
If all is bug fixes, you could hit by a bug using symlink instead of
the real /lib/libcpp.so.2a. If there are api changes, you may or
may not hit it depending on your apps.

Frank

It might be an idea worth considering to have a ‘patch’ or ‘update’ repository.
Checking this repository could be part of the normal installation
procedure.

(Also, please put nfsd and portmap back in newer distributions).

“Chris McKillop” <cdm@qnx.com> wrote in message news:ae34k5$o1l$1@nntp.qnx.com

Yes, that is something we didn’t realize until it was too late. You can
use the ipfilter from my 6.1 repository, > http://qnx.wox.org/repository/6.1/> ,
and when the next release of the Public CDROM is made (when, no idea) it will
include both ipfilter packages.

chris


Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
One of the other guys here just gave me a note,
ipfilter is looking for npm_tcpip_v6.so and he says
that npm_tcpip_v4.so is all that’s avaliable on his installation.

Any suggestions?

Pete Eddy


“Chris McKillop” <> cdm@qnx.com> > wrote in message
news:ae2sof$hen$> 2@nntp.qnx.com> …
Yep. I think this is an NC packaging bug. Regardless, tell the install
to continue, disregarding the error, and manually symlink /lib/libcpp.so.2
to
/lib/libcpp.so.2a and everything should work fine.

chris

Pete Eddy <> peter.w.eddy@lmco.com> > wrote:
…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing,
they
say the can’t resolve dependancies. For example it can’t find
Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post
more
simptoms later if I no one else has seen this problem.

Thanks
Pete Eddy



\

Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/




\

Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

Art Hays <avhays@nih.gov> wrote:

It might be an idea worth considering to have a ‘patch’ or ‘update’ repository.
Checking this repository could be part of the normal installation
procedure.

(Also, please put nfsd and portmap back in newer distributions).

I haven’t heard a definite answer as whether the missing of nfsd
is an oversight or not.
For the new Dinkum runtime lib, Christ at least said it is a bug,
which my understand is its missing is of an oversight.

frank

I haven’t heard a definite answer as whether the missing of nfsd
is an oversight or not.
For the new Dinkum runtime lib, Christ at least said it is a bug,

Well, I guess one can take it as Gospel then that it’s a bug :wink:

“Pete Eddy” <peter.w.eddy@lmco.com> wrote in message
news:ae2qi0$f63$1@inn.qnx.com

Yeah I just installed it, and it seems to fix a couple compatability
issues, and automatically reconise my video card. All the QNX stuff seems
to work so far. So I was happy with that.

I just seem to be having some trouble with the 3rd party apps. They
are
all completely separate from the 6.2 OS install image in this version. It
seems like the X windows support from the 3rd party disk is have problems.
I think I may need to install something I’m missing. The package manager
shows XFree86 installed, but I can’t run anything that requires the X
windows shared libraries. I think maybe the Xwindows package is messed
up.

HELP!!! Any body who has any Idea what’s wrong, I’d appreciate any help I
could get. DDD may not be the slickest debugger interface, but it beats
the
gdb command line.

Emacs is broken due to a change in the memory allocation routines between
QNX 6.2Beta3 and QNX 6.2 Release. There will be a new emacs package
at:
http://developers.cogentrts.com/repository
soon.

The Cogent Gamma/DataHub demo crashes during the DataHub demo if
you do not have QNET running. Just start QNET with the command line:
$ mount -T io-net npm-qnet.so
to avoid the crash.

Cheers,
Andrew

“David Donohoe” <ddonohoe@qnx.com> wrote in message
news:ae61it$21e$1@nntp.qnx.com

I haven’t heard a definite answer as whether the missing of nfsd
is an oversight or not.
For the new Dinkum runtime lib, Christ at least said it is a bug,

Well, I guess one can take it as Gospel then that it’s a bug > :wink:

Was it the fifth or sixth day that He said ‘Let there be bugs’? :wink:

Kris

Pete Eddy wrote in message …

…The 3rd Party disk is real handy, it saves a lot of time with
installations. However some of the packages give me errors installing,
they
say the can’t resolve dependancies. For example it can’t find Libcpp.So.2a
when resolving dependancies. Does anyone know what to do about this? I
couldn’t get emacs or dia to work, and couple other apps. I will post more
simptoms later if I no one else has seen this problem.

Pete:

I too am having various problems with 6.2 third-party apps. Regarding X
Windows, I found that manually creating the following symlink helps with the
libs:

ln -s /opt/X11R6 /usr/X11R6

X apps apparently do not run with 6.2 because, unlike with 6.1, XPhoton is
not automatically launched (by Photon?) as “XPhoton -once” when you run the
X app. Instead, if you first launch X by typing

XPhoton &

then you can run your X apps. I have been unable to find another solution.

->>>–Sherwood–>

I too am having various problems with 6.2 third-party apps. Regarding X
Windows, I found that manually creating the following symlink helps with the
libs:

ln -s /opt/X11R6 /usr/X11R6

Better to take the advice from the FAQ found here:

http://qnx.wox.org/qwiki/QnxFaq

chris

\

Chris McKillop <cdm@qnx.com> “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

The Faq doesn’t say anything about setting up the link. It just tells you:
a… setconf CS_LIBPATH getconf CS_LIBPATH:/opt/X11R6/lib
a… on -t /dev/con1 /opt/X11R6/bin/XPhoton

What’s the difference between setconf and just setting a environment
variable?
Pete Eddy


“Chris McKillop” <cdm@qnx.com> wrote in message
news:af3q9c$nru$1@nntp.qnx.com

I too am having various problems with 6.2 third-party apps. Regarding X
Windows, I found that manually creating the following symlink helps with
the
libs:

ln -s /opt/X11R6 /usr/X11R6


Better to take the advice from the FAQ found here:

http://qnx.wox.org/qwiki/QnxFaq

chris

\

Chris McKillop <> cdm@qnx.com> > “The faster I go, the behinder I get.”
Software Engineer, QSSL – Lewis Carroll –
http://qnx.wox.org/

“Chris McKillop” <cdm@qnx.com> wrote in message
news:af3q9c$nru$1@nntp.qnx.com

I too am having various problems with 6.2 third-party apps. Regarding X
Windows, I found that manually creating the following symlink helps with
the
libs:

ln -s /opt/X11R6 /usr/X11R6


Better to take the advice from the FAQ found here:

http://qnx.wox.org/qwiki/QnxFaq

I can see why this may be a better solution for the library paths, but
there are plenty of open source projects out there that make assumptions
about X11 bins being in /usr/X11R6. I know that some configure scripts
check both /usr and /opt, but I still bump into problems that are best
addressed with the symlink. Out of curiosity, why doesn’t the X11
install get mapped into the /usr hierarchy the way many of the other
installations do?

Cheers,
Andrew