ffmpeg install on Solaris 11.3 - ffmpeg

I have archive software that uses ffmpeg on a Solaris server to generate previews during the archive process. I have installed ffmpeg on the Solaris server following the steps outlined here
It appears as though the package installs successfully but if I run 'ffmpeg' as root I receive '-bash: ffmpeg: command not found'. From what I understand, running this command is what needs to work for the archive software to be able to use ffmpeg. From a bit of research it looks like I either have to move the ffmpeg install location to somewhere else or define some path that points to the ffmpeg software. My Solaris knowledge is limited so I am not sure how to do either of those things. Could someone describe how to define the path or move the installed package to the correct location?
Thank you

Related

Is there a temporary fix possible to compile successfully working ffmpeg for the windows 10 using MinGW?

Current ffmpeg depends on CryptAcquireContextW what was deprecated and now removed from Windows. It compiles fine, but on running it crashes with text: "ffmpeg procedure entry point CryptAcquireContextW could not be located in the dynamic link library". advapi32 does not provide it anymore? The net say's it is deprecated already for a longer, however latest stable 4.3.git ffmpeg still depends on it.
Is there a temporary fix possible to compile successfully working ffmpeg for the windows 10 using MinGW?

How to build(compile) ffmpeg.exe for windows 10

I need to build FFmppg for the windows environment with limited features.I am not able to find good documentation for building FFmpeg.exe for windows. Suggest me the good documentation for building FFmpeg on windows or tell me step by step procedure to compile
See ffmpeg-windows-build-helpers. It's a script that simplifies compiling ffmpeg for Windows.
Run ./cross_compile_ffmpeg.sh -h to see all available options to customize the build.

AVI INFO crashes the Octave GUI every time I try to run the code

I am trying to run a code in octave which requires reading frame info of a video file. However, it always crashes when I write the aviinfo. The line goes as this:
> vInfo = aviinfo('C:\devwork\Octave\boosted\resizedVideos\11-50-48--11-50-58_resized.mp4');
I realized that I did not have FFmpeg installed on my system. I did install it but still it crashes. Any idea why? How should I solve it?
While looking for solutions I came across this discussion which says there is a possibility of an "unfortunate interplay between the Octave code and the ffmpeg code. But I am unable to figure out why?
Which version of octave did you install.
Newer versions (latest is 4.2.1) all include the video package with ffmpeg preinstalled, so should be just a matter of loading the video package and then running the command.
For the above example, you are trying to read an avi file, not write it, so if the file does not exist there may be issues.
Running a similar example on my win10 machine using the video package, I see the same issue of it crashing.
It is now reported as an issue in an octave bug report: https://savannah.gnu.org/bugs/index.php?51057

gcc is unable to create an executable file when installing FFmpeg

I'm trying to install FFmpeg directly from the source and I keep getting this error:
gcc is unable to create an executable file.
If gcc is a cross-compiler, use the --enable-cross-compile option.
Only do this if you know what cross compiling means.
C compiler test failed.
If you think configure made a mistake, make sure you are using the latest
version from Git. If the latest version fails, report the problem to the
ffmpeg-user#ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
Include the log file "config.log" produced by configure as this will help
solving the problem.
Can anyone help? Also, yum install ffmpeg doesn't work.
Apparently, with the limited information I have, you need to at least install gcc to compile ffmpeg. See How to Compile FFmpeg on CentOS for instructions. It is designed for CentOS, but should work for RHEL and Fedora.
Alternatively you can simply use a static build of ffmpeg instead of compiling, but it doesn't have the advantage of customization that compiling provides.
Note that Stack Overflow is limited to programming questions and discussions.

file required for ffmpeg portability

I'm making a python GUI app and using ffmpeg to encode files. I'm bundling ffmpeg with it, so I'm wondering what do I need to make it portable. Would it work with just the ffmpeg binary in my /opt/local/bin folder?
Whatever binaries you distribute with your application need to be compiled for each target platform you want them to run on.

Resources