Recherche avancée

Sur d’autres sites (7017)

• make/cmake error : relocation R_X86_64_32 against `ff_a64_muxer' can not be used when making a shared object

  21 juin 2017, par NotCras

  Here’s what’s going on. I’m trying to set up OpenSceneGraph, however I run into the following error during the make process (spaces added for easier reading) :

  /usr/bin/ld: /usr/local/lib/libavformat.a(allformats.o): relocation R_X86_64_32 against `ff_a64_muxer' can not be used when making a shared object; recompile with -fPIC
  
  
  
  /usr/local/lib/libavformat.a: error adding symbols: Bad value
  
  
  
  collect2: error: ld returned 1 exit status
  
  
  
  src/osgPlugins/ffmpeg/CMakeFiles/osgdb_ffmpeg.dir/build.make:291: recipe for target 'lib/osgPlugins-3.4.0/osgdb_ffmpeg.so' failed
  
  
  
  make[2]: *** [lib/osgPlugins-3.4.0/osgdb_ffmpeg.so] Error 1
  
  
  
  CMakeFiles/Makefile2:6663: recipe for target 
  
  
  
  'src/osgPlugins/ffmpeg/CMakeFiles/osgdb_ffmpeg.dir/all' failed
  
  
  
  make[1]: *** [src/osgPlugins/ffmpeg/CMakeFiles/osgdb_ffmpeg.dir/all] Error 2
  
  
  
  make[1]: *** Waiting for unfinished jobs....

  This error does not stop the cmake process. A little later (error above occurs at 39%, process fails at 46%), I get this error :

  Makefile:127: recipe for target 'all' failed
  
  
  
  make: *** [all] Error 2

  Then the process stops.

  I’ve looked at some other solutions, but they didn’t have what I needed (here and here). I’ve run cmake with the -fPIC flag and that didn’t solve anything.

  I found a potential solution here but I don’t know how to implement "recompile your FFmpeg/libavcodec/libavformat with pic enabled". Can anyone talk me through it or give me a good resource ? I’ve never done it before and I don’t want to mess up my computer.

  Any help would be much appreciated. Thanks in advance !

• build : Fine-grained link-time dependency settings

  22 janvier 2017, par Diego Biurrun

  build : Fine-grained link-time dependency settings
  Previously, all link-time dependencies were added for all libraries,
  
  resulting in bogus link-time dependencies since not all dependencies
  
  are shared across libraries. Also, in some cases like libavutil, not
  
  all dependencies were taken into account, resulting in some cases of
  
  underlinking.
  To address all this mess a machinery is added for tracking which
  
  dependency belongs to which library component and then leveraged
  
  to determine correct dependencies for all individual libraries.
  

  • [DBH] Makefile
  • [DBH] avbuild/common.mak
  • [DBH] avbuild/library.mak
  • [DBH] configure
  • [DBH] tests/checkasm/Makefile

• Advice with ffmpeg creating clips out of a video

  5 décembre 2016, par Janx from Venezuela

  First of all I’m pretty new at this of video transcoding. I’m trying to use ffmpeg to create a 10 second clip out of a much larger video source, all this in a Node.js application using fluent-ffmpeg. My code goes something like :

  var command = ffmpeg().input(<sourcepath>).native().seekInput(<desiredstartpoint>)
  
      .duration(10)
  
      .on('start', function(commandLine){ // do some database persistence 
  
      }).on('progress',function(e){ // refresh a kill timeout
  
      }).on('error',function(e){ // clean up the mess
  
      }).on('end',function(e){ // success 
  
      }).save(<clipdestinationpath>);
  
  </clipdestinationpath></desiredstartpoint></sourcepath>

  Which usually translates into something like :

    ffmpeg -re -ss <desiredstartpoint> -i <sourcepath> -y -t 10 <clipdestinationpath>
  
  </clipdestinationpath></sourcepath></desiredstartpoint>

  What’s happening is that sometimes the process seems to ’hang’ and I have to manually kill the ffmpeg process (a batch console that appears on windows) for the node process to continue and the ’error’ callback to trigger. Same happens if I run the ffmpeg command manually on a CMD. It usually starts to :

     frame= xxx fps= yy q=x.x size= xxxKb time=00:00:0x.xx bitrate=xx.xxkbits/s
  
     frame= xxx fps= yy q=x.x size= xxxKb time=00:00:0x.xx bitrate=xx.xxkbits/s
  
     frame= xxx fps= yy q=x.x size= xxxKb time=00:00:0x.xx bitrate=xx.xxkbits/s

  Until is suddenly does it no more, and its hanged.

  I do have some fail-overs :

  • On the progress callback, I keep track of a timeout kill action, for when it hangs up, if there’s more than N seconds without activity, I call the kill like

    command.kill();

  • The other thing that I do is to decrement the desiredStartPoint by one (1) second at the time for up to five (5) seconds (greater than zero of course), and try again. Eventually the clip generates right, but it is so random... Sometimes it works like a charm, on the very first (1st) try it creates the clip all is OK to go.

  So my question is :

  • Do you see anything here that I might be missing ? Do I have to consider other variables ? like keyframes, fps, advanced stuffs like that ?

  I’ve also noticed that this happens more frequently on video sources recorded at high bitrate frequencies... I really don’t know men.