Hello,
I am just starting the conversion from QNX4 to Nto. For
my own sanity I am porting TCSH to Neutrino… - I don’t
feel like rewriting all my scripts for bash.
I have some basic questions regarding the changeover.
-
what is the NTO specific #define?
i.e. in QNX4 you could use QNX for QNX only code I would like to make my code changes such that I can still compile under QNX4 –
-
Is there a general invocation to configure that should be used when porting to NTO? I have gotten the latest config.guess and config.sub off the gnu.org site – Now I get a “x86-pc-nto-qnx” system which is unsupported in the configure script… I don’t have a problem adding that type to the configure script - But I don’t want to add a non-standard machine… Should I get a pre-ported app and see what someone else has done… if so what is the canonoical port?
Any other suggestions would be welcome
Bill
Previously, Markus Loffler wrote in qdn.public.qnxrtp.devtools:
NTO defines QNXNTO
Thanks, that is what I wanted to know – But where did you find this from… it is not in the help system at least by searching for QNXNTO
– it is not under qcc or gcc…
<…time passes…>
– now that I know what to look for I can find it in header files in /usr/include.
<…time passes…>
– OK it is the migration kit under the “Development Environment”
section - but you will find it only if you search for QNXNTO
QNXNTO finds nothing… then again if you knew to search for QNXNTO
you wouldn’t need to find it at all…
I know this is a just being released but this really should be documented in the help for the qcc or gcc… or at least a link from there to information in the migration kit. i.e a See Also
Thanks,
Bill
Watcom defines WATCOMC
GNU defines GNUC
But beware:
NTO defines QNX
QNX defines QNX
so to test for QNX now you have to test if defined(QNX) &&
!defined(QNXNTO)
“AII Development” <> derbyw@derbtronics.com> > wrote in message
news:Voyager.001017102726.552975A@dev98…
Hello,
I am just starting the conversion from QNX4 to Nto. For
my own sanity I am porting TCSH to Neutrino… - I don’t
feel like rewriting all my scripts for bash.
I have some basic questions regarding the changeover.
-
what is the NTO specific #define?
i.e. in QNX4 you could use QNX for QNX only code I would like to make
my code changes such that I can still compile under QNX4 –
-
Is there a general invocation to configure that should be used when
porting to NTO? I have gotten the latest config.guess and config.sub off the
gnu.org site – Now I get a “x86-pc-nto-qnx” system which is unsupported in
the configure script… I don’t have a problem adding that type to the
configure script - But I don’t want to add a non-standard machine… Should I
get a pre-ported app and see what someone else has done… if so what is the
canonoical port?
Any other suggestions would be welcome
Bill
\
x86-pc-nto-qnx is the correct system name.
Have you tried regenerating your configure with autoconf?
AII Development <derbyw@derbtronics.com> wrote:
Hello,
I am just starting the conversion from QNX4 to Nto. For
my own sanity I am porting TCSH to Neutrino… - I don’t
feel like rewriting all my scripts for bash.
I have some basic questions regarding the changeover.
-
what is the NTO specific #define?
i.e. in QNX4 you could use QNX for QNX only code I would like to make my code changes such that I can still compile under QNX4 –
-
Is there a general invocation to configure that should be used when porting to NTO? I have gotten the latest config.guess and config.sub off the gnu.org site – Now I get a “x86-pc-nto-qnx” system which is unsupported in the configure script… I don’t have a problem adding that type to the configure script - But I don’t want to add a non-standard machine… Should I get a pre-ported app and see what someone else has done… if so what is the canonoical port?
Any other suggestions would be welcome
Bill
–
cburgess@qnx.com
NTO defines QNXNTO
Watcom defines WATCOMC
GNU defines GNUC
But beware:
NTO defines QNX
QNX defines QNX
so to test for QNX now you have to test if defined(QNX) &&
!defined(QNXNTO)
“AII Development” <derbyw@derbtronics.com> wrote in message
news:Voyager.001017102726.552975A@dev98…
Hello,
I am just starting the conversion from QNX4 to Nto. For
my own sanity I am porting TCSH to Neutrino… - I don’t
feel like rewriting all my scripts for bash.
I have some basic questions regarding the changeover.
-
what is the NTO specific #define?
i.e. in QNX4 you could use QNX for QNX only code I would like to make
my code changes such that I can still compile under QNX4 –
-
Is there a general invocation to configure that should be used when
porting to NTO? I have gotten the latest config.guess and config.sub off the
gnu.org site – Now I get a “x86-pc-nto-qnx” system which is unsupported in
the configure script… I don’t have a problem adding that type to the
configure script - But I don’t want to add a non-standard machine… Should I
get a pre-ported app and see what someone else has done… if so what is the
canonoical port?
Any other suggestions would be welcome
Bill
AII Development <derbyw@derbtronics.com> wrote:
: I know this is a just being released but this really should be documented
: in the help for the qcc or gcc… or at least a link from there to
: information in the migration kit. i.e a See Also
So many people expect the docs to emerge full-grown, like Athena from her
father’s forehead…
I’ll add this to the list. Thanks.
Steve Reid stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems Ltd.
Sorry,
That came out a little stronger than I intended.
Actually I don’t expect them to be done en-mass –
But it is frustrating to flounder about for hours knowing
it’s in there… somewhere… 
Bill
Steve Reid wrote in message <8si7ta$2ur$1@nntp.qnx.com>…
AII Development <> derbyw@derbtronics.com> > wrote:
: I know this is a just being released but this really should be documented
: in the help for the qcc or gcc… or at least a link from there to
: information in the migration kit. i.e a See Also
So many people expect the docs to emerge full-grown, like Athena from her
father’s forehead…
I’ll add this to the list. Thanks.
Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems Ltd.
Previously, Bill Derby wrote in qdn.public.qnxrtp.devtools:
Sorry,
That came out a little stronger than I intended.
Actually I don’t expect them to be done en-mass –
But it is frustrating to flounder about for hours knowing
it’s in there… somewhere… >
Bill
Steve Reid wrote in message <8si7ta$2ur$> 1@nntp.qnx.com> >…
AII Development <> derbyw@derbtronics.com> > wrote:
: I know this is a just being released but this really should be documented
: in the help for the qcc or gcc… or at least a link from there to
: information in the migration kit. i.e a See Also
So many people expect the docs to emerge full-grown, like Athena from her
father’s forehead…
I’ll add this to the list. Thanks.
Steve Reid > stever@qnx.com
TechPubs (Technical Publications)
QNX Software Systems Ltd.
\
Unlike I really interested by these informations, because I plan to port man distribution to QRTP and I have to modify somethings in sources and headers to compile succesfully, we have to admit that it doesn’t belong to QNX (maybe !?) to give informations to write portable (at least UNIX) applications or to port UNIX apps to QRTP.
BUT, QNX supplies Xphoton so, as they made a step in this way, they have to continue!! (joke and I want to seize the opportunity of this article to thanks QNX and the developpers of Xphoton it’s a very interesting feature).
Anyway, if anybody knows where we can find information on how to port apps in the right way, I’m intersted (maybe at www.gnu.org, I’m going to see).
Alain.
Which version of man are you porting? The netbsd man and groff 1.16
already come with the RTP.
Unlike I really interested by these informations, because I plan
to port man distribution to QRTP and I have to modify somethings
in sources and headers to compile succesfully, we have to admit
that it doesn’t belong to QNX (maybe !?) to give informations to
write portable (at least UNIX) applications or to port UNIX apps
to QRTP. > BUT, QNX supplies Xphoton so, as they made a step in
this way, they have to continue!! (joke and I want to seize the
opportunity of this article to thanks QNX and the developpers of
Xphoton it’s a very interesting feature).
Anyway, if anybody knows where we can find information on how to
port apps in the right way, I’m intersted (maybe at > www.gnu.org> ,
I’m going to see).
Alain.
–
cburgess@qnx.com
Previously, Colin Burgess wrote in qdn.public.qnxrtp.devtools:
Which version of man are you porting? The netbsd man and groff 1.16
already come with the RTP.
Unlike I really interested by these informations, because I plan
to port man distribution to QRTP and I have to modify somethings
in sources and headers to compile succesfully, we have to admit
that it doesn’t belong to QNX (maybe !?) to give informations to
write portable (at least UNIX) applications or to port UNIX apps
to QRTP. > BUT, QNX supplies Xphoton so, as they made a step in
this way, they have to continue!! (joke and I want to seize the
opportunity of this article to thanks QNX and the developpers of
Xphoton it’s a very interesting feature).
Anyway, if anybody knows where we can find information on how to
port apps in the right way, I’m intersted (maybe at > www.gnu.org> ,
I’m going to see).
Alain.
–
cburgess@qnx.com
Oups !!!
Where is it?
I made a full install and when I type find / -name man, I get:
/pkgs/repository/qnx/binutils/core-2.9.1/usr/man
/pkgs/repository/qnx/gcc/core-2.95.2/usr/man
/pkgs/repository/qnx/ddd/core3.2/usr/man
/pkgs/base/qnx/os/utils2.1/usr/man
which only are directories.
I was trying to port man-1.5g
Alain.
They aren’t in the base package though.
/pkgs/repository/bsd/netbsd-man from “Public Software/BSD/Netbsd Man”
/pkgs/repository/gnu/groff from “Public Software/Gnu Utilities/Groff”
–
cburgess@qnx.com