[x264-devel] how to compile on Mac?

Mo DeJong mo at modejong.com
Thu Jun 20 01:57:22 CEST 2013


I can confirm that adding --disable-opencl to the configure call does fix the build on Mac (I have 10.7.5). I am building with a very simple script that configures and builds the current version of yasm, x264, and ffmpeg, it is attached to this email in case anyone would like to try it out.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: build.sh
Type: application/octet-stream
Size: 1917 bytes
Desc: not available
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20130619/bd5d53de/attachment.obj>
-------------- next part --------------


cheers
Mo DeJong


On Jun 19, 2013, at 12:05 PM, BugMaster wrote:

> On Wed, 19 Jun 2013 11:55:50 -0700, Mo DeJong wrote:
>> I just tried to build with the x264 snapshot on a Mac and got a bunch of errors also:
> 
>> In file included from ./extras/cl.h:27:
>> ./extras/cl_platform.h:64:10: warning: This path should never
>> happen outside of internal operating system
>>      development. AvailabilityMacros do not function correctly here! [-W#warnings]
>>        #warning  This path should never happen outside of internal operating system development. ...
> 
>>> 
>> In file included from ./common/opencl.h:31:
>> ./extras/cl.h:1165:21: error: unknown type name
>> 'CL_EXT_PREFIX__VERSION_1_1_DEPRECATED'
>> extern CL_API_ENTRY CL_EXT_PREFIX__VERSION_1_1_DEPRECATED cl_mem CL_API_CALL
>>                    ^
>> ./extras/cl.h:1165:65: error: expected ';' after top level declarator
>> extern CL_API_ENTRY CL_EXT_PREFIX__VERSION_1_1_DEPRECATED cl_mem CL_API_CALL
> 
>>>> fatal error: too many errors emitted, stopping now [-ferror-limit=]
> 
> 
>>> uname -a
>> Darwin 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT
>> 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64
> 
> This one is known problem with OpenCL in current version. You either
> need to disable OpenCL (./configure --disable-opencl) or get patch
> from
> https://github.com/DarkShikari/x264-devel/commit/3af33c98a60a62bf9dee9ccb0f2475b8124a5354
> 
> PS. As for topic starter problem I am dunno. May be he doesn't have
> yasm installed or configured it incorrectly.
> 
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel



More information about the x264-devel mailing list