Hi,
I migrated from 6.1 to 6.2 Nc.Now i find that most of my build (nearly
70% of the tree) fails.Possibly because some of the definitions have been
moved around.Is there a way that i can work around this without having to
patch my old code.? If somebody could tell me what all changed in terms of
library and header file organization that would be great.
Thanks
Sreekanth
Hello!
Sreekanth wrote:
I migrated from 6.1 to 6.2 Nc.Now i find that most of my build (nearly
70% of the tree) fails.Possibly because some of the definitions have been
moved around.Is there a way that i can work around this without having to
patch my old code.? If somebody could tell me what all changed in terms of
library and header file organization that would be great.
Just wanted to add a “me-too”. I’m trying QNX 6.2NC on a IBM A31p
notebook since our (paid for) commercial 6.1A does not support the mouse
and will not let me go to text mode with the keyboard once at the Photon
login screen…
It works with 6.2NC (I do need to boot from CD, since booting directly
from hard drive doesn’t work) but both our “makedepend” and make fails
(and this is stuff that compiled perfectly under 6.1). Dependencies
because of things like :
incomplete include == “#include _NTO_HDR(sys/compiler.gnu.h)”
and
cannot find include file “iostream.h”
while make fails with undefined references to math stuff (sqrt, acos,
_Sin).
Now, either QNX has made some changes from 6.1 that would have warranted
a new major version number (they even removed nfsd, portmap! what kind
of unix is that?), 6.2 is broken, NC is broken OR this is all my
fault… Difficult to know now that they separated it in different
products!
Side note: is QNX so popular (monopoly on embedded OS?) that they can
afford doing stuff that Microsoft is usually known for? The only other
time I heard of this kind of move from a software company it came from a
desperate, cash-strapped company that let the marketing department run
amok…
Ricky Ng-Adam, stagiaire laboratoire de robotique
(450) 652-8499 x 2757, local BR0.50
1740 Lionel-Boulet, Varennes
IREQ - Hydro-Québec, Canada
I think if you posted the symbols you’re looking for someone would be able
to tell you where/if
they exist in 6.2 NC(if they moved).
–
Cheers,
Adam
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>
“Sreekanth” <sreekanth@cambira.com> wrote in message
news:agd97g$3gp$1@inn.qnx.com…
Hi,
I migrated from 6.1 to 6.2 Nc.Now i find that most of my build (nearly
70% of the tree) fails.Possibly because some of the definitions have been
moved around.Is there a way that i can work around this without having to
patch my old code.? If somebody could tell me what all changed in terms of
library and header file organization that would be great.Thanks
Sreekanth
Have you asked your sales representative about the possibility of a free
upgrade from your paid-for 6.1A to Momentics SE? I know this is customary
in some regions 
dB
“Ricky Ng-Adam” <ng-adam.ricky@ireq.ca> wrote in message
news:3D2AEE71.5D023B19@ireq.ca…
Hello!
Sreekanth wrote:
I migrated from 6.1 to 6.2 Nc.Now i find that most of my build
(nearly
70% of the tree) fails.Possibly because some of the definitions have
been
moved around.Is there a way that i can work around this without having
to
patch my old code.? If somebody could tell me what all changed in terms
of
library and header file organization that would be great.Just wanted to add a “me-too”. I’m trying QNX 6.2NC on a IBM A31p
notebook since our (paid for) commercial 6.1A does not support the mouse
and will not let me go to text mode with the keyboard once at the Photon
login screen…It works with 6.2NC (I do need to boot from CD, since booting directly
from hard drive doesn’t work) but both our “makedepend” and make fails
(and this is stuff that compiled perfectly under 6.1). Dependencies
because of things like :incomplete include == “#include _NTO_HDR(sys/compiler.gnu.h)”
and
cannot find include file “iostream.h”
while make fails with undefined references to math stuff (sqrt, acos,
_Sin).Now, either QNX has made some changes from 6.1 that would have warranted
a new major version number (they even removed nfsd, portmap! what kind
of unix is that?), 6.2 is broken, NC is broken OR this is all my
fault… Difficult to know now that they separated it in different
products!Side note: is QNX so popular (monopoly on embedded OS?) that they can
afford doing stuff that Microsoft is usually known for? The only other
time I heard of this kind of move from a software company it came from a
desperate, cash-strapped company that let the marketing department run
amok…Thanks,
Ricky Ng-Adam, stagiaire laboratoire de robotique
(450) 652-8499 x 2757, local BR0.50
1740 Lionel-Boulet, Varennes
IREQ - Hydro-Québec, Canada
Adam,
My general assumption was that since it is not a major release(I
think it is mainly bug fixes) from 6.1 to 6.2 everything would work if i
just recompile my sources.I have found out the places where my build is
breaking and i have patched up in some locations.But I am unable to do so in
many places because it is too cumbersome and i am wary of the fact that i
might introduce bugs while trying to fix the build.Also my build is
complaining about some missing C++ libraries.It is not clear to me from the
release notes whether the CPP libraries are part of NC version or they come
only with the Professional edition.Could you guide me with that?
Thanks
Sreekanth
“Adam Mallory” <amallory@qnx.com> wrote in message
news:ageseg$eo1$1@nntp.qnx.com…
I think if you posted the symbols you’re looking for someone would be able
to tell you where/if
they exist in 6.2 NC(if they moved).–
Cheers,
AdamQNX Software Systems Ltd.
[ > amallory@qnx.com > ]With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
“Sreekanth” <> sreekanth@cambira.com> > wrote in message
news:agd97g$3gp$> 1@inn.qnx.com> …
Hi,
I migrated from 6.1 to 6.2 Nc.Now i find that most of my build
(nearly
70% of the tree) fails.Possibly because some of the definitions have
been
moved around.Is there a way that i can work around this without having
to
patch my old code.? If somebody could tell me what all changed in terms
of
library and header file organization that would be great.Thanks
Sreekanth
\
Hi, all.
The Non Commercial (NC) version includes the x86 GNU libstdc++ only.
If your source relies on any Dinkum specific defines, then they will
not be there. Also, if you use a util like mkdepend, you will need
to exclude the system header files from your mkdepend, or use gcc to
generate your dependencies, as a full C Preprocessor is required to
correctly resolve some of the dependendcies.
There is a pearl script included in our 3rd party distribution that
emulates mkdepend but uses gcc to do it.
If you can provide us with more details, we will be happy to work with
you to resolve things.
Regards,
Graeme Peterson.
Tools Group.
Sreekanth <sreekanth@cambira.com> wrote:
Adam,
My general assumption was that since it is not a major release(I
think it is mainly bug fixes) from 6.1 to 6.2 everything would work if i
just recompile my sources.I have found out the places where my build is
breaking and i have patched up in some locations.But I am unable to do so in
many places because it is too cumbersome and i am wary of the fact that i
might introduce bugs while trying to fix the build.Also my build is
complaining about some missing C++ libraries.It is not clear to me from the
release notes whether the CPP libraries are part of NC version or they come
only with the Professional edition.Could you guide me with that?Thanks
Sreekanth
“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:ageseg$eo1$> 1@nntp.qnx.com> …
I think if you posted the symbols you’re looking for someone would be able
to tell you where/if
they exist in 6.2 NC(if they moved).–
Cheers,
AdamQNX Software Systems Ltd.
[ > amallory@qnx.com > ]With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
“Sreekanth” <> sreekanth@cambira.com> > wrote in message
news:agd97g$3gp$> 1@inn.qnx.com> …
Hi,
I migrated from 6.1 to 6.2 Nc.Now i find that most of my build
(nearly
70% of the tree) fails.Possibly because some of the definitions have
been
moved around.Is there a way that i can work around this without having
to
patch my old code.? If somebody could tell me what all changed in terms
of
library and header file organization that would be great.Thanks
Sreekanth
\
6.2.0 is a major release. Minor releases have just the last number changed.
6.2.1 would be the next minor release.
“Sreekanth” <sreekanth@cambira.com> wrote in message
news:agf3ap$evd$1@inn.qnx.com…
Adam,
My general assumption was that since it is not a major
release(I
think it is mainly bug fixes) from 6.1 to 6.2 everything would work if i
just recompile my sources.I have found out the places where my build is
breaking and i have patched up in some locations.But I am unable to do so
in
many places because it is too cumbersome and i am wary of the fact that i
might introduce bugs while trying to fix the build.Also my build is
complaining about some missing C++ libraries.It is not clear to me from
the
release notes whether the CPP libraries are part of NC version or they
come
only with the Professional edition.Could you guide me with that?Thanks
Sreekanth
“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:ageseg$eo1$> 1@nntp.qnx.com> …
I think if you posted the symbols you’re looking for someone would be
able
to tell you where/if
they exist in 6.2 NC(if they moved).–
Cheers,
AdamQNX Software Systems Ltd.
[ > amallory@qnx.com > ]With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net
“Sreekanth” <> sreekanth@cambira.com> > wrote in message
news:agd97g$3gp$> 1@inn.qnx.com> …
Hi,
I migrated from 6.1 to 6.2 Nc.Now i find that most of my build
(nearly
70% of the tree) fails.Possibly because some of the definitions have
been
moved around.Is there a way that i can work around this without having
to
patch my old code.? If somebody could tell me what all changed in
terms
of
library and header file organization that would be great.Thanks
Sreekanth
\