search

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 259 forks source link

[mingw64] [libass] The pkg-config script could not be found or is too old #1937

Closed Murmur closed 3 years ago

Murmur commented 3 years ago

I have not been running autobuild_suite script for many months but running today gives me pkg-config script could not be found error message. I did not see an uploaded logfile link so maybe this fails very early in the build process. I have not idea how to fix this, I did delete build/libass-git folder before trying second time. Ideas anyone?

Starting 64bit compilation of global tools(B(B
fribidi git (B ................................................ [Up-to-date(B]
  Running git clone for libass...
┌ libass git (B ......................................... [Recently updated(B]
├(B Running autoreconf...
├(B Running configure...
Likely error (tail of the failed operation logfile):
configure: error: The pkg-config script could not be found or is too old.  Make sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.

Alternatively, you may set the environment variables FREETYPE_CFLAGS
and FREETYPE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

To get pkg-config, see <http://pkg-config.freedesktop.org/>.
See `config.log' for more details
configure failed. Check C:/projects/media-ab/build/libass-git/build-64bit/ab-suite.configure.log(B
This is required for other packages, so this script will exit.(B
  Creating diagnostics file...
- - -  -
- -------------------------------------------------------------------------------
Build jpegxl: 1
-------------------------------------------------------------------------------
update autobuild suite
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
critical updates
-------------------------------------------------------------------------------
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing pacman (5.2.2-12) breaks dependency 'pacman-contrib' required by base

resolving dependencies...
looking for conflicting packages...
:: mingw-w64-x86_64-pkgconf and mingw-w64-x86_64-pkg-config are in conflict. Remove mingw-w64-x86_64-pkg-config? [Y/n] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: mingw-w64-x86_64-pkgconf and mingw-w64-x86_64-pkg-config are in conflict
error: could not set install reason for package mingw-w64-x86_64-pkgconf (could not find or read package)
-------------------------------------------------------------------------------
Updating msys2 system and installed packages...
-------------------------------------------------------------------------------
error: no targets specified (use -h for help)
:: Synchronizing package databases...
 mingw32 is up to date
 mingw64 is up to date
 msys is up to date
:: Starting core system upgrade...
warning: terminate other MSYS2 programs before proceeding
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing pacman (5.2.2-12) breaks dependency 'pacman-contrib' required by base
-------------------------------------------------------------------------------
Updates finished.
-------------------------------------------------------------------------------
1480c1 commented 3 years ago

you could try opening mintty and running pacman -Syyuu --noconfirm as I do know that msys2 recently switched to using pkgconf as their default instead of pkg-config

Murmur commented 3 years ago

Thanks you gave me a hint to the correct direction, pacman -Syyuu --noconfirm still gave an error in a build process but msys2 magic word...I deleted the entire $mediaAutoBuildRoot/msys64 folder then build process downloaded a fresh msys2 and all went fine.