All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14461] New: Qt5webenegine does not build due to fontconfig/freetype dependency problem
Date: Thu, 16 Dec 2021 14:47:15 +0000	[thread overview]
Message-ID: <bug-14461-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=14461

            Bug ID: 14461
           Summary: Qt5webenegine does not build due to
                    fontconfig/freetype dependency problem
           Product: buildroot
           Version: 2021.08.2
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: wojciech.ziniewicz@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

Hello,
I'm experiencing the same qt5 webengine build problem on x86 64 bit
architecture with following combinations of gcc and buildroot:
- gcc8, gcc9, gcc10
- 2021.08.2, 2021.08.3, 2021.11

It seems that qt5webengine requires freetype2.pc file which exists (parallel to
other .pc files). Both pkg config/fontconfig and freetype are normally
available.
The freetype/fontconfig pair is compiled prior to qt5webengine and it does not
really matter whether I explicitly add them to the config file or not because
they are included via FONTCONFIG dependency in qt5webengine.


-------------------------------- the error:
ERROR at //build/config/linux/pkg_config.gni:103:17: Script returned non-zero
exit code.
    pkgresult = exec_script(pkg_config_script, args, "value")
                ^----------
Current dir:
/common_cache/nerves/artifacts/rzjb_system_dev-portable-1.1.0/build/qt5webengine-5.15.2/src/core/release/
Command:
/common_cache/nerves/artifacts/rzjb_system_dev-portable-1.1.0/host/bin/python2
/common_cache/nerves/artifacts/rzjb_system_dev-portable-1.1.0/build/qt5webengine-5.15.2/src/3rdparty/chromium/build/config/linux/pkg-config.py
-p
/common_cache/nerves/artifacts/rzjb_system_dev-portable-1.1.0/build/qt5webengine-5.15.2/host-bin/host-pkg-config
freetype2
Returned 1.
stderr:
Package freetype2 was not found in the pkg-config search path.
Perhaps you should add the directory containing `freetype2.pc'
to the PKG_CONFIG_PATH environment variable
Package 'freetype2', required by 'virtual:world', not found
Could not run pkg-config.
See //build/linux/BUILD.gn:24:3: whence it was called.
  pkg_config("freetype_from_pkgconfig") {
  ^--------------------------------------
See //build/config/freetype/BUILD.gn:10:24: which caused the file to be
included.
    public_configs = [ "//build/linux:freetype_from_pkgconfig" ]
                       ^--------------------------------------
Project ERROR: GN run error!
make[4]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 3
make[3]: *** [Makefile:79: sub-core-make_first] Error 2
make[2]: *** [Makefile:49: sub-src-make_first] Error 2
make[1]: *** [package/pkg-generic.mk:270:
/common_cache/nerves/artifacts/rzjb_system_dev-portable-1.1.0/build/qt5webengine-5.15.2/.stamp_built]
Error 2
make: *** [Makefile:23: _all] Error 2
--------------

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2021-12-16 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 14:47 bugzilla [this message]
2021-12-16 17:23 ` [Buildroot] [Bug 14461] Qt5webenegine does not build due to fontconfig/freetype dependency problem bugzilla
2021-12-16 17:41 ` bugzilla
2021-12-16 17:53 ` bugzilla
2021-12-16 18:03 ` bugzilla
2021-12-16 21:18 ` bugzilla
2024-06-15 15:00 ` bugzilla

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=bug-14461-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.