c0redump@skreel.org wrote:
 > oh, well. so if it didn't find qt, it may be due to the fact
 > that you already launched the script configure with no options.
 > Doing that will give the variable QTDIR something inexistant in
 > config.cache. When you recall configure with -qt-dir=... , it
 > still reads config.cache, and telling configure where QT is
 > doesn't override the previous config. so remove config.cache,
 > and retry. i may be wrong of course

I tried that, no joy. So where does configure expect to find qt2 
and why not symlink it so this problem goes away?




-- 
Paul Beard
8040 27th Ave NE
Seattle WA 98115
206 529 8400

Deliberation, n.:
	The act of examining one's bread to determine which side it is
buttered on.
		-- Ambrose Bierce, "The Devil's Dictionary"