From: Hashim Aziz <hashaziz@hotmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Fatal errors when compiling x264 from source while Avisynth is enabled
Date: Tue, 05 Mar 2019 02:05:00 -0000 [thread overview]
Message-ID: <AM4PR0101MB2258CA0652D7B6428CB9B216D5720@AM4PR0101MB2258.eurprd01.prod.exchangelabs.com> (raw)
I'm trying to follow the FFmpeg wiki's guide here to build FFmpeg from source with the most superior codecs it can make use of, like libfdk-aac and libopus:
https://trac.ffmpeg.org/wiki/CompilationGuide/Ubuntu
I've sorted many of the dependencies to get it to work on Cygwin, and thankfully I didn't need to build most of the packages in that guide from source because they were included in the Cygwin repository, but there are 2 or 3 that are not, including x264 and x265.
So I'm now trying to build x624 from source with the following command:
cd /ffmpeg_sources && git -C x264 pull 2> /dev/null || git clone --depth 1 https://git.videolan.org/git/x264 && cd x264 && PATH="/usr/local/bin:$PATH" PKG_CONFIG_PATH="/ffmpeg_build/lib/pkgconfig" ./configure --prefix="/ffmpeg_build" --bindir="/usr/local/bin" --enable-static --enable-pic && PATH="usr/local/bin:$PATH" make -j4 && make install
But at the configure stage of this command, I get a few errors and lots of warnings, but the final error is this one:
[Makefile:272: input/avs.o] Error 1
I believe this is a Cygwin error based on the fact that the error immediately before the one above is the HMODULE error here:
https://stackoverflow.com/questions/45181102/ffmpeg-on-cygwin-failed-to-compile-libx264-error-unknown-type-name-hmodule
And in that question the OP and another answer are trying to follow the very same guide while using Cygwin on the same 64-bit Windows 7.
What's the problem here and how can I solve it? The errors go away and the compilation works when I include --disable-avs, but I don't want the version of FFmpeg that I build to come without AVS/Avisynth support.
Thank you in advance.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2019-03-05 2:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 2:05 Hashim Aziz [this message]
2019-03-05 3:16 ` Brian Inglis
2019-03-05 19:40 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AM4PR0101MB2258CA0652D7B6428CB9B216D5720@AM4PR0101MB2258.eurprd01.prod.exchangelabs.com \
--to=hashaziz@hotmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).