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

Alan Coopersmith alan.coopersmith at oracle.com
Mon Dec 13 16:37:04 PST 2010

Trevor Woerner wrote:
> On Mon, Dec 13, 2010 at 7:03 PM, Gaetan Nadon <memsize at videotron.ca> wrote:
>> The resulting variables XORG_CFLAGS and XORG_LIBS are unique to each package
>> and hold different values.
>> This is where I think the concept of a cache does not hold. The last write
>> wins and if you pick a random
>> package to rebuild, it will pick the value written last.
> Ah okay, I think I see where you're going. In my original email I was
> trying to say: "maybe all the variables between all the packages
> should be coordinated so they don't clash" but seeing how huge of a
> job that would be it's probably much safer this way. I'm guessing it's
> probably not being used by many people, and I'm all for getting rid of
> clutter :-)

We tried that early on in modularization for all the libraries and apps,
which is why they have strangely worded configure messages such as:

checking for ICO... yes

when you're building ico (it should really be "checking for the packages that
ICO needs"), due to commits such as:

Unfortunately, it doesn't seem to have been consistently applied or kept up.

	-Alan Coopersmith-        alan.coopersmith at oracle.com
	 Oracle Solaris Platform Engineering: X Window System

More information about the xorg-devel mailing list