Path: utzoo!attcan!uunet!cs.utexas.edu!oakhill!abair
From: abair@turbinia.oakhill.uucp (Alan Bair)
Newsgroups: comp.windows.x
Subject: Re: difficulty installing in other than /usr/[bin,lib,include]/X11
Message-ID: <ABAIR.89Nov21013728@turbinia.oakhill.uucp>
Date: 21 Nov 89 07:37:28 GMT
References: <29336@shemp.CS.UCLA.EDU>
Sender: news@oakhill.UUCP
Organization: SPS CAD, Motorola Inc., Austin, Texas.
Lines: 63
In-reply-to: wine@maui.cs.ucla.edu's message of 20 Nov 89 16:11:39 GMT

In article <29336@shemp.CS.UCLA.EDU> wine@maui.cs.ucla.edu (David Wine) writes:

   I tried to make X to sit in /n/color/share/usr/bin/X11R3, with
   the obvious lib and include libraries.  I used the site.def file
   which follows and made the World.  To install I did
   make DESTDIR=/n/color/share install.  The files all went to
   the expected places (/n/color/share/usr/.../X11R3/...) but
   X can't find its fonts.  What did I do wrong?

   --David

(deleted code)
   #ifndef DestDir
   #define DestDir /* as nothing */
   #endif
   #ifndef UsrLibDir
   #define UsrLibDir $(DESTDIR)/usr/lib
   #endif
   #ifndef BinDir
   #define BinDir $(DESTDIR)/usr/bin/X11R3
   #endif
   #ifndef IncDir
   #define IncDir $(DESTDIR)/usr/include/X11R3
   #endif
   #ifndef LibDir
   #define LibDir $(USRLIBDIR)/X11R3
   #endif

I wanted to do a similar thing.  Install the code in /usr/local/..., mount
/usr/local on all the nodes and use the appropriate -I/... options when
compiling.  This looked a lot easier to maintain, instead of creating links
in /usr/include & /usr/lib on our nodes.  It does work.

I think the problem you are having and why the install notes strongly suggest
you use the link method, is due to certain uses of the xxxDir defines above.
I know that at least the LibDir define is used in compiling certain X
functions, so it knows where the X library is.  So when you try to do what
you did, without the links, some of the code looks in /usr/bin/X11R3 for
example.  There is no link from here to where the code actually is, so it
fails.

I solved this by coding in the complete path for the defines.  Now the path
is in the compiled code and it gets installed where it will be looked for.
This does violate the suggestions, but I think it is a lot cleaner, especially
in a networking environment like I am in.

One other point, which I think is what the link suggestion was for.  I am
starting to run out of space in the /usr/local filesystem, so I may have
to keep the code somewhere else.  Well with my method I can still handle that.
I move the code from /usr/local to somewhere else and put links in place.
However, now I only have to make the links in one place and if I used a
commonly mounted filesystem for the alternate location , I do not even have
to update any mountings.  I suppose I could even use the DESTDIR method to
install in the new location.

Hope this helps.  If anyone else has a better idea, please let me know.


--
Alan Bair
SPS CAD                   Logic Simulation & Test
Motorola, Inc.            Austin, Texas
...!cs.utexas.edu!oakhill!turbinia!abair