Opened 8 years ago
Closed 8 years ago
#5050 closed defect (wontfix)
new libx265 not found in configure:
Reported by: | telperion | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | build system |
Version: | git-master | Keywords: | libx265 |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
new libx265 not found in configure:
config.log:
check_pkg_config x265 x265.h x265_api_get
pkg-config --exists --print-errors x265
check_func_headers x265.h x265_api_get -lx265
check_ld cc -lx265
check_cc
BEGIN /tmp/ffconf.50xKqPZL.c
1 #include <x265.h>
2 long check_x265_api_get(void) { return (long) x265_api_get; }
3 int main(void) { return 0; }
END /tmp/ffconf.50xKqPZL.c
gcc -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -I../static/include -g -O3 -march=native -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=c99 -fomit-frame-pointer -pthread -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/fribidi -I/usr/include/freetype2 -I/usr/include/freetype2 -I/usr/include/p11-kit-1 -I/usr/include/schroedinger-1.0 -I/usr/include/orc-0.4 -I/home/mc/develop-deb/ffmpeg-git/ffmpeg2/static/include -c -o /tmp/ffconf.oJ4D4RLX.o /tmp/ffconf.50xKqPZL.c
In file included from /tmp/ffconf.50xKqPZL.c:1:0:
/usr/include/x265.h:103:5: error: unknown type name 'bool'
bool bScenecut;
ERROR: x265 not found using pkg-config
x265 changes:
analysis: Dump/reuse scenecut and satdCost of lowres in analysis save and loa
https://bitbucket.org/multicoreware/x265/commits/e2e507ffe752d6c193a219b242c433bdc55f39f7
Change History (5)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
That seems like a x265 problem, bool is not a C type, they should fix their header.
comment:3 by , 8 years ago
It is if you include stdbool.h
. It is bad style for headers to require other previous headers, but it is technically legal, provided it is documented (which it does not seem to be), so I agree in this instance that would be x265's fault.
comment:4 by , 8 years ago
@Cigaes
yes, adding
<include stdbool.h>
in x265.h
allows the configuration and compilation of ffmpeg
comment:5 by , 8 years ago
Keywords: | libx265 added |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
I think this should be fixed in x265.
also reported at
https://bitbucket.org/multicoreware/x265/issues/212/new-libx265-not-found-in-ffmpeg-configure