Boy I do not care if you post it on the web or not, but your g#$ [EMAIL PROTECTED]
configure script has serious problems.
You want to know why the configure script kept giving me the following
error:
Jay: ac fuck: xvid_h
checking for xvid.h...
Jay Dammit! Checking here??
(cached) no
checking for xvid_init in -lxvidcore... (cached) no
configure: warning: Could not run XviD test program, checking why...
*** The test program compiled, but did not run. This usually means
Look where I say 'fuck'. YOur script is checking for a file called
'xvid_h', not xvid.h!
See what I did to get around the stupid thing?:
ac_cv_header="xvid.h"
if eval "test \"`echo '$''{'ac_cv_header'+set}'`\" = set"; then
#if eval "test \"`echo '$''{'ac_cv_header_$ac_safe'+set}'`\" = set;
^^^
This guy is giving the
'_' between xvid and h.
Someone thinks they are pretty crafty, when all I see is a screwed up
configure script.
Jay
On Mon, 2004-01-05 at 18:18, indurain wrote:
> Hello,
>
> I received this error using your configure:
>
> checking for Qt library (version >= 200)... no
> configure: warning:
> *** Could not run Qt test program, checking why...
> *** Configure discovered/uses these settings:
> *** Qt libraries: /usr/lib/qt3/lib
> *** Qt headers: /usr/lib/qt3/include
> *** Note:
> *** Compilation of Qt utilities also might be turned off (if not wanted).
> *** If you are experiencing problems which will not be described
> *** bellow please report then on '[EMAIL PROTECTED]' mailing list
> *** (i.e. some misdetection or omitted path)
>
> configure: error:
> *** Qt test program compiled, but did not run. This usually means
> *** that the run-time linker is not finding Qt library or finding the wrong
> *** version of Qt. If it is not finding Qt, you will need to set your
> *** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point
> *** to the installed location Also, make sure you have run ldconfig if that
> *** is required on your system.
> ***
> *** If you have an old version installed, it is best to remove it, although
> *** you may also be able to get things to work by modifying LD_LIBRARY_PATH
> ***
> *** i.e. bash> export LD_LIBRARY_PATH=/usr/lib/qt3/lib:$LD_LIBRARY_PATH
>
> There are lots of things inherently broken with this script that the
> simple sticking '/usr/lib/qt3/lib/' in front of $LD_LIBRARY_PATH
>
> First, if you look at the top of this output, I believe you want to
> check for Qt Library 2.00 or greater, not 200.
>
> Second for qt3, it uses pkg-config to get its version library number.
> Thus, configure needs to take this into account. In fact, I do not see
> how the heck it gets a version number in the first place! So here is my
> little hack to get around this:
>
> (inside configure)
> min_qt_version=2.00
> echo "jay after: " $min_qt_version
> echo "Jay ac_c " $ac_c
> echo "Jay ac_cv_qt_version: " $ac_cv_qt_version
> echo "Jay LIBS " $LIBS
>
> ac_cv_qt_version=`pkg-config --modversion qt-mt`
>
> # I don't understand this code block at all so I did not touch it
> if test x$ac_have_qt = xyes ; then
> echo $ac_n "checking for Qt library (version >= $min_qt_version)""... $ac_c"
> 1>&6
> echo "configure:10209: checking for Qt library (version >= $min_qt_version)" >&5
> if eval "test \"`echo '$''{'ac_cv_qt_version'+set}'`\" = set"; then
> echo $ac_n "(cached) $ac_c" 1>&6
>
> So now I get a print-out as follows:
> jay after: 2.00
> Jay ac_c
> Jay ac_cv_qt_version:
> Jay LIBS -lnsl -ldl
> checking for Qt library (version >= 2.00)... (cached) found qt-mt version 3.2.2,
> libraries /usr/lib/qt3/lib, headers /usr/lib/qt3/include
>
> In conclusion, 2.00, not 200, and re-do the configure so it uses pkg-config
> for qt3 and above (which anyone who wants to use k3b under KDE3+ with the
> avifile program will need qt3+ anyways).
>
> Jay Freyensee
>
>
_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile
