- attached size_t named type.patch
x265.h:192:5: error: ‘size_t’ does not name a type
https://bitbucket.org/multicoreware/x265/diff/source/x265.h?diff2=6440af3f2798&at=default
on linux debian 64: x265.h:192:5: error: ‘size_t’ does not name a type
Comments (4)
-
-
Account Deleted Henry Vindin: Your patch works. I added the line "#include <cstddef>" to /x265/source/x265.h and rebuilt with success after coming across the same error on a fresh source download.
I do run across a different issue instead when trying to configure FFMPEG with libx265 compiled with this change. From the config.log:
"ERROR: x265 not found using pkg-config /usr/local/include/x265.h:30:19: fatal error: cstddef: No such file or directory #include <cstddef> ^ compilation terminated. ERROR: x265 not found using pkg-config "
-
- changed status to resolved
api: fix size_t and bool type in x265_picture (fixes
#244)→ <<cset cb8769b5ea70>>
-
Dan Styles, I believe that the pkg-config errors seen when building ffmpeg are the result of the wiki entries and compilation guides being out of date, there are a huge number of places that issues have been posted regarding the .pc file generated by the x265 build and how ffmpeg should handle it.
You might want to read these:
https://ffmpeg.zeranoe.com/forum/viewtopic.php?t=1948 http://ffmpeg.org/pipermail/ffmpeg-user/2015-April/026026.html https://bitbucket.org/multicoreware/x265/issues/125/x265-not-found-using-pkg-config
You need to make sure that you compile everything correctly although that is not necessarily always the simplest task, but I definitely don't know the intricacies of the compilation of ffmpeg or x265 well enough to provide you with more informed advice.
- Log in to comment
I believe this is caused by cstddef not being included implicitly in new versions of gcc.
See - https://gcc.gnu.org/gcc-4.6/porting_to.html