[x264-devel] Intel Compiler support

Dennis Munsie dmunsie at gmail.com
Thu Mar 24 19:55:42 CET 2011


Here you go -- x264build.txt contains the output in the terminal when doing a make.  It aborts on the first file, so that's why it's a bit short.

Thanks!
dennis

-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.h
Type: application/octet-stream
Size: 614 bytes
Desc: not available
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20110324/c55351ff/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: application/octet-stream
Size: 2232 bytes
Desc: not available
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20110324/c55351ff/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.mak
Type: application/octet-stream
Size: 840 bytes
Desc: not available
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20110324/c55351ff/attachment-0002.obj>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: x264build.txt
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20110324/c55351ff/attachment.txt>
-------------- next part --------------


On Mar 24, 2011, at 1:03 PM, BugMaster wrote:

> On Thu, 24 Mar 2011 10:57:04 -0400, Dennis Munsie wrote:
>> Are there any additional instructions on how to use this new
>> support for the Intel compiler?  Doing the following did not work on my machine:
> 
>> $ CC=icc ./configure --prefix=/usr/local
>> $ make
> 
>> I get a ton of errors, mostly ones that look like this:
> 
>>        common/common.h(244): error: expected an expression
>>              for( int i = 0; i < i_mvc-1; i++ )
> 
>> This is on Debian Squeeze, 64-bit using the 11.1 version of the
>> Intel compiler.  I placed the /opt/intel/Compiler/11.1/bin/intel64
>> directory in my path before doing the configure and make steps. 
> 
>> Thanks!
>> dennis
> 
> CC=icc must be enough. It would be simpler to analyse if attach
> config.log, config.h, config.mak and log of ALL errors during
> compilation (not only one). Error message"expected an expression"
> sounds like missed header include.
> 
> On Thu, 24 Mar 2011 15:38:02 +0000, Mans Rullgard wrote:
> 
>> The patch appears to support the Intel compiler on Windows only.
> 
> No. It supposed to support Windows / Linux / Mac OS X
> 
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel



More information about the x264-devel mailing list