Very Computer

by **John Barr** » Fri, 29 Sep 2000 04:00:00

Hi, All.

Just installed IBM's c for AIX v5 on AIX 4.3.3. Now we want/need c++
compiler there.

It seems that the latest c++ compiler for AIX would be the VisualAge v5.

Must we then order the VisualAge compiler and use it totally in lieu of "c
for AIX" (besides for c++)? Or can the two coexist?

TIA,
John

by **John McQu** » Sat, 30 Sep 2000 04:00:00

John,

Please see other notes about Visual Age C++ and the IBM C++ interms of what's
current & what's supported.

The Visual Age C++ package comes with a seperatly installable C compiler.
There's nothing to stop you retaining your existing C compiler other than it
not being 100% upto date. But as you mention V5 I suspect this is actually the
Visual Age product or at least the C part of it. Does it install in /usr/vac,
what is the lslpp output, lslpp -l vac.C

From a co-existance point of view you'll need to watch which file extensions
use which binaries, in your makefiles and also which symbolic links in
/usr/bin point to which real binaries in either /usr/vacpp/bin for the Visual
Age C++ product and /usr/lpp/xlC.

Being honest though, given that the Visual Age C Compiler is sort of bundled
with the C++ one it would be easier all round just to use it. IBM have a *
habit of avoiding support issues when you aren't at the current level of
anything.

Kindest Regards

John McQue

> Hi, All.

> Just installed IBM's c for AIX v5 on AIX 4.3.3. Now we want/need c++
> compiler there.

> It seems that the latest c++ compiler for AIX would be the VisualAge v5.

> Must we then order the VisualAge compiler and use it totally in lieu of "c
> for AIX" (besides for c++)? Or can the two coexist?

> TIA,
> John

by **John Barr** » Sat, 30 Sep 2000 04:00:00

Hi, John.

That's what I suspected. (You seem to have to do lots of things with AIX on
suspicion, no?) What with the package labelled as vac (VisualAge c?).
lslpp says our vac.C is 5.0.1.0. Not related to xlC, it seems.

So it looks like the c compiler we have is a subset of the c & c++ package,
and that we should just upgrade/trade-in whatever the c for aix distrib, for
VisualAge. Or end up having to buy both. Live and learn.

Regards,
John B.

So it

> John,

> Please see other notes about Visual Age C++ and the IBM C++ interms of
what's
> current & what's supported.

> The Visual Age C++ package comes with a seperatly installable C compiler.
> There's nothing to stop you retaining your existing C compiler other than
it
> not being 100% upto date. But as you mention V5 I suspect this is actually
the
> Visual Age product or at least the C part of it. Does it install in
/usr/vac,
> what is the lslpp output, lslpp -l vac.C

> From a co-existance point of view you'll need to watch which file
extensions
> use which binaries, in your makefiles and also which symbolic links in
> /usr/bin point to which real binaries in either /usr/vacpp/bin for the
Visual
> Age C++ product and /usr/lpp/xlC.

> Being honest though, given that the Visual Age C Compiler is sort of
bundled
> with the C++ one it would be easier all round just to use it. IBM have a
*
> habit of avoiding support issues when you aren't at the current level of
> anything.

> Kindest Regards

> John McQue

> > Hi, All.

> > Just installed IBM's c for AIX v5 on AIX 4.3.3. Now we want/need c++
> > compiler there.

> > It seems that the latest c++ compiler for AIX would be the VisualAge v5.

> > Must we then order the VisualAge compiler and use it totally in lieu of
"c
> > for AIX" (besides for c++)? Or can the two coexist?

> > TIA,
> > John

Very Computer

c, c++ on AIX 4.3.3

c, c++ on AIX 4.3.3

c, c++ on AIX 4.3.3

c, c++ on AIX 4.3.3