m-ab-s / media-autobuild_suite

This Windows Batchscript helps setup a Mingw-w64 compiler environment for building ffmpeg and other media tools under Windows.
GNU General Public License v3.0
1.51k stars 262 forks source link

Highway-git now works, zvbi now fails #2465

Open QGtKMlLz opened 1 year ago

QGtKMlLz commented 1 year ago
          Thanks!  But further past that I get this:
17:03:37 zvbi-0.2 0.2.35  ............................... [Not installed]
17:03:37 ├ zvbi-0.2.35  ............................... [File up-to-date]
17:03:37 ├ Running extract...
17:03:39 ├ Running configure...
17:04:50 ├ Running install...
Likely error (tail of the failed operation logfile):
                                 ^
../../src/export.c:1813:12: error: call to undeclared function 'open'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
                int fd = open (name, flags, mode);
                         ^
3 errors generated.
make[2]: *** [Makefile:591: export.lo] Error 1
make[2]: Leaving directory '/build/zvbi-0.2.35/build-64bit/src'
make[1]: *** [Makefile:645: install-recursive] Error 1
make[1]: Leaving directory '/build/zvbi-0.2.35/build-64bit/src'
make: *** [Makefile:822: install] Error 2

logs.zip

_Originally posted by @Cooly0 in https://github.com/m-ab-s/media-autobuild_suite/issues/2463#issuecomment-1601746556_

tomcarrot commented 1 year ago

I have the same issue with vorbis-tools as other people had with highway-git:


        Starting 64bit compilation of audio tools
  Running git update for vorbis-tools...
┌ vorbis-tools git  ................................... [Recently updated]
├ Running autoreconf...
├ Running configure...
Likely error (tail of the failed operation logfile):
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports the include directive... yes (GNU style)
checking for gcc... ccache gcc
checking whether the C compiler works... no
configure: error: in `/build/vorbis-tools-git/build-64bit':
configure: error: C compiler cannot create executables
See `config.log' for more details
configure failed. Check C:/media-autobuild_suite-master/build/vorbis-tools-git/build-64bit/ab-suite.configure.log
This is required for other packages, so this script will exit.
  Creating diagnostics file...

Attach C:\media-autobuild_suite-master\build\logs.zip to the GitHub issue.
Make sure the suite is up-to-date before reporting an issue. It might've been fixed already.

Try running the build again at a later time.

logs.zip

Biswa96 commented 1 year ago

@tomcarrot Your issue is different than this issue. The last error in your given logs is

configure: error: C compiler cannot create executables

There may be something wrong in the system or mabs installation.

tomcarrot commented 1 year ago

You are right, my apologies. My old mabs installation did not work correctly, so i deleted everything, and started a clean one. The previous error happened in the new installation. Just to be sure, i deleted everything and started a clean install again, and now it gives a different error message:

        Starting 64bit compilation of global tools
├ Installing brotli... done
  Running git clone for highway...
  Running git update for highway...
┌ highway git  ........................................ [Recently updated]
├ Running cmake...
Likely error (tail of the failed operation logfile):

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:28 (project)

-- Configuring incomplete, errors occurred!
cmake failed. Check C:/media-autobuild_suite-master/build/highway-git/build-64bit/ab-suite.cmake.log
This is required for other packages, so this script will exit.
  Creating diagnostics file...

Attach C:\media-autobuild_suite-master\build\logs.zip to the GitHub issue.
Make sure the suite is up-to-date before reporting an issue. It might've been fixed already.

Try running the build again at a later time.

logs.zip