Gary Beckmann <gbeckmann(a)RADIONICS.com> wrote:
So, basically on hpux 10.20 with HP's ansic compiler,
> what `which cc`
/usr/bin/cc:
LINT A.10.32.22 CXREF A.10.32.22
HP92453-01 A.10.32.22 HP C Compiler
/usr/lib/libc: $Revision: 76.3 $
Two things:
1. Upgrade your compiler. I don't know how old this is, but it's old.
If it's not too old (although I suspect it is, as I haven't had any
HP compiler -g problems in years and YEARS), you can probably
download a patch. If it's really old, you may have to buy the
upgrade.
2. Looking at /usr/bin/cc won't necessarily give you useful information,
as it's just a driver program. You need to look at the main compiler
engine -- for example:
$ strings `which cc` | grep ccom
/opt/ansic/lbin/ccom
/ccom
$ what /opt/ansic/lbin/ccom
/opt/ansic/lbin/ccom:
LINT A.10.32.30 CXREF A.10.32.30
HP92453-01 A.10.32.30 HP C Compiler
HP-UX SLLIC/OPTIMIZER UX.10.20.565 (DART45): 03/19/99
Ucode Code Generator - UX10.20.70 (DART45 IZ3) (PACG_UX10)
REV: HP SESD Code
High Level Optimizer - UX.10.21.990303 (UX10.MULTI) [-DHLO_RELEASE +O3] -
01-Apr-99.12:31
/usr/lib/libc: $Revision: 76.3 $
[ Wow. 1999 -- and I've got a pretty "up-to-date" compiler, if not
the absolute latest for HP-UX 10.20. ;-( ]
--
Darryl Okahata
darrylo(a)soco.agilent.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.