Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!rice!uupsi!sunic!news.funet.fi!hydra!poros!kankkune
From: kankkune@cs.Helsinki.FI (Risto Kankkunen)
Newsgroups: comp.windows.x
Subject: Re: Small problem with mkfontdir when building X11R4.18
Message-ID: <8321@hydra.Helsinki.FI>
Date: 2 Nov 90 17:01:52 GMT
References: <8307@hydra.Helsinki.FI>
Sender: news@cs.Helsinki.FI
Organization: University of Helsinki, Department of Computer Science
Lines: 19


I was having some problems to build the font directories. Casper Dik
and Vick Khera pointed to me that this was due to a known bug in the
mkfontdir's Imakefile. I had completely forgotten that the -B switch
doesn't mean the same thing in gcc and cc.

I would have thought that this bug had been corrected in one of the
18 fixes...

However, the second point is still valid. Is it a good practice to
compile the programs so that they get these bogus library paths in
their executable? I think you could build the release by specifying
the paths only in LD_LIBRARY_PATH. After all, now that I am testing
the release (and haven't yet installed it), that is the only way to
get those programs started (I don't want to cd to the programs home
directories all the time).
 Risto Kankkunen                   kankkune@cs.Helsinki.FI (Internet)
 Department of Computer Science    rkankkunen@finuh         (Bitnet)
 University of Helsinki, Finland   ..!mcvax!uhecs!kankkune   (UUCP)