Am 27.09.2011 21:46, schrieb Richard Rasker:
> Op zondag 25-09-2011 om 21:59 uur [tijdzone +0200], schreef Johannes
> Sixt:
>> Am 25.09.2011 12:07, schrieb Richard Rasker:
>>> Here are the relevant parts from config.log:
>>>
>>> configure:26532: checking for x264_encoder_open in -lx264
>>> configure:26567: gcc -o conftest -g -O2 conftest.c -lx264 -lpthread -lm
>>> -lm -ldl -lpthread >&5
>>> /tmp//ccGPyZ0S.o: In function `main':
>>> /home/user/my_cinelerra/conftest.c:39: undefined reference to
>>> `x264_encoder_open'
>>> collect2: ld returned 1 exit status
>>
>> Strange. I do not have such lines ("checking for x264_encoder_open in
>> -lx264") in my config.log. Nor does it count lines beyond 20409. Perhaps
>> it is a different version of pgk-config (mine is 0.25).
>
> $ pkg-config --version
> 0.23
>
> So it's slightly older.
>
>> Anyway, x264_encoder_open will not be found in -lx264; the symbol is
>> named x264_encoder_open_116 or whatever the x264 version is. Can you
>> find out what the code in the configure script looks like that produces
>> the above message in config.log? Mine begins with these lines:
>>
>> ############## libx264
>> LIBX264_LIBS=""
>>
>> pkg_failed=no
>> { $as_echo "$as_me:${as_lineno-$LINENO}: checking for LIBX264" >&5
>> $as_echo_n "checking for LIBX264... " >&6; }
>>
>> and goes on with ca. 70 lines of shell script. The core of the check
>> seems to be merely:
>>
>> if test $_pkg_short_errors_supported = yes; then
>> LIBX264_PKG_ERRORS=`$PKG_CONFIG --short-errors
>> --print-errors "x264" 2>&1`
>> else
>> LIBX264_PKG_ERRORS=`$PKG_CONFIG --print-errors "x264" 2>&1`
>> fi
>>
>> and the rest of the 70 lines just look like bookkeeping and reporting.
>
>
> I appear to have a completely different version of configure; I can find
> the starting lines you mention (from line number 26531 onwards), but not
> the core lines above.
>
> Here's the version I pulled in through git, should you want to compare
> it:
>
> http://www.linetec.nl/linux/configure
>
> I'm still rather puzzled about what's going on here ...
So am I. The tests in your configure script originate from the standard
AC_TRY_LINK and AC_TRY_COMPILE macros. Perhaps pgk-config 0.23 did it
ths way? I don't know...
These checks cannot succeed with libx264 because the function
x264_encoder_open is actually a macro that maps to x264_encoder_open_116
or similar, and the AC_TRY macros do not account for this.
Can you upgrade your pkg-config?
-- Hannes
_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra