I’ve been able to narrow down an issue where I sometimes don’t get the
development tools installed correctly. If I just check the “Development” box
and let it pull in all that it wants to what happens is that some of the GNU
bin utils (always “ar”, “ranlib”, etc.) and the “libstdc++.a” file will
generate errors when even just doing an “ls” in their directory (ie: “find
/ -mount -print > /dev/null” will spit out errors to stderr). If I go in and
one-by-one install pieces the GNU bin tools will work fine, but pretty
consistantly when I install the “GNU C++ Development” package the error
about “libstdc++.a” (“no such file or directory”) will occur. The error that
the bin tools show is “file name too long”.
I’m booting with the non-DMA kernel, and a dcheck and chkfsys turn up no
errors on the drive media itself. Plus the fact that it is always the same
sets of files that have the errors nomatter what order the rest of the
components get installed in would seem to eliminate the possibility of them
getting installed in the same spot on the disk…
Is this an known error/issue I just didn’t see in the knowledge base, or any
other ideas? I’ll report it as an issue if anyone thinks it should be. The
hardware this is on is a “standard” Dell laptop that otherwise doesn’t seem
to have any issues running RTP and I’ve done multiple fresh installs just to
eliminate the possibility of a single bad install being the source…
Marisa
Narrowing that down further, it seems to be exclusively the “target files
for x86” package under the GNU C++ tools that cause the error… Removing
that eliminates it, reinstalling causes it to reappear. I don’t know why it
causes the error with the GNU bin tools when installed as a entire group…
Marisa
Marisa Giancarla <mgiancarla@macromedia.com> wrote:
Hello,
What version of QNX RTP do you have? (“uname -a”)
Regards,
Marcin
Narrowing that down further, it seems to be exclusively the “target files
for x86” package under the GNU C++ tools that cause the error… Removing
that eliminates it, reinstalling causes it to reappear. I don’t know why it
causes the error with the GNU bin tools when installed as a entire group…
Marisa
“Marcin Dzieciol” <marcind@qnx.com> wrote in message
news:93fhec$fub$1@nntp.qnx.com…
Marisa Giancarla <> mgiancarla@macromedia.com> > wrote:
Hello,
What version of QNX RTP do you have? (“uname -a”)
uname -a gives:
“QNX localhost 6.00 2000/09/13-14:09:41edt x86pcx86”
Marisa
Marisa Giancarla <mgiancarla@macromedia.com> wrote:
Hello Marisa,
“Marcin Dzieciol” <> marcind@qnx.com> > wrote in message
news:93fhec$fub$> 1@nntp.qnx.com> …
Marisa Giancarla <> mgiancarla@macromedia.com> > wrote:
Hello,
What version of QNX RTP do you have? (“uname -a”)
uname -a gives:
“QNX localhost 6.00 2000/09/13-14:09:41edt x86pcx86”
I have just installed “clean” QNX RTP (same as yours).
Then I installed from package manager ALL Development section
from the CD in one shot. Everything works fine, ar and other
utillities exist, doing find / -mount -print, in /usr/lib, didn’t
return any errors. Can you be more specific, what do I have to
do to reproduce the problem.
regards,
Marcin
\
Marisa
“Marcin Dzieciol” <marcind@qnx.com> wrote in message
news:93i9mf$5ir$1@nntp.qnx.com…
Marisa Giancarla <> mgiancarla@macromedia.com> > wrote:
I have just installed “clean” QNX RTP (same as yours).
Then I installed from package manager ALL Development section
from the CD in one shot. Everything works fine, ar and other
utillities exist, doing find / -mount -print, in /usr/lib, didn’t
return any errors. Can you be more specific, what do I have to
do to reproduce the problem.
Hmm, for me every time I install the GNU C++ “x86 target files” I get the
problem whether installed as part of a set or individually, and removing
that package corrects it… The gnu bin tools only seem to get corrupted when
installing all as a set as once…
Marisa