[PATCH modular 1/4] build.sh: remove CACHE env variable as it is not implementable

[Gaetan Nadon]

On Mon, 2010-12-13 at 11:11 -0500, Trevor Woerner wrote:

> Wouldn't that suggest there's a mistake in one or both of these
> settings?
> 
> They're both looking in the same directory ($HOME/xorg/src/lib) so
> that's a good thing. But if clock only requires "-lXft" but xdm
> requires all of "-lXft", "-lXrender", and "-lX11" then maybe
> something's wrong with how both projects setup the "pkg_cv_XFT_LIBS"
> variable?
> 

The name of the variable is purely arbitrary. It means different things
to different modules. I don't really understand how this Autoconf
feature can be useful. Perhaps if the modules configuration is very
vanilla, things like CC don't change so you get some benefit. Maybe
there is something I don't understand. 

http://www.gnu.org/software/automake/manual/autoconf.html#Caching-Results

It looks to me that this feature made the assumptions that there would
be no name clashing. Thanks for looking into this, I need to be
convinced it is safe to use.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.x.org/archives/xorg-devel/attachments/20101213/8d40f7f9/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg-devel/attachments/20101213/8d40f7f9/attachment.pgp>