Closed qyot27 closed 7 years ago
Out of interest, is there a reason why you are building from GitHub and not from the official release tarball?
I know I haven't made a release in a long time...
It's for two, not entirely unrelated reasons: the length of time between tarballs is one of them, but the other is that I've generally moved most of the dependencies in my FFmpeg/mpv cross-compile guide to the git/svn/cvs repos if they have one available, except in the case of critical libs (gcrypt and the like needed for GnuTLS, or gcc's direct dependencies), or - rather infrequently - regressions in specific libs (the inverse is also true if there's an issue with a point release, but it's been fixed upstream).
This should have been fixed by @aleksander0m in #54 / #55
Confirming that it does resolve the issue. Thanks.
It's not causing the lib or bins to fail, since it's occurring right at the end, but it does cause make to fail, which can interfere with automated installation.
I do not have doxygen or asciidoc installed, and as per the response in issue #41, this should mean that docs aren't built. The problem is that make is still attempting to dive into doc/ and build them anyway.
I've tried explicitly passing --disable-maintainer-mode as well, just in case maintainer mode is on by default (which it shouldn't be if it is, but still), but the exact same error results. It also happens regardless of whether I'm compiling natively for Linux or cross compiling with MinGW-w64.
Ideally, docs (and the frontends, even though it's far more likely to build those) could be enabled/disabled at configure time and then the directories passed through to make accordingly. My attempts to wriggle a solution like that into
configure.ac
/Makefile.am
yesterday never actually worked as I wanted it to (it just kept skipping docs and frontends entirely, even if I just wanted to skip the docs directory), so I'm just filing a normal bug report instead.Compilation log: