riazm@cs.tamu.edu (Riaz Mohammad) (05/21/91)
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 result is the compilation processes of some of the C programs are affected. Any suggestions? Thanks ps I'm a novice sys adm of a stand alone Domain 3000 m/c and its *not* on a network -- Riaz Mohammad. Institute for Innovation & Design in Engineering Texas A&M University Internet:riazm@cs.tamu.edu College Station, Tx 77840 YellNet: 409-268-1493
thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) (05/21/91)
> 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.
rees@pisa.citi.umich.edu (Jim Rees) (05/22/91)
In article <9105211443.AA13056@pan.ssec.honeywell.com>, thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) writes:
I'm sorry that I don't know which directory has 'ldexp'. If someone does,
then perhaps they could make life easier on you.
'xesa' will tell you... Oops, looks like 'xesa' isn't part of standard
software, and regular 'esa' only gives the address. Anyway, 'ldexp' is in
syslib. Note that the version of syslib you use depends on what kind of
node you have, but these days it's usually syslib.881.beierl_c@apollo.HP.COM (Christopher Beierl) (05/22/91)
In article <9105211443.AA13056@pan.ssec.honeywell.com> thompson@PAN.SSEC.HONEYWELL.COM (John Thompson) writes: >> 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 >... >I'm sorry that I don't know which directory has 'ldexp'. If someone does, >then perhaps they could make life easier on you. For what it's worth, "ldexp" lives in /lib/syslib (or /lib/syslib.xxx) -Chris =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Christopher T. Beierl Internet: beierl_c@apollo.hp.com User Interface Technology Division / East Phone: (508) 256-6600 x4054 Hewlett-Packard, Inc. HP-Telnet: 256-4054
vinoski@apollo.HP.COM (Stephen Vinoski) (05/22/91)
ldexp is in /lib/syslib.881. -steve | Steve Vinoski (508)256-0176 x5904 | Internet: vinoski@apollo.hp.com | | HP Apollo Division, Chelmsford, MA 01824 | UUCP: ...!apollo!vinoski |