Qt3 and QNX6.2NC Grrr....

QNX Newsgroups (Archives) openqnx.developer
1

Hi Frank,

Using QNX6.2 and SMP kernel resolve a problem
→ XFree4.2 doesn’t lockup !!!
good, BUT…
I’ve trouble get my programs run (and Qt3 samples programs).
In fact the compile pass without difficulty (no particular errors) but when I
start the executable I get strange behaviour.
Everything working with a file give a coredump.
The behaviour of the QThread class is ??? strange

I’ve identified that a Qt samples compiled under QNX 6.1A works fine under
QNX 6.2 NC but if I recompiled this sample it doesn’t work. (the outliner XML
sample)
another indice : in 6.2 I have to add :
DEFINES += QT_NO_STL
in .pro file to compile.
in 6.1A that wasn’t obligatory.

Well, in French we say “Au secours !!!”
I suppose problem with a C++ library but which ?

Thanks (a lot of)

PS : is it completely stupid to boot a 6.1 box with qnxbasesmp.ifs from a 6.2
system ? Cause I think this is I want to resolv my both problem :slight_smile:
PS2 : In French we use the expression “keep cool” too !-)

Institut Albert Bonniot
Johan CARDON Faculté de Medecine de Grenoble
Laboratoire IMAG/TIMC/GMCAO Domaine de la Merci
Tel: +33 (0)4 76 54 95 05 38706 La Tronche Cedex

2

On Thu, 20 Jun 2002, Johan CARDON wrote:

Hi Frank,

Using QNX6.2 and SMP kernel resolve a problem
→ XFree4.2 doesn’t lockup !!!

good to hear. whether cdm wants to admit it or not, the lockup
problem ends up to be a qnx smp support problem :slight_smile:

Well, in French we say “Au secours !!!”
I suppose problem with a C++ library but which ?

Most likely because of the C++ changes.
6.1 uses Dinkum and 6.2NC uses GNU.
I will have to re-port the Qt to 6.2NC GNU C++ when I have “free”
time or “paid” time.

PS : is it completely stupid to boot a 6.1 box with qnxbasesmp.ifs from a 6.2

I don’t think there is a problem with that.
I did that a lot, before the release of 6.2, because I had other
problems with the libc that is built into the boot image in 6.1.
copying the boot image from 6.2 solves the problem.
I switched to 6.2 totally since it was released.

Frank

system ? Cause I think this is I want to resolv my both problem > :slight_smile:
PS2 : In French we use the expression “keep cool” too !-)

Institut Albert Bonniot
Johan CARDON Faculté de Medecine de Grenoble
Laboratoire IMAG/TIMC/GMCAO Domaine de la Merci
Tel: +33 (0)4 76 54 95 05 38706 La Tronche Cedex

\

Bringing you mounds of caffeinated joy
http://thinkgeek.com/sf

openqnx-developer mailing list
openqnx-developer=> 5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/openqnx-developer

3

Le Jeudi 20 Juin 2002 17:42, vous avez écrit :

Most likely because of the C++ changes.
6.1 uses Dinkum and 6.2NC uses GNU.
I will have to re-port the Qt to 6.2NC GNU C++ when I have “free”
time or “paid” time.

Yes, I understand the problem. What is the Trolltech position ? Do they just

say (like me) : Thank you Mr Liu, good job !

Before mail you, I tested to compile Qt3.0.4 with your recommendation but get
errors at link stage so I decided to continue using your binaries port. But I
will be patient and test the 6.2 qnxbasesmp.ifs under 6.1

–
Institut Albert Bonniot
Johan CARDON Faculté de Medecine de Grenoble
Laboratoire IMAG/TIMC/GMCAO Domaine de la Merci
Tel: +33 (0)4 76 54 95 05 38706 La Tronche Cedex

4

Is this a problem with just 6.2NC or with 6.2 PE, as well? (I’m not yet
clear on what was the problem…)

-----Original Message-----
From: openqnx-developer-admin=5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openqnx-developer-admin=5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of
Johan CARDON
Sent: Thursday, June 20, 2002 10:00 AM
To: openqnx
Subject: Re: [Openqnx-developer] Qt3 and QNX6.2NC Grrr…


Le Jeudi 20 Juin 2002 17:42, vous avez écrit :

Most likely because of the C++ changes.
6.1 uses Dinkum and 6.2NC uses GNU.
I will have to re-port the Qt to 6.2NC GNU C++ when I have “free” time

or “paid” time.

Yes, I understand the problem. What is the Trolltech position ? Do they

just
say (like me) : Thank you Mr Liu, good job !

Before mail you, I tested to compile Qt3.0.4 with your recommendation
but get
errors at link stage so I decided to continue using your binaries port.
But I
will be patient and test the 6.2 qnxbasesmp.ifs under 6.1

–
Institut Albert Bonniot
Johan CARDON Faculté de Medecine de Grenoble
Laboratoire IMAG/TIMC/GMCAO Domaine de la Merci
Tel: +33 (0)4 76 54 95 05 38706 La Tronche Cedex

\

Bringing you mounds of caffeinated joy

http://thinkgeek.com/sf

openqnx-developer mailing list openqnx-developer=5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/openqnx-developer

5

Le Jeudi 20 Juin 2002 18:09, vous avez écrit :

Is this a problem with just 6.2NC or with 6.2 PE, as well? (I’m not yet
clear on what was the problem…)
Hi,

I can just test on NC cause I haven’t PE.
The problem is that when you compile a Qt3 project who works fine on QNX6…1A,
you gets a beautiful little executable file (compile and link stage are ok)
and when you run this file you have very strange behaviour.

To be more precise :
In 6.1A there were no coredump with my project. and my XML parsing with QDOM
works fine.
In 6.2NC I get rapidly a coredump. gdb says it is on the messageHandler in
main.cpp (MessageHandler is the function you install with
qInstallMsgHandler() )
So, I disable this function, recompile and see my main window with some mixed
icone in toolbar and if I try to open and parse my XML file I always get this
message box :
title : Critical Error
msg : Error parsing XML file
button : Ok

Hope this help you.
Thanks,

Institut Albert Bonniot
Johan CARDON Faculté de Medecine de Grenoble
Laboratoire IMAG/TIMC/GMCAO Domaine de la Merci
Tel: +33 (0)4 76 54 95 05 38706 La Tronche Cedex

6

I don’t have the PE version, and am not sure it has the same problem.
Being just a QNX hobbist, I can’t justify the cost to my “boss”. She
would rather use the money to feed the kids :slight_smile:
On the other hand, it is probably NOT a good idea to have PE.
I certainly don’t want my ported applications stop running for those
free NC users. cdm and the 3rd party CD got bitten by this already.

As far as Qt goes, my guess is PE may have a better chance than
NC because PE includes the Dinkum C++ support. Still, it probably
won’t just work, because rumor said 6.2PE changed the C++ default
to GNU, while 6.1 C++ defaults to Dinkum …

To answer johan, no I’ve never heard a word from Trolltech. They
are probably mad at me because my work took away their revenue from
the customer engineering work for QNX :slight_smile:

Frank

On Thu, 20 Jun 2002, Lonnie VanZandt wrote:

Is this a problem with just 6.2NC or with 6.2 PE, as well? (I’m not yet
clear on what was the problem…)

-----Original Message-----
From: openqnx-developer-admin=> 5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openqnx-developer-admin=> 5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> ] On Behalf Of
Johan CARDON
Sent: Thursday, June 20, 2002 10:00 AM
To: openqnx
Subject: Re: [Openqnx-developer] Qt3 and QNX6.2NC Grrr…


Le Jeudi 20 Juin 2002 17:42, vous avez écrit :
Most likely because of the C++ changes.
6.1 uses Dinkum and 6.2NC uses GNU.
I will have to re-port the Qt to 6.2NC GNU C++ when I have “free” time

or “paid” time.

Yes, I understand the problem. What is the Trolltech position ? Do they
just
say (like me) : Thank you Mr Liu, good job !

Before mail you, I tested to compile Qt3.0.4 with your recommendation
but get
errors at link stage so I decided to continue using your binaries port.
But I
will be patient and test the 6.2 qnxbasesmp.ifs under 6.1

–
Institut Albert Bonniot
Johan CARDON Faculté de Medecine de Grenoble
Laboratoire IMAG/TIMC/GMCAO Domaine de la Merci
Tel: +33 (0)4 76 54 95 05 38706 La Tronche Cedex

\

Bringing you mounds of caffeinated joy
http://thinkgeek.com/sf

openqnx-developer mailing list openqnx-developer=> 5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/openqnx-developer


\

Bringing you mounds of caffeinated joy
http://thinkgeek.com/sf

openqnx-developer mailing list
openqnx-developer=> 5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/openqnx-developer

7

Good dig on the SMP there Frank. :wink:

Just to clarify for people…there was a mistake in the packaging of the
Dinkum C++ libs in the NC edition where libcpp.so.2a was not included in the
distribution. You can not, however, target the Dinkum C++ lib from NC, just
run binaries built with it. So if you are building Qt apps on 6.2 vs. libs
from 6.1 and the 6.1 libs are built against dinkum, you are in trouble. I
am not sure what Qt is built against.

chris

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

----- Original Message -----
From: “Frank Liu” <liug=wJsaexb6DEQ3G7qi5jAxu4dd74u8MsAO@public.gmane.org>
To: <openqnx-developer=5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Sent: Thursday, June 20, 2002 9:59 AM
Subject: RE: [Openqnx-developer] Qt3 and QNX6.2NC Grrr…



I don’t have the PE version, and am not sure it has the same problem.
Being just a QNX hobbist, I can’t justify the cost to my “boss”. She
would rather use the money to feed the kids :slight_smile:
On the other hand, it is probably NOT a good idea to have PE.
I certainly don’t want my ported applications stop running for those
free NC users. cdm and the 3rd party CD got bitten by this already.

As far as Qt goes, my guess is PE may have a better chance than
NC because PE includes the Dinkum C++ support. Still, it probably
won’t just work, because rumor said 6.2PE changed the C++ default
to GNU, while 6.1 C++ defaults to Dinkum …

To answer johan, no I’ve never heard a word from Trolltech. They
are probably mad at me because my work took away their revenue from
the customer engineering work for QNX :slight_smile:

Frank

On Thu, 20 Jun 2002, Lonnie VanZandt wrote:

Is this a problem with just 6.2NC or with 6.2 PE, as well? (I’m not yet
clear on what was the problem…)

-----Original Message-----
From: openqnx-developer-admin=> 5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
[mailto:openqnx-developer-admin=> 5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> ] On Behalf Of
Johan CARDON
Sent: Thursday, June 20, 2002 10:00 AM
To: openqnx
Subject: Re: [Openqnx-developer] Qt3 and QNX6.2NC Grrr…


Le Jeudi 20 Juin 2002 17:42, vous avez écrit :
Most likely because of the C++ changes.
6.1 uses Dinkum and 6.2NC uses GNU.
I will have to re-port the Qt to 6.2NC GNU C++ when I have “free” time

or “paid” time.

Yes, I understand the problem. What is the Trolltech position ? Do they
just
say (like me) : Thank you Mr Liu, good job !

Before mail you, I tested to compile Qt3.0.4 with your recommendation
but get
errors at link stage so I decided to continue using your binaries port.
But I
will be patient and test the 6.2 qnxbasesmp.ifs under 6.1

–
Institut Albert Bonniot
Johan CARDON Faculté de Medecine de Grenoble
Laboratoire IMAG/TIMC/GMCAO Domaine de la Merci
Tel: +33 (0)4 76 54 95 05 38706 La Tronche Cedex

\

Bringing you mounds of caffeinated joy
http://thinkgeek.com/sf

openqnx-developer mailing list openqnx-developer=> 5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/openqnx-developer


\

Bringing you mounds of caffeinated joy
http://thinkgeek.com/sf

openqnx-developer mailing list
openqnx-developer=> 5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/openqnx-developer

Bringing you mounds of caffeinated joy

http://thinkgeek.com/sf    <<<
8

On Thu, 20 Jun 2002, Chris McKillop wrote:

from 6.1 and the 6.1 libs are built against dinkum, you are in trouble. I
am not sure what Qt is built against.

Qt on the openqnx site was built on qnx 6.1, as mentioned in previous emails.
Since Qt is a C++ thingy, you would have guessed “Qt is built against”
Dinkum. I don’t think there is a GNU C++ support in the devtools in 6.1.

The following matrix of QNX C++ (dev toolchain) support may be helpful:

QNX 6.0: GNU C++
QNX 6.1: Dinkum C++
QNX 6.2NC: GNU C++
QNX 6.2SE/PE: GNU C++ and Dinkum C++

QNX6.1 also has the runtime support for GNU C++ so that you can
run the old binaries from QNX 6.0.
QNX6.2NC also has the runtime support for the old Dinkum as found
in QNX 6.1 so that you can run those old binaries from QNX 6.1 (that’s
how johan ran the Qt examples).
QNX6.2NC also is supposed to have the runtime support of the new
Dinkum as in QNX6.2PE/SE so that you can run the programs compiled
on the QNX6.2SE/PE boxes, but as cdm mentioned, the packaging team
screwed up and missed that. Hopefully the next patch will fix that.
In the meantime, you may get around by symlink the old Dinkum lib
to new Dinkum lib name.

Frank