From: Darryl Cook (dlc@cs.appstate.edu)
Date: Mon Nov 17 2003 - 07:44:21 EST
Well thanks to Dr. Blinn, we finally got to the bottom of the ld
problems. It turns out that the mount command in /sbin and /usr/sbin is
different. Somehow the /usr/sbin/mount command had been copied to /sbin
either through the patches or through user error. It looks for
libraries etc in the /usr filesystems which isnt available at boot time
since they arent mounted. After copying back in the right copy from
backup, everything is back to normal now. Thanks for all the responses!
darryl
Original problem:
Im running Tru64 5.1b on an Alpha ES40. I was forced to reboot this
morning and booted into single user mode to fix some things. As always
I ran mount -a -t advfs so as to boot all the local file systems and
none of the nfs filesystems. I received an error message from ld
complaining that it couldnt find the ldcdrom.so library. Nothing but /
was mounted as well. I booted into multiuser mode and everything went
fine. I did a man on ld and see that it should be looking in /usr/shlib
among a few other directories as the default. The ldcdrom.so file is
in /usr/shlib as it should be but apparently ld isnt looking there.
Im sure that there is a file that contains the default paths for ld to
look in.....can someone point me to that file please so I can verify
that it isnt corrupted or hasnt been changed? Is there any way to tell
what directories ld is going to look in? ( I know where it is supposed
to look but is there a way to verify that it is indeed looking there)?
thanks for any info
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:44 EDT