ANSI C compiler package question..

[Mark Stewart]

I am having a problem with my ANSI C compiler and it sounds like I'm going to have to reinstall it.

Basically(in case anyone knows something more about what could be causing this), it started - out of nowhere - reporting the following error when trying to use the "cc" command:

unrecognized HP-UX version: B.11.00 (assuming 10.0 filesystem)

/opt/ansic/lbin/ccom: checksum error

/pt/ansic/bin/cc: unable to unlock compiler

/opt/ansic/bin/cc: Try running /opt/ansic/bin/cc on the server

I found all of this weird, since there really isn't a server, and this is an 11.00 machine - which the software should run fine on. The checksum part made me think it was a licensing error, but the licensing support center says nothing should have changed at all since it's a permanent license.

I don't seem to see a CD for this around my office anywhere either. Is this already packaged in the HP-UX cd's and I just use the code word to unlock it? I put this on a long while ago and am drawing a blank as to where I installed it from. Thanks!

[Patrick Wallek]

It sounds like somehow part of your directories got corrupted. Here is a listing from one of my machines with Ansi C installed:

[ root@hqued02:/opt/ansic/lbin ]
# ll
total 22508
dr-xr-xr-x 2 bin bin 1024 Oct 10 2002 ./
dr-xr-xr-x 10 bin bin 1024 Oct 10 2002 ../
-r-xr-xr-x 1 bin bin 11395072 Sep 20 2001 ccom*
-r-xr-xr-x 1 bin bin 24576 Sep 20 2001 dag*
-r-xr-xr-x 1 bin bin 12288 Sep 20 2001 flip*
-r-xr-xr-x 1 bin bin 57344 Sep 20 2001 lint2*
-r-xr-xr-x 1 bin bin 16384 Sep 20 2001 lpfx*
-r-xr-xr-x 1 bin bin 16384 Sep 20 2001 nmf*
[ root@hqued02:/opt/ansic/lbin ]
# cksum *
4205941423 11395072 ccom
161667668 24576 dag
522606262 12288 flip
3172547308 57344 lint2
3152431806 16384 lpfx
3814974741 16384 nmf
[ root@hqued02:/opt/ansic/lbin ]
# swlist -l product | grep -i ansi
C-ANSI-C B.11.11.04 HP C/ANSI C Compiler


What version are you running? Check your /opt/ansic/lbin directory and see what it looks like. Do you have a tape you can restore from?

[Patrick Wallek · Accepted solution]

To answer your other question -- Yes, Ansi C is on the normal applications CDs. If you have a support contract linked to your ITRC id, you can also download it by going to http://itrc.hp.com making sure you sign in, go to SUM (Software Update Manager), select your system and browse through the updates.

I have gotten quite a bit of software like that. It's much easier than ordering the CDs and waiting on them.

[Mark Stewart]

I checked my lbin against yours and I do have the same files. I have different sizes for mine though and the checksums are different(as I would expect..). My version number is also different. I have B.11.01.01 installed.

Unfortunately, this portion of this workstation wasn't part of the backup strategy employed in the past(that's what I just got done fixing). So there is no older version to revert to.

I also don't have an HP Support Contract linked to my account, that I know of. I don't even think I have an HP Support Contract currently. That pesky applications CD must be around here somewhere though.. I guess I could reinstall from that, use the codeword I already have, and then add any updates/patches available and hopefully be ok, correct?

[Patrick Wallek]

As long as the codeword you have is for the specific set of application CDs you have you will be OK. If the codeword does not match the application CDs, you will have problems.

[Mark Stewart]

is the codeword corresponding to a specific CD or to a specific version?

the reason I ask is that I have two sets from March 2001, and two sets December 2001. I have no idea which one of the 4 I installed this from originally. Does it matter? Is there a way to figure out which it was that I used, if it does matter?

[Patrick Wallek]

The codeword is keyed to a specific SET of CDs. As far as I know if the codeword is generated for March 2001 Application CDs, then it should work on ANY March 2001 set of CDs, but definitely would NOT work on Dec. 2001 Application CDs.

[A. Clay Stephenson]

The codewords don't apply to a specific CD but they do apply to a specific CD Part No printed on the CD. For example, if the codeword applies to a Mar '01 CD Set then any
Disk1, for example, of any Mar '01 Application CD Set will work. If the codeword is correct then the package will be "visible" to swinstall otherwise it remains hidden.

[Mark Stewart]

got it installed.. seems to be working properly now..

i still have no idea how this got screwed up in the first place, but at least it's good to go now.

Are there any patches I should be adding to this?

Also, while I tested it, I got a cc warning that was strange:

cc:487:warning:Possibly incorrect message catalog

anyone know what that relates to?