- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ANSI C compiler package question..
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2004 08:56 AM
02-19-2004 08:56 AM
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!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2004 09:29 AM
02-19-2004 09:29 AM
Re: ANSI C compiler package question..
[ 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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2004 09:31 AM
02-19-2004 09:31 AM
SolutionI have gotten quite a bit of software like that. It's much easier than ordering the CDs and waiting on them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2004 09:56 AM
02-19-2004 09:56 AM
Re: ANSI C compiler package question..
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2004 10:08 AM
02-19-2004 10:08 AM
Re: ANSI C compiler package question..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2004 02:18 AM
02-20-2004 02:18 AM
Re: ANSI C compiler package question..
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2004 02:22 AM
02-20-2004 02:22 AM
Re: ANSI C compiler package question..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2004 02:23 AM
02-20-2004 02:23 AM
Re: ANSI C compiler package question..
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 as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2004 04:36 AM
02-20-2004 04:36 AM
Re: ANSI C compiler package question..
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?