I’m trying to port BLT2.4u (TCL/Tk extension). The static versions of
bltsh and bltwish work well. I’m having trouble with the shared
versions – they crash before main while loading shared libs.
Python2.1.1 and Pmw expect the
shared versions.
I’m trying to port BLT2.4u (TCL/Tk extension). The static versions of
bltsh and bltwish work well. I’m having trouble with the shared
versions – they crash before main while loading shared libs.
Python2.1.1 and Pmw expect the shared versions.
You can link TCL/Tk statically by activating the TCL/Tk/Tkinter entries
in the Modules/Setup file … you should also add a reference to the BLT
object module to the Tkinter (?) line.
I installed the mig4nto-procmgr files as described on the website (i.e. make
install), which put a copy of the executable mig4nto-procmgr in my /x86/bin
directory. When I try to run it from that directory (i.e. ./mig4nto-procmgr
-vv
&) it says that it can’t find the library libmig4nto.so.1.
I looked for that library and found a similar one (libmig4nto.so) in
/usr/nto/src/nto/mig4nto/mig4nto/x86/so. I copied that library to /lib and
tried
running the executable from the /x86/bin directory again, but it gave the
same
error message.
I renamed the library from .so to .so.1 and reran the executable and it
didn’t
give me any error message, but neither did it print out anything about
successful
operation.
My questions are:
Was renaming the library the right thing to do?
If so, is there any way to verify that mig4nto-procmgr is running
correctly
(i.e. what should I expect to see with the -vv flags on)?
I installed the mig4nto-procmgr files as described on the website (i.e. make
install), which put a copy of the executable mig4nto-procmgr in my /x86/bin
directory. When I try to run it from that directory (i.e. ./mig4nto-procmgr
-vv
&) it says that it can’t find the library libmig4nto.so.1.
I looked for that library and found a similar one (libmig4nto.so) in
/usr/nto/src/nto/mig4nto/mig4nto/x86/so. I copied that library to /lib and
tried
running the executable from the /x86/bin directory again, but it gave the
same
error message.
I renamed the library from .so to .so.1 and reran the executable and it
didn’t
give me any error message, but neither did it print out anything about
successful
operation.
My questions are:
Was renaming the library the right thing to do?
If so, is there any way to verify that mig4nto-procmgr is running
correctly
(i.e. what should I expect to see with the -vv flags on)?
Does anyone know if it’s possible to compile a DOS executable under QNX, copy
the executable to a DOS machine and have it run?
I have one piece of code (to control some motor control boards) that has to run
under both DOS and QNX. I’ve seen some tidbits that maybe the Watcom compiler
does that, but I’m now using qcc(gcc), so I’m especially interested if it’s
possible (via some flag or something) under qcc. Thanks!
Does anyone know if it’s possible to compile a DOS executable under QNX,
copy
the executable to a DOS machine and have it run?
I have one piece of code (to control some motor control boards) that has
to run
under both DOS and QNX. I’ve seen some tidbits that maybe the Watcom
compiler
does that, but I’m now using qcc(gcc), so I’m especially interested if
it’s
possible (via some flag or something) under qcc. Thanks!
Watcom is only available for QNX4.
I guess it might be possible to port gcc for DOS under QNX6.
Personnaly I think it would be much easier to have a windows machine
and a QNX6 machine on the network and share the common files
through file sharing.
Ok, I guess I’ll give the NFS route a shot. Thanks.
Neville
Mario Charest wrote:
“Neville Bonwit” <> neville@erg.sri.com> > wrote in message
news:> 3BE835A1.8B6678BB@erg.sri.com> …
Does anyone know if it’s possible to compile a DOS executable under QNX,
copy
the executable to a DOS machine and have it run?
I have one piece of code (to control some motor control boards) that has
to run
under both DOS and QNX. I’ve seen some tidbits that maybe the Watcom
compiler
does that, but I’m now using qcc(gcc), so I’m especially interested if
it’s
possible (via some flag or something) under qcc. Thanks!
Watcom is only available for QNX4.
I guess it might be possible to port gcc for DOS under QNX6.
Personnaly I think it would be much easier to have a windows machine
and a QNX6 machine on the network and share the common files
through file sharing.
“Neville Bonwit” <> neville@erg.sri.com> > wrote in message
news:> 3BE835A1.8B6678BB@erg.sri.com> …
Does anyone know if it’s possible to compile a DOS executable under QNX,
copy
the executable to a DOS machine and have it run?
I have one piece of code (to control some motor control boards) that has
to run
under both DOS and QNX. I’ve seen some tidbits that maybe the Watcom
compiler
does that, but I’m now using qcc(gcc), so I’m especially interested if
it’s
possible (via some flag or something) under qcc. Thanks!
Watcom is only available for QNX4.
I guess it might be possible to port gcc for DOS under QNX6.
Personnaly I think it would be much easier to have a windows machine
and a QNX6 machine on the network and share the common files
through file sharing.
Ok, I guess I’ll give the NFS route a shot. Thanks.
You might want to look at SMBfsys to mount a DOS machine disk onto your QNX
box. Much simpler and more efficient than NFS.
Neville
Mario Charest wrote:
“Neville Bonwit” <> neville@erg.sri.com> > wrote in message
news:> 3BE835A1.8B6678BB@erg.sri.com> …
Does anyone know if it’s possible to compile a DOS executable under QNX,
copy
the executable to a DOS machine and have it run?
I have one piece of code (to control some motor control boards) that has
to run
under both DOS and QNX. I’ve seen some tidbits that maybe the Watcom
compiler
does that, but I’m now using qcc(gcc), so I’m especially interested if
it’s
possible (via some flag or something) under qcc. Thanks!
Watcom is only available for QNX4.
I guess it might be possible to port gcc for DOS under QNX6.
Personnaly I think it would be much easier to have a windows machine
and a QNX6 machine on the network and share the common files
through file sharing.
On Tue, 06 Nov 2001 11:10:25 -0800, Neville Bonwit <neville@erg.sri.com> wrote:
Does anyone know if it’s possible to compile a DOS executable under QNX, copy
the executable to a DOS machine and have it run?
No, but you can compile code for QNX under DOS(WIndows), copy the code to
QNX and run it.
This can be done using the QNX cross development SDK, hosted under
Windows.
I have one piece of code (to control some motor control boards) that has to run
under both DOS and QNX. I’ve seen some tidbits that maybe the Watcom compiler
does that, but I’m now using qcc(gcc), so I’m especially interested if it’s
possible (via some flag or something) under qcc. Thanks!
“Neville Bonwit” <> neville@erg.sri.com> > wrote in message
news:> 3BE835A1.8B6678BB@erg.sri.com> …
Does anyone know if it’s possible to compile a DOS executable under QNX,
copy
the executable to a DOS machine and have it run?
I have one piece of code (to control some motor control boards) that has
to run
under both DOS and QNX. I’ve seen some tidbits that maybe the Watcom
compiler
does that, but I’m now using qcc(gcc), so I’m especially interested if
it’s
possible (via some flag or something) under qcc. Thanks!
Watcom is only available for QNX4.
I guess it might be possible to port gcc for DOS under QNX6.
There are couple of “ports” gcc for Windows. For example, Mingw (i386-mingw32)
Personnaly I think it would be much easier to have a windows machine
and a QNX6 machine on the network and share the common files
through file sharing.