That's a great suggestion martin, is there a easy I can determine the number of cores being used ?
On Tue, Feb 2, 2016 at 6:04 PM, Reuben Martin <[email protected]> wrote: > On Monday, February 01, 2016 08:19:07 PM Srikanth Kommineni wrote: > > The older script it not setting the CPU option and seems to be compiling > > fine but when I tried to remove the cpu option in the newer script and > its > > failing with > > > > ffmpeg-android-master/toolchain-android/bin/arm-linux-androideabi-gcc is > > unable to create an executable file. > > > > C compiler test failed. > > > > It might be getting set with an environment variable, or a default value > somewhere. There are a lot more components to this than is revealed from > the > build scripts. > > Check the man pages for your compiler to see what CPU architectures it > supports. It appears you’re building it on a Mac, and in that case it is > either using gcc (which the version of gcc on a mac is older than the > aforementioned arm cpu), or more likely is using LLVM, which I am not > familiar > what CPU architectures it supports. The man pages should cover that though. > > One quick way to test the theory is to run the newer binary and see how > many > cores are being used. > > -Reuben > _______________________________________________ > ffmpeg-user mailing list > [email protected] > http://ffmpeg.org/mailman/listinfo/ffmpeg-user > -- Srikanth Kommineni _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user
