Porting of Python 2.1.1 to QNX6.1 solved ...

bridged with qdn.public.qnxrtp.porting
Armin Steinhoff

Porting of Python 2.1.1 to QNX6.1 solved ...

Post by Armin Steinhoff » Fri Aug 24, 2001 8:59 pm

Hi all,

the port of Python 2.1.1 can to be done with the following steps:

1) install the Python archive at /
then do the export cmds: export PYTHONPATH=/Python-2.1.1 ,
export PYTHONHOME=/Python-2.1.1
2) copy all *.py files from /Python-2.1.1/Lib to
/Python-2.1.1/lib/python2.1
(there is a curious fault in the UNIX distribution..)

3) configure: CC=qcc LDFLAGS=-Wl,-E CCSHARED="-shared -fPIC"
CFLAGSFORSHARED="-shared -fPIC" LDSHARED="qcc -shared"
BLDSHARED="qcc -shared" ./configure --with-threads
(in ONE cmd line ..)

4) make
5) make install
6) export cmds: export PYTHONPATH=/usr/local/lib/python2.1
export PYTHONHOME=/usr/local/lib/python2.1

7) copy all shared objects from $PYTHONPATH/lib-dynload to
$PYTHONPATH/lib/python2.1 (as you know ... there is a curious
faulr ...)

8) Have fun with Python :)

Armin

David Alessio

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by David Alessio » Tue Oct 09, 2001 10:07 pm

This compiles and Python comes up, but
import math
fails with a SIGSEGV three calls into libc from dlopen("math.so",
RTLD_NOW) in dynload_shlib.c

Does anyone else have this problem? Any ideas?

Thanks,
david



Armin Steinhoff wrote:
Hi all,

the port of Python 2.1.1 can to be done with the following steps:

1) install the Python archive at /
then do the export cmds: export PYTHONPATH=/Python-2.1.1 ,
export PYTHONHOME=/Python-2.1.1
2) copy all *.py files from /Python-2.1.1/Lib to
/Python-2.1.1/lib/python2.1
(there is a curious fault in the UNIX distribution..)

3) configure: CC=qcc LDFLAGS=-Wl,-E CCSHARED="-shared -fPIC"
CFLAGSFORSHARED="-shared -fPIC" LDSHARED="qcc -shared"
BLDSHARED="qcc -shared" ./configure --with-threads
(in ONE cmd line ..)

4) make
5) make install
6) export cmds: export PYTHONPATH=/usr/local/lib/python2.1
export PYTHONHOME=/usr/local/lib/python2.1

7) copy all shared objects from $PYTHONPATH/lib-dynload to
$PYTHONPATH/lib/python2.1 (as you know ... there is a curious
faulr ...)

8) Have fun with Python :)

Armin

Armin

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by Armin » Wed Oct 10, 2001 4:41 pm

David Alessio wrote:
This compiles and Python comes up, but
import math
fails with a SIGSEGV three calls into libc from dlopen("math.so",
RTLD_NOW) in dynload_shlib.c

Does anyone else have this problem?

No, I have checked it and didn't saw such a problem. Python 2.1 works
very stable ....
Any ideas?

Take care about LD_LIBRARY_PATH and its frends ...
Armin

Thanks,
david



Armin Steinhoff wrote:

Hi all,

the port of Python 2.1.1 can to be done with the following steps:

1) install the Python archive at /
then do the export cmds: export PYTHONPATH=/Python-2.1.1 ,
export PYTHONHOME=/Python-2.1.1
2) copy all *.py files from /Python-2.1.1/Lib to
/Python-2.1.1/lib/python2.1
(there is a curious fault in the UNIX distribution..)

3) configure: CC=qcc LDFLAGS=-Wl,-E CCSHARED="-shared -fPIC"
CFLAGSFORSHARED="-shared -fPIC" LDSHARED="qcc -shared"
BLDSHARED="qcc -shared" ./configure --with-threads
(in ONE cmd line ..)

4) make
5) make install
6) export cmds: export PYTHONPATH=/usr/local/lib/python2.1
export PYTHONHOME=/usr/local/lib/python2.1

7) copy all shared objects from $PYTHONPATH/lib-dynload to
$PYTHONPATH/lib/python2.1 (as you know ... there is a curious
faulr ...)

8) Have fun with Python :)

Armin

Guest

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by Guest » Thu Oct 11, 2001 7:01 am

Hi David,
This compiles and Python comes up, but
import math
fails with a SIGSEGV three calls into libc from dlopen("math.so",
RTLD_NOW) in dynload_shlib.c

Does anyone else have this problem? Any ideas?
Has math.so been linked against the static libm? If it is, that would
need to be changed, my math.so is linked against libm.so.2 (check the
output of "objdump -p math.so" to find out what it is linked against),
and it works for me.

Julian Kinraid

David Alessio

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by David Alessio » Fri Oct 12, 2001 10:20 pm

Hi Julian,

Dynamic Section:
NEEDED libm.so.2
NEEDED libc.so.2


Good thought, though. Thanks for the feedback.

-david




jkinraid@clear.net.nz wrote:
Hi David,

This compiles and Python comes up, but
import math
fails with a SIGSEGV three calls into libc from dlopen("math.so",
RTLD_NOW) in dynload_shlib.c

Does anyone else have this problem? Any ideas?

Has math.so been linked against the static libm? If it is, that would
need to be changed, my math.so is linked against libm.so.2 (check the
output of "objdump -p math.so" to find out what it is linked against),
and it works for me.

Julian Kinraid

David Alessio

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by David Alessio » Sat Oct 13, 2001 4:48 am

Hello,

I don't know exactly what the problem was, but if I adjust Armin's
procedure, it works for me. I even have Tkinter working (on 8.3.2) with
most of Guido's and Matt's demos.

Now if we can only get XPhoton fixed, it'd stay up longer...

Cheers,
-david



David Alessio wrote:
This compiles and Python comes up, but
import math
fails with a SIGSEGV three calls into libc from dlopen("math.so",
RTLD_NOW) in dynload_shlib.c

Does anyone else have this problem? Any ideas?

Thanks,
david

Armin Steinhoff wrote:

Hi all,

the port of Python 2.1.1 can to be done with the following steps:

1) install the Python archive at /
then do the export cmds: export PYTHONPATH=/Python-2.1.1 ,
export PYTHONHOME=/Python-2.1.1
2) copy all *.py files from /Python-2.1.1/Lib to
/Python-2.1.1/lib/python2.1
(there is a curious fault in the UNIX distribution..)
Don't do the copy, instead, use a link:

2) cd /Python-2.1.1
mkdir lib
ln -s /Python-2.1.1/Lib lib/python2.1
3) configure: CC=qcc LDFLAGS=-Wl,-E CCSHARED="-shared -fPIC"
CFLAGSFORSHARED="-shared -fPIC" LDSHARED="qcc -shared"
BLDSHARED="qcc -shared" ./configure --with-threads
(in ONE cmd line ..)

4) make
4.5) You will now have a directory something like this:
/Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1
Create a link Lib/lib-dynload that points to this directory:
ln -s /Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1 Lib/lib-dynload
5) make install
6) export cmds: export PYTHONPATH=/usr/local/lib/python2.1
export PYTHONHOME=/usr/local/lib/python2.1
Hmmm, I don't need these.
7) copy all shared objects from $PYTHONPATH/lib-dynload to
$PYTHONPATH/lib/python2.1 (as you know ... there is a curious
faulr ...)
I didn't need to do this. I think this is necessary only if the Env
Vars are defined in (6)

8) Have fun with Python :)

Armin
Now I can. Thanks Armin!

Chris McKillop

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by Chris McKillop » Sat Oct 13, 2001 6:44 am

David Alessio <david.alessio@hsa.hitachi.com> wrote:

Hello,

I don't know exactly what the problem was, but if I adjust Armin's
procedure, it works for me. I even have Tkinter working (on 8.3.2) with
most of Guido's and Matt's demos.

Now if we can only get XPhoton fixed, it'd stay up longer...
Something to try...

slay Xphoton gtwm
Xphoton -nocrc &
gtwm &

chris

--
cdm@qnx.com "The faster I go, the behinder I get."
Chris McKillop -- Lewis Carroll --
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Armin

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by Armin » Sat Oct 13, 2001 11:28 am

David Alessio wrote:
Hello,

I don't know exactly what the problem was, but if I adjust Armin's
procedure, it works for me. I even have Tkinter working (on 8.3.2) with
most of Guido's and Matt's demos.

Now if we can only get XPhoton fixed, it'd stay up longer...

Hmmm ... add the neccessary X server, libs a.s.o to the X11R6
directories of XPhoton and you can run XFree86 if you have a critical
X application. (~ 2-3 MB of binaries ... )

BTW ... the port of XFree86 version 4.1 available at

http://www.sourceforge.net/projects/openqnx

Big thanks to Frank !!

Armin


Cheers,
-david



David Alessio wrote:

This compiles and Python comes up, but
import math
fails with a SIGSEGV three calls into libc from dlopen("math.so",
RTLD_NOW) in dynload_shlib.c

Does anyone else have this problem? Any ideas?

Thanks,
david

Armin Steinhoff wrote:

Hi all,

the port of Python 2.1.1 can to be done with the following steps:

1) install the Python archive at /
then do the export cmds: export PYTHONPATH=/Python-2.1.1 ,
export PYTHONHOME=/Python-2.1.1

2) copy all *.py files from /Python-2.1.1/Lib to
/Python-2.1.1/lib/python2.1
(there is a curious fault in the UNIX distribution..)


Don't do the copy, instead, use a link:

2) cd /Python-2.1.1
mkdir lib
ln -s /Python-2.1.1/Lib lib/python2.1

Yes ... of course that's better :)
3) configure: CC=qcc LDFLAGS=-Wl,-E CCSHARED="-shared -fPIC"
CFLAGSFORSHARED="-shared -fPIC" LDSHARED="qcc -shared"
BLDSHARED="qcc -shared" ./configure --with-threads
(in ONE cmd line ..)

4) make



4.5) You will now have a directory something like this:
/Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1
Create a link Lib/lib-dynload that points to this directory:
ln -s /Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1 Lib/lib-dynload

I will 'repare' in the next days the 'getpath' module ... so that
configure and make are only neccessary to build python 2.1.1
5) make install

6) export cmds: export PYTHONPATH=/usr/local/lib/python2.1
export PYTHONHOME=/usr/local/lib/python2.1


Hmmm, I don't need these.

At least one of them should be set .. IMHO
7) copy all shared objects from $PYTHONPATH/lib-dynload to
$PYTHONPATH/lib/python2.1 (as you know ... there is a curious
faulr ...)

I didn't need to do this. I think this is necessary only if the Env
Vars are defined in (6)

interesting ...
Armin

Armin

Re: Correction ...Porting of Python 2.1.1 to QNX6.1 solved .

Post by Armin » Sat Oct 13, 2001 11:34 am

Armin wrote:
David Alessio wrote:

Hello,

I don't know exactly what the problem was, but if I adjust Armin's
procedure, it works for me. I even have Tkinter working (on 8.3.2) with
most of Guido's and Matt's demos.

Now if we can only get XPhoton fixed, it'd stay up longer...

Hmmm ... add the neccessary X server, libs a.s.o to the X11R6
directories of XPhoton and you can run XFree86 if you have a
critical X application. (~ 2-3 MB of binaries ... )

BTW ... the port of XFree86 version 4.1 available at

http://www.sourceforge.net/projects/openqnx

Big thanks to Frank !!
Sorry ... too early. Version 4.1 will be available in a short time
frame ....

Armin

Armin



Cheers,
-david



David Alessio wrote:

This compiles and Python comes up, but
import math
fails with a SIGSEGV three calls into libc from dlopen("math.so",
RTLD_NOW) in dynload_shlib.c

Does anyone else have this problem? Any ideas?

Thanks,
david

Armin Steinhoff wrote:

Hi all,

the port of Python 2.1.1 can to be done with the following steps:

1) install the Python archive at /
then do the export cmds: export PYTHONPATH=/Python-2.1.1 ,
export PYTHONHOME=/Python-2.1.1

2) copy all *.py files from /Python-2.1.1/Lib to
/Python-2.1.1/lib/python2.1
(there is a curious fault in the UNIX distribution..)


Don't do the copy, instead, use a link:

2) cd /Python-2.1.1
mkdir lib
ln -s /Python-2.1.1/Lib lib/python2.1

Yes ... of course that's better :)

3) configure: CC=qcc LDFLAGS=-Wl,-E CCSHARED="-shared -fPIC"
CFLAGSFORSHARED="-shared -fPIC" LDSHARED="qcc -shared"
BLDSHARED="qcc -shared" ./configure --with-threads
(in ONE cmd line ..)

4) make



4.5) You will now have a directory something like this:
/Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1
Create a link Lib/lib-dynload that points to this directory:
ln -s /Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1 Lib/lib-dynload

I will 'repare' in the next days the 'getpath' module ... so that
configure and make are only neccessary to build python 2.1.1

5) make install

6) export cmds: export PYTHONPATH=/usr/local/lib/python2.1
export PYTHONHOME=/usr/local/lib/python2.1


Hmmm, I don't need these.

At least one of them should be set .. IMHO

7) copy all shared objects from $PYTHONPATH/lib-dynload to
$PYTHONPATH/lib/python2.1 (as you know ... there is a curious
faulr ...)

I didn't need to do this. I think this is necessary only if the Env
Vars are defined in (6)

interesting ...

Armin

Miguel Simon

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by Miguel Simon » Sat Oct 13, 2001 5:31 pm

Armin et. al.

Hi... I wonder if perhaps you could clarify something for me here:

1. To get XFree86 going, I will need to stop photon, and then start
XFree86. Correct? How would I stop photon? Then, how do I start
XFree86 here? Just like we do in Linux?

2. Any way to tell which applications need Photon vs. XFree86?

3. Can I have both XFree86 and Photon running simultaneously?

Thanks...

Miguel


--
---
my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.
---
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com

Frank Liu

Re: Correction ...Porting of Python 2.1.1 to QNX6.1 solved .

Post by Frank Liu » Sat Oct 13, 2001 10:36 pm

ok, it is up there now.
any quesitons, please join the mailing list at
http://lists.sourceforge.net/lists/list ... -developer

frank

On Sat, 13 Oct 2001, Armin wrote:
Armin wrote:

David Alessio wrote:

Hello,

I don't know exactly what the problem was, but if I adjust Armin's
procedure, it works for me. I even have Tkinter working (on 8.3.2) with
most of Guido's and Matt's demos.

Now if we can only get XPhoton fixed, it'd stay up longer...

Hmmm ... add the neccessary X server, libs a.s.o to the X11R6
directories of XPhoton and you can run XFree86 if you have a
critical X application. (~ 2-3 MB of binaries ... )

BTW ... the port of XFree86 version 4.1 available at

http://www.sourceforge.net/projects/openqnx

Big thanks to Frank !!

Sorry ... too early. Version 4.1 will be available in a short time
frame ....

Armin



Armin



Cheers,
-david



David Alessio wrote:

This compiles and Python comes up, but
import math
fails with a SIGSEGV three calls into libc from dlopen("math.so",
RTLD_NOW) in dynload_shlib.c

Does anyone else have this problem? Any ideas?

Thanks,
david

Armin Steinhoff wrote:

Hi all,

the port of Python 2.1.1 can to be done with the following steps:

1) install the Python archive at /
then do the export cmds: export PYTHONPATH=/Python-2.1.1 ,
export PYTHONHOME=/Python-2.1.1

2) copy all *.py files from /Python-2.1.1/Lib to
/Python-2.1.1/lib/python2.1
(there is a curious fault in the UNIX distribution..)


Don't do the copy, instead, use a link:

2) cd /Python-2.1.1
mkdir lib
ln -s /Python-2.1.1/Lib lib/python2.1

Yes ... of course that's better :)

3) configure: CC=qcc LDFLAGS=-Wl,-E CCSHARED="-shared -fPIC"
CFLAGSFORSHARED="-shared -fPIC" LDSHARED="qcc -shared"
BLDSHARED="qcc -shared" ./configure --with-threads
(in ONE cmd line ..)

4) make



4.5) You will now have a directory something like this:
/Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1
Create a link Lib/lib-dynload that points to this directory:
ln -s /Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1 Lib/lib-dynload

I will 'repare' in the next days the 'getpath' module ... so that
configure and make are only neccessary to build python 2.1.1

5) make install

6) export cmds: export PYTHONPATH=/usr/local/lib/python2.1
export PYTHONHOME=/usr/local/lib/python2.1


Hmmm, I don't need these.

At least one of them should be set .. IMHO

7) copy all shared objects from $PYTHONPATH/lib-dynload to
$PYTHONPATH/lib/python2.1 (as you know ... there is a curious
faulr ...)

I didn't need to do this. I think this is necessary only if the Env
Vars are defined in (6)

interesting ...

Armin




Frank Liu

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by Frank Liu » Sat Oct 13, 2001 10:41 pm

when I installed rtp, I chose the text console, so I can
either "startx" or "ph" to run either X or photon.
I am sure you can reconfig your system so that it starts up in text.

simutaneously? two solutions:
1) run "ph" to start Photon as your main GUI, use Xphoton for X apps.
2) run "startx" to start X as your main GUI, use "phinx" for Photon apps.

My guess is both Xphoton and phinx aren't reliable for heavy duty usage.
They should work fine for casual usage. Depending on your main usage
of the GUI, you can choose either 1 or 2 above.

BTW, Garry should be able to give more insights on the status of phinx
or Xphoton. They are his baby :)

Frank

On Sat, 13 Oct 2001, Miguel Simon wrote:
Armin et. al.

Hi... I wonder if perhaps you could clarify something for me here:

1. To get XFree86 going, I will need to stop photon, and then start
XFree86. Correct? How would I stop photon? Then, how do I start
XFree86 here? Just like we do in Linux?

2. Any way to tell which applications need Photon vs. XFree86?

3. Can I have both XFree86 and Photon running simultaneously?

Thanks...

Miguel


--
---
my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.
---
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com

Miguel Simon

Re: Correction ...Porting of Python 2.1.1 to QNX6.1 solved .

Post by Miguel Simon » Sat Oct 13, 2001 11:45 pm

Frank...

I see your port now. Great work! :) Thanks.

I wonder if you are thinking about porting KDevelop? Would this be a
difficult task? Has someone done this before?

Also, where you successful in porting ddd with your XFree86 4.1 port?

Bests...

Miguel.

Frank Liu wrote:
ok, it is up there now.
any quesitons, please join the mailing list at
http://lists.sourceforge.net/lists/list ... -developer

frank

On Sat, 13 Oct 2001, Armin wrote:

Armin wrote:

David Alessio wrote:

Hello,

I don't know exactly what the problem was, but if I adjust Armin's
procedure, it works for me. I even have Tkinter working (on 8.3.2) with
most of Guido's and Matt's demos.

Now if we can only get XPhoton fixed, it'd stay up longer...

Hmmm ... add the neccessary X server, libs a.s.o to the X11R6
directories of XPhoton and you can run XFree86 if you have a
critical X application. (~ 2-3 MB of binaries ... )

BTW ... the port of XFree86 version 4.1 available at

http://www.sourceforge.net/projects/openqnx

Big thanks to Frank !!

Sorry ... too early. Version 4.1 will be available in a short time
frame ....

Armin



Armin



Cheers,
-david



David Alessio wrote:

This compiles and Python comes up, but
import math
fails with a SIGSEGV three calls into libc from dlopen("math.so",
RTLD_NOW) in dynload_shlib.c

Does anyone else have this problem? Any ideas?

Thanks,
david

Armin Steinhoff wrote:

Hi all,

the port of Python 2.1.1 can to be done with the following steps:

1) install the Python archive at /
then do the export cmds: export PYTHONPATH=/Python-2.1.1 ,
export PYTHONHOME=/Python-2.1.1

2) copy all *.py files from /Python-2.1.1/Lib to
/Python-2.1.1/lib/python2.1
(there is a curious fault in the UNIX distribution..)


Don't do the copy, instead, use a link:

2) cd /Python-2.1.1
mkdir lib
ln -s /Python-2.1.1/Lib lib/python2.1

Yes ... of course that's better :)

3) configure: CC=qcc LDFLAGS=-Wl,-E CCSHARED="-shared -fPIC"
CFLAGSFORSHARED="-shared -fPIC" LDSHARED="qcc -shared"
BLDSHARED="qcc -shared" ./configure --with-threads
(in ONE cmd line ..)

4) make



4.5) You will now have a directory something like this:
/Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1
Create a link Lib/lib-dynload that points to this directory:
ln -s /Python-2.1.1/build/lib.qnx-6.1.0-x86pc-2.1 Lib/lib-dynload

I will 'repare' in the next days the 'getpath' module ... so that
configure and make are only neccessary to build python 2.1.1

5) make install

6) export cmds: export PYTHONPATH=/usr/local/lib/python2.1
export PYTHONHOME=/usr/local/lib/python2.1


Hmmm, I don't need these.

At least one of them should be set .. IMHO

7) copy all shared objects from $PYTHONPATH/lib-dynload to
$PYTHONPATH/lib/python2.1 (as you know ... there is a curious
faulr ...)

I didn't need to do this. I think this is necessary only if the Env
Vars are defined in (6)

interesting ...

Armin




--
---
my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.
---
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com

Miguel Simon

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by Miguel Simon » Sat Oct 13, 2001 11:51 pm

Frank...

Thanks.

When installing your port of XFree86, any suggestions on where to put
the different executables? Any general hits about what not to do, or
what to do? Thanks.

There is an entry in http://qdn.qnx.com/support/bok/solution.qnx?10044
about how to get into command mode.

Regards...

Miguel.


Frank Liu wrote:
when I installed rtp, I chose the text console, so I can
either "startx" or "ph" to run either X or photon.
I am sure you can reconfig your system so that it starts up in text.

simutaneously? two solutions:
1) run "ph" to start Photon as your main GUI, use Xphoton for X apps.
2) run "startx" to start X as your main GUI, use "phinx" for Photon apps.

My guess is both Xphoton and phinx aren't reliable for heavy duty usage.
They should work fine for casual usage. Depending on your main usage
of the GUI, you can choose either 1 or 2 above.

BTW, Garry should be able to give more insights on the status of phinx
or Xphoton. They are his baby :)

Frank

On Sat, 13 Oct 2001, Miguel Simon wrote:

Armin et. al.

Hi... I wonder if perhaps you could clarify something for me here:

1. To get XFree86 going, I will need to stop photon, and then start
XFree86. Correct? How would I stop photon? Then, how do I start
XFree86 here? Just like we do in Linux?

2. Any way to tell which applications need Photon vs. XFree86?

3. Can I have both XFree86 and Photon running simultaneously?

Thanks...

Miguel


--
---
my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.
---
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com
--
---
my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.
---
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com

Frank Liu

Re: Porting of Python 2.1.1 to QNX6.1 solved ...

Post by Frank Liu » Sun Oct 14, 2001 5:04 am

I will post a detailed installation instruction to the mailing list.


On Sat, 13 Oct 2001, Miguel Simon wrote:
Frank...

Thanks.

When installing your port of XFree86, any suggestions on where to put
the different executables? Any general hits about what not to do, or
what to do? Thanks.

There is an entry in http://qdn.qnx.com/support/bok/solution.qnx?10044
about how to get into command mode.

Regards...

Miguel.


Frank Liu wrote:

when I installed rtp, I chose the text console, so I can
either "startx" or "ph" to run either X or photon.
I am sure you can reconfig your system so that it starts up in text.

simutaneously? two solutions:
1) run "ph" to start Photon as your main GUI, use Xphoton for X apps.
2) run "startx" to start X as your main GUI, use "phinx" for Photon apps.

My guess is both Xphoton and phinx aren't reliable for heavy duty usage.
They should work fine for casual usage. Depending on your main usage
of the GUI, you can choose either 1 or 2 above.

BTW, Garry should be able to give more insights on the status of phinx
or Xphoton. They are his baby :)

Frank

On Sat, 13 Oct 2001, Miguel Simon wrote:

Armin et. al.

Hi... I wonder if perhaps you could clarify something for me here:

1. To get XFree86 going, I will need to stop photon, and then start
XFree86. Correct? How would I stop photon? Then, how do I start
XFree86 here? Just like we do in Linux?

2. Any way to tell which applications need Photon vs. XFree86?

3. Can I have both XFree86 and Photon running simultaneously?

Thanks...

Miguel


--
---
my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.
---
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com


--
---
my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.
---
Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com

Post Reply

Return to “qdn.public.qnxrtp.porting”