Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-unix!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.UUCP
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.windows.x
Subject: Sun, "ld", NFS and ranlib
Message-ID: <11893@teknowledge-vaxc.ARPA>
Date: Fri, 17-Apr-87 11:42:31 EST
Article-I.D.: teknowle.11893
Posted: Fri Apr 17 11:42:31 1987
Date-Received: Sat, 18-Apr-87 06:24:17 EST
Distribution: na
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 22
Keywords: nfs compile link ld ranlib library sun
Xref: utgpu comp.unix.questions:1736 comp.unix.wizards:1786 comp.windows.x:540

We are encountering the following problem with our Sun-3s (SunOS 3.2):

	One non-fileserver node has ranlib'ed /usr/xwindows/lib/libX*.a
	X libraries, but exports /usr for NFS mount.

	Other standalone disked nodes NFS mount the above node's
	/usr/xwindows directory.

	When someone tries to compile and link a program that uses the
	NFS mounted X libraries, "ld" complains that they need to be ranlib'ed.

The workaround we're using is to make local (i.e., non-NFS mounted) copies
of the X libraries and ranlib them locally.  However, I still want to know
(1) why it doesn't work for NFS mounted directories, and (2) if it ought to
work at all.

Thanks in advance,
Mike Khaw
-- 
internet:  mkhaw@teknowledge-vaxc.arpa
usenet:	   {hplabs|sun|ucbvax|decwrl|sri-unix}!mkhaw%teknowledge-vaxc.arpa
USnail:	   Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303