New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ffmpeg.exe - Entry Point Not Found on Microsoft® Windows® Web Server 2008 #118
Comments
The script explicitly adds --enable-libvpx/libx264/libx265 according to whether the respective libs are built or not. I can take that away and just obey ffmpeg_options.txt. Is that ffmpeg 32-bits that's giving that error? It shouldn't. |
I think that it's ffmpeg 32bit, but I'll ask the user to make sure. (he didn't post if it was a 32bit OS)
sounds good to me |
He's using a 64bit system, so it's a 64bit OS and x265 also doesn't work for him properly. :( |
So it's 64-bit XP. |
iirc Windows® Web Server 2008 is based on Vista, not XP |
Right, Vista/2008 didn't have that function either. Server 2008 R2 has it, since it's based on 7. |
Check a0b509c...531929c. |
Updated an got:
will report back once the script ran through,... |
Sourceforge is down, you can't update msys. On Fri, 17 Jul 2015 18:40 Georg Pelz notifications@github.com wrote:
|
ah okay. (the database being reported as invalid/corrupted sounded serious) |
You can still run the suite, it just won't upgrade msys/mingw. Also, make sure to not delete anything from /mingw32 or /mingw64, or it will prevent you from building. |
Script is running, but since bitbucket is totally slow atm, it's really a pain,.. :) |
stuck at: Cloning into 'libgme-git'... |
A user got an:
exception trying to use ffmpeg, since GetNumaNodeProcessorMaskEx sounds like x265, is possible to disable libx265 from being build into ffmpeg? (checked the ffmpeg_options.txt, but there was no mentioning of x265)
The text was updated successfully, but these errors were encountered: