I'm having some difficulty installing gcc 2.95.1 from the "jazz"
distribution -- I tried e-mailing Mark directly, but it seems my provider
has been "blacklisted" by ORBS...

So, actually my first question is which version SHOULD I be interested in?
Per the Jazz website at http://jazz.external.hp.com/src/gnu/gnuframe.html,
there are three versions:

 "egcs" 2.91.57 for 5.5 & 6.0
 "gcc" 2.95.1 for 6.0 as is "thread safe"
 "gcc" 2.95.2 for 6.0 and is NOT "thread safe" -- from the download page:

   "The g++ in this version does not produce thread safe exception handling
code. If you know you need the thread safe exception handling, use the
2.95.1 version."

I presume I want the latest version, BUT I know I want to experiment with
"threaded" programs, so I'm thinking I need 2.95.1.  Of course, now that I
re-read the warning on that page, I see it is talking about "g++" in
particular, not C or C++, however, wouldn't a problem like that effect ALL
of the compiled output?

But that's a tangent to the problem -- I have a fresh install of MPE/iX 6.0,
downloaded and de-tarred the gnucore & related files, ran through the
installation instructions, and even the simplest compile [the old faithful
"hello world"] fails with "cannot execute cpp - no such file" (or words to
that effect)

Realizing that the "problem" was the missing routine, I downloaded and
de-tarred the 2.95.2 version, then using the ;KEEP option on the restore, I
restored /usr/local/bin/@ -- two files were "found" that didn't exist from
the 2.95.1 installation: cpp & ld.

Thinking I had "solved" the problem, I tried a compile.  SEVERAL minutes
later, the compile bombs out with a bounds violation.  Well, the first
problem (in my mind) was the bounds violation -- I'd get to the fact that it
takes a couple MINUTES to compile "hello world" on an otherwise dormant
machine later...

but, curiosity won out and I added the "-v" flag to the gcc command (shows
"what the compiler runs")  Turns out it was caught in some sort of loop
where gcc invoked cpp, and cpp re-called cpp over and over [and expanding
the "parameter" line as it went]  This explained almost everything -- why it
took a while to bomb out, and that it bombed out because the command-line
was too big...  It also showed that gcc was version 2.95.1, but cpp was
2.95.2, so I thought that might be a possible cause of this problem
[mismatched versions]

That's when I remembered that a lot of gnu/linux "utilities" act or re-act
based on their OWN program name -- so I copied "gcc" to "cpp" and tried
again -- success at last!

However, that success was short lived -- this ONLY worked for MANAGER.SYS,
when I logged on as my "normal" user ID, the exact same compile command went
into the aforementioned loop...

So now I'm stuck with this dilemma: should I try to fully install version
2.95.2, or have I missed some all-important "permissions" setting on this
"copy" of gcc-as-cpp? [I even tried a symbolic link from cpp to gcc, same
problem...]  Is there a way to install BOTH versions simultaneously?  Or,
considering the vastly different installation methods, does 2.95.1 need to
be "uninstalled" before installing 2.95.2? [and if so, how?]

Tom Emerson
Sr. Systems Analyst
NDC | e COMMERCE
[log in to unmask]
626-258-4309
626-350-3832 FAX