Recherche avancée

Sur d’autres sites (5200)

• Building x264 with YASM : failing the ASM check

  11 janvier 2020, par radiofreemyourenji

  My question up front is, "I have new yasm, I think x264 is supposed to be cool with that, why is x264 not cool with that ?"

  


  For reasons, I am building a CentOS docker image (based on centos:latest) that contains a from-scratch ffmpeg build, following the guide here. It's a good guide, it's worked for me before, so I was feeling good about it.

  


  Today I'm hitting a choke point on the libx264 build point : specifically, I say

  


  PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  ./configure \
  --prefix="/tmp/ffmpeg_build" \
  --bindir="/tmp/bin" \
  --enable-static


  


  And I get a reply back

  


  


  Found no assembler

  


  Minimum version is nasm-2.13

  


  If you really want to compile without asm, configure with —disable-asm.

  


  


  That's unexpected. I have yasm, which I understand to be 1) there to do the things nasm does but better, and 2) to be the daisy-fresh most modern version given that I pulled it from its repo about an hour ago, and built it about fifty-nine minutes ago. For what it's worth, nasm is on the box too since the instructions request it, but it's below their stated version (i.e. it's "NASM version 2.10.07 compiled on Jun 9 2014")

  


  So it seems like yasm is not being found. There's another StackExchange question that mentions that problem, which came out to a pathing issue. So, I added yasm to my path like so :

  


  PATH=/tmp/ffmpeg_sources/yasm:$PATH \
  PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  ./configure
  ...etc


  


  That still gave the Found-no-assembler problem. As a last, confused resort, I told the script explicitly what I wanted to use for the variable $AS, because based on my quick look into configure, that looked like where yasm/nasm was meant to go. The command becomes :

  


  AS=`which yasm`
  PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  ./configure
  ...etc


  


  That at least gave

  


  


  Found yasm 1.3.0

  


  Minimum version is nasm-2.13

  


  If you really want to compile without asm, configure with —disable-asm.

  


  


  Looking in the config.log I see the following :

  


  checking whether /tmp/bin/yasm supports vmovdqa32 [eax]{k1}{z}, zmm0... no
Failed commandline was:
--------------------------------------------------
/tmp/bin/yasm conftest.asm  -I. -I$(SRCPATH) -DARCH_X86_64=1 -I$(SRCPATH)/common/x86/ -f elf64  -o conftest.o
conftest.asm:1: error: instruction expected after label
conftest.asm:1: warning: ignoring unrecognized character `{'
conftest.asm:1: warning: ignoring unrecognized character `}'
conftest.asm:1: warning: ignoring unrecognized character `{'
conftest.asm:1: warning: ignoring unrecognized character `}'
--------------------------------------------------
Failed program was:
--------------------------------------------------
vmovdqa32 [eax]{k1}{z}, zmm0
--------------------------------------------------


  


  So : what's the deal here ? Is my assumption that yasm drop-in replaces nasm bad ? Is yasm good for this purpose, but I'm not providing the right information to ./configure ? Are my instructions for building ffmpeg for CentOS simply out of date with respect to this prerequisite and I should just try harder to get a modern nasm ?

  


• expected end of line but found unknown token

  17 juin 2017, par Denzil Williams

  Ok so after days of searching, here I am. I am new to ffmpeg, applescript, and terminal.

  I want to use ffmpeg to batch convert a group of selected files in any folder. I was successful in doing this by opening the terminal at the folder location and using this code :

  for f in *.flv; do ffmpeg -i "$f" -acodec libmp3lame -b:a 256k "${f%.flv}.mp3" && rm "$f"; done

  which finds all flv files, and converts it to 256 bit rate mp3, then deletes the original files.

  Now I want it to be more automated, so I looked into creating a service. I tried running an apple script through automator, which I want it to open the terminal at the folder location the file then run the code to convert the files. Here’s the code I attempted :

  tell application "Finder" to set currentFolder to target of front Finder window as text
  
  set theWin to currentFolder's POSIX path
  
  
  
  tell application "Terminal"
  
      if not (exists window 1) then reopen
  
      activate
  
      do script "cd " & quoted form of theWin & ";clear" in window 1
  
      tell application "Terminal"
  
          do script "for f in *.flv; do ffmpeg -i "$f" -acodec libmp3lame -b:a 256k "${f%.flv}.mp3" && rm "$f"; done"
  
      end tell
  
  end tell

  The first part of code opens up terminal at the folder location just fine. But when I add the part with the ffmpeg code it crashes. The error is apparently with the "$", those are what light up as the error, the error message says "Expected end of line, but found unknown token". Looking for some assistance please. I need the "$" because those are what make the loop work for renaming the files and such.

• Building x264 with YASM : failing the ASM check

  11 janvier 2020, par radiofreemyourenji

  My question up front is, "I have new yasm, I think x264 is supposed to be cool with that, why is x264 not cool with that ?"

  For reasons, I am building a CentOS docker image (based on centos:latest) that contains a from-scratch ffmpeg build, following the guide here. It’s a good guide, it’s worked for me before, so I was feeling good about it.

  Today I’m hitting a choke point on the libx264 build point : specifically, I say

  PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  
    ./configure \
  
    --prefix="/tmp/ffmpeg_build" \
  
    --bindir="/tmp/bin" \
  
    --enable-static

  And I get a reply back

  Found no assembler

  Minimum version is nasm-2.13

  If you really want to compile without asm, configure with —disable-asm.

  That’s unexpected. I have yasm, which I understand to be 1) there to do the things nasm does but better, and 2) to be the daisy-fresh most modern version given that I pulled it from its repo about an hour ago, and built it about fifty-nine minutes ago. For what it’s worth, nasm is on the box too since the instructions request it, but it’s below their stated version (i.e. it’s "NASM version 2.10.07 compiled on Jun 9 2014")

  So it seems like yasm is not being found. There’s another StackExchange question that mentions that problem, which came out to a pathing issue. So, I added yasm to my path like so :

  PATH=/tmp/ffmpeg_sources/yasm:$PATH \
  
    PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  
    ./configure
  
    ...etc

  That still gave the Found-no-assembler problem. As a last, confused resort, I told the script explicitly what I wanted to use for the variable $AS, because based on my quick look into configure, that looked like where yasm/nasm was meant to go. The command becomes :

  AS=`which yasm`
  
    PKG_CONFIG_PATH="/tmp/ffmpeg_build/lib/pkgconfig" \
  
    ./configure
  
    ...etc

  That at least gave

  Found yasm 1.3.0

  Minimum version is nasm-2.13

  If you really want to compile without asm, configure with —disable-asm.

  Looking in the config.log I see the following :

  checking whether /tmp/bin/yasm supports vmovdqa32 [eax]{k1}{z}, zmm0... no
  
  Failed commandline was:
  
  --------------------------------------------------
  
  /tmp/bin/yasm conftest.asm  -I. -I$(SRCPATH) -DARCH_X86_64=1 -I$(SRCPATH)/common/x86/ -f elf64  -o conftest.o
  
  conftest.asm:1: error: instruction expected after label
  
  conftest.asm:1: warning: ignoring unrecognized character `{'
  
  conftest.asm:1: warning: ignoring unrecognized character `}'
  
  conftest.asm:1: warning: ignoring unrecognized character `{'
  
  conftest.asm:1: warning: ignoring unrecognized character `}'
  
  --------------------------------------------------
  
  Failed program was:
  
  --------------------------------------------------
  
  vmovdqa32 [eax]{k1}{z}, zmm0
  
  --------------------------------------------------

  So : what’s the deal here ? Is my assumption that yasm drop-in replaces nasm bad ? Is yasm good for this purpose, but I’m not providing the right information to ./configure ? Are my instructions for building ffmpeg for CentOS simply out of date with respect to this prerequisite and I should just try harder to get a modern nasm ?