Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!att!ucbvax!PAN.SSEC.HONEYWELL.COM!thompson
From: thompson@PAN.SSEC.HONEYWELL.COM (John Thompson)
Newsgroups: comp.sys.apollo
Subject: re: Undefined Global
Message-ID: <9105211443.AA13056@pan.ssec.honeywell.com>
Date: 21 May 91 14:43:36 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 38




> After a system crash, when we tried to boot up, the following message
> appears:
> 
> 	undefined global "ldexp" in /install/ri.apollo.os.v.10.3/lib/libc
> 
> We tried renaming as well as deleting libc and rebooting it with essentially
> the same results. This  time the undefined global was found at another 
> location. Another libc was found under /lib directory and we copied it to
> the /install/........./lib directory but the result was the same.
The problem is almost certainly _NOT_ libc.  libc is referencing a global,
and it isn't defined.  That points to a different library that should have 
been loaded already.

Check your /lib directory with the Aegis '/com/ld //node/lib -a' command.
This will tell you if there's a library name there that has no attributes
(file name present, but no file).  If you find one with 'attributes unknown',
then get a good copy from another node.

If this doesn't fix it, you're probably missing an entire file + filename.
Check your /lib directory out against a known good node at the same O/S
(and preferably DN3000).  Libraries that aren't in your /lib directory
are good candidates.

I'm sorry that I don't know which directory has 'ldexp'.  If someone does,
then perhaps they could make life easier on you.


-- jt --
John Thompson
Honeywell, SSEC
Plymouth, MN  55441
thompson@pan.ssec.honeywell.com

When in danger, when in doubt --
run in circles, scream and shout.