Hi kabi, > maybe they are cached in config.cache
Thats what's also wierd. After a config the file does not exist. > however it you use QTDIR or --with-qt these values should be ignored. True. I tried the to: 1. let the auto. detection work, 2. Use the QRDIR 3. Use --with-qt (only, no explicit pointing to lib directories) They all pointed to the same directory. I even put in errenous paths to confirm this. [avifile0.7-0.7.16]$ echo $QTDIR /usr/local/qt [avifile0.7-0.7.16]$ ls /usr/local/qt bin/ doc/ INSTALL MANIFEST README tutorial/ changes-3.0.5 examples/ lib/ mkspecs/ README.QT config.status* extensions/ LICENSE.GPL PLATFORMS src/ config.tests/ FAQ LICENSE.QPL plugins/ tools/ configure* include/ Makefile qmake/ translations/ I addition to this, qt-mt is found, but the multithreading test fails. I take it that compiling Qt produces the mt by defalt (I will check on this). Also, when I do finish the configure, the compile is ok, but link fails. Something is definetly wrong here. I will investigate further. Two more question: 1. How do I disable qt? Do I use --with-qt=false? --disable-qt does not seem to work. 2. How do I install this. The REAME and INSTALL file have different insructions. README says: "make install" and the INSTALL says: "make -j 2 install". Thanx for the reply. Regards, Hugo Ferreira. PS: Sorry about the stupid questions, but I am new to this Linux/video stuff. On Sat, 5 Oct 2002 17:28:35 +0200 Zdenek Kabelac <[EMAIL PROTECTED]> wrote: > On Fri, Oct 04, 2002 at 09:46:20AM +0100, Hugo Ferreira wrote: > > I have set the environement variables and paths explicitly to no avail. > > (It automatcally detects the correct the paths BTW) > > > > Finally I edited the "configure" file and placed a few echos to see what's > > happening. I don't know much about autoconf et al., so this is the only > > way I new how to look at this. > > > > While doing so, misteriously this thing worked. What baffles me is that I > > only added echos and cats. Some of these where even incorrect. It also > > seems that with no changes the compilation and execution of the executable > > does not occur. Testing for the version in resulting output fails of course. > > > > Can anyone give me pointers to find out more about this? > > > maybe they are cached in config.cache - however it you use > QTDIR or --with-qt these values should be ignored. > > bye > kabi > > > > _______________________________________________ > Avifile mailing list > [EMAIL PROTECTED] > http://prak.org/mailman/listinfo/avifile _______________________________________________ Avifile mailing list [EMAIL PROTECTED] http://prak.org/mailman/listinfo/avifile
