I’m chassing a problem with devi-elo not working with 6.1.
To isolate the problem, i’m trying to run 6.0 version of devi-elo
on 6.1 machine
The 6.1 machine is custom build. Files are store on flash
and not all components are installed.
With trying to run devi-elo (6.0) it compains it couldn’t find the
share object (didn’t tell which one).
I used objdump to check what .so were needed. I copied
libph.so.1 libphrender.so.1 and libc.so.1. Made sure
LD_LIBRARY_PATH was pointing to them. Still
devi-elo complains it can’t access the shared library.
What have I missed?
export DL_DEBUG=1
this should give you some extra information.
Mario Charest <mcharest@voidzinformatic.com> wrote:
I’m chassing a problem with devi-elo not working with 6.1.
To isolate the problem, i’m trying to run 6.0 version of devi-elo
on 6.1 machine
The 6.1 machine is custom build. Files are store on flash
and not all components are installed.
With trying to run devi-elo (6.0) it compains it couldn’t find the
share object (didn’t tell which one).
I used objdump to check what .so were needed. I copied
libph.so.1 libphrender.so.1 and libc.so.1. Made sure
LD_LIBRARY_PATH was pointing to them. Still
devi-elo complains it can’t access the shared library.
What have I missed?
“Jason Clarke” <jclarke@qnx.com> wrote in message
news:9in10o$4dd$1@nntp.qnx.com…
export DL_DEBUG=1
Interesting > 
this should give you some extra information.
I didn’t change anything, I see no extra information.
However if I start the 6.1 version of devi-elo I see the
extra info. Is DL_DEBUG capability new to 6.1?
With 6.0 devi-elo all I see is:
sh: ./devi-elo: Can’t access shared library
Mario Charest <> mcharest@voidzinformatic.com> > wrote:
I’m chassing a problem with devi-elo not working with 6.1.
To isolate the problem, i’m trying to run 6.0 version of devi-elo
on 6.1 machine
The 6.1 machine is custom build. Files are store on flash
and not all components are installed.
With trying to run devi-elo (6.0) it compains it couldn’t find the
share object (didn’t tell which one).
I used objdump to check what .so were needed. I copied
libph.so.1 libphrender.so.1 and libc.so.1. Made sure
LD_LIBRARY_PATH was pointing to them. Still
devi-elo complains it can’t access the shared library.
What have I missed?
Mario Charest <mcharest@voidzinformatic.com> wrote:
“Jason Clarke” <> jclarke@qnx.com> > wrote in message
news:9in10o$4dd$> 1@nntp.qnx.com> …
export DL_DEBUG=1
Interesting >
this should give you some extra information.
I didn’t change anything, I see no extra information.
However if I start the 6.1 version of devi-elo I see the
extra info. Is DL_DEBUG capability new to 6.1?
Nope.
With 6.0 devi-elo all I see is:
sh: ./devi-elo: Can’t access shared library
???, I’ve used it since nto2.0
maybe you mixing your build files up and you are using *.so.2
with 6.0 stuff? (just a guess)
Mario Charest <> mcharest@voidzinformatic.com> > wrote:
I’m chassing a problem with devi-elo not working with 6.1.
To isolate the problem, i’m trying to run 6.0 version of devi-elo
on 6.1 machine
The 6.1 machine is custom build. Files are store on flash
and not all components are installed.
With trying to run devi-elo (6.0) it compains it couldn’t find the
share object (didn’t tell which one).
I used objdump to check what .so were needed. I copied
libph.so.1 libphrender.so.1 and libc.so.1. Made sure
LD_LIBRARY_PATH was pointing to them. Still
devi-elo complains it can’t access the shared library.
What have I missed?
“Jason Clarke” <jclarke@qnx.com> wrote in message
news:9in5ii$70l$1@nntp.qnx.com…
Mario Charest <> mcharest@voidzinformatic.com> > wrote:
“Jason Clarke” <> jclarke@qnx.com> > wrote in message
news:9in10o$4dd$> 1@nntp.qnx.com> …
export DL_DEBUG=1
Interesting >
this should give you some extra information.
I didn’t change anything, I see no extra information.
However if I start the 6.1 version of devi-elo I see the
extra info. Is DL_DEBUG capability new to 6.1?
Nope.
With 6.0 devi-elo all I see is:
sh: ./devi-elo: Can’t access shared library
???, I’ve used it since nto2.0
maybe you mixing your build files up and you are using *.so.2
with 6.0 stuff? (just a guess)
The build files only contains .so.2 related stuff, yes. I’m trying to get
devi-elo from 6.0 running on a 6.1 machine.
I can run the ls command from 6.0 with no problem so it’s not a libc issue.
Mario Charest <> mcharest@voidzinformatic.com> > wrote:
I’m chassing a problem with devi-elo not working with 6.1.
To isolate the problem, i’m trying to run 6.0 version of devi-elo
on 6.1 machine
The 6.1 machine is custom build. Files are store on flash
and not all components are installed.
With trying to run devi-elo (6.0) it compains it couldn’t find the
share object (didn’t tell which one).
I used objdump to check what .so were needed. I copied
libph.so.1 libphrender.so.1 and libc.so.1. Made sure
LD_LIBRARY_PATH was pointing to them. Still
devi-elo complains it can’t access the shared library.
What have I missed?
If you are getting “Can’t access shared library” on running the program,
you are most likely missing the dynamic loader.
Make sure you have
/usr/lib/ldqnx.so.1 → /proc/boot/libc.so.1
Mario Charest <mcharest@voidzinformatic.com> wrote:
I’m chassing a problem with devi-elo not working with 6.1.
To isolate the problem, i’m trying to run 6.0 version of devi-elo
on 6.1 machine
The 6.1 machine is custom build. Files are store on flash
and not all components are installed.
With trying to run devi-elo (6.0) it compains it couldn’t find the
share object (didn’t tell which one).
I used objdump to check what .so were needed. I copied
libph.so.1 libphrender.so.1 and libc.so.1. Made sure
LD_LIBRARY_PATH was pointing to them. Still
devi-elo complains it can’t access the shared library.
What have I missed?
“Colin Burgess” <cburgess@qnx.com> wrote in message
news:9ivdki$bsd$1@nntp.qnx.com…
If you are getting “Can’t access shared library” on running the program,
you are most likely missing the dynamic loader.
Make sure you have
/usr/lib/ldqnx.so.1 → /proc/boot/libc.so.1
Arrggggh
Thanks Colin
Mario Charest <mcharest@zinformatic.com> wrote:
“Colin Burgess” <> cburgess@qnx.com> > wrote in message
news:9ivdki$bsd$> 1@nntp.qnx.com> …
If you are getting “Can’t access shared library” on running the program,
you are most likely missing the dynamic loader.
Make sure you have
/usr/lib/ldqnx.so.1 → /proc/boot/libc.so.1
Please, make that:
/usr/lib/ldqnx.so.1 → …/…/proc/boot/libc.so.1
Absolute path is evil in QNET case 
-xtang
Arrggggh
Thanks Colin
Sorry Xiaodan! :v)
Xiaodan Tang <xtang@qnx.com> wrote:
Mario Charest <> mcharest@zinformatic.com> > wrote:
“Colin Burgess” <> cburgess@qnx.com> > wrote in message
news:9ivdki$bsd$> 1@nntp.qnx.com> …
If you are getting “Can’t access shared library” on running the program,
you are most likely missing the dynamic loader.
Make sure you have
/usr/lib/ldqnx.so.1 → /proc/boot/libc.so.1
Please, make that:
/usr/lib/ldqnx.so.1 → …/…/proc/boot/libc.so.1
Absolute path is evil in QNET case >
-xtang
Arrggggh
Thanks Colin
–
cburgess@qnx.com