Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QtWebEngine
  4. Qtwebengine build failing with out of memory while compiling evaluate_prg_hwy file

Qtwebengine build failing with out of memory while compiling evaluate_prg_hwy file

Scheduled Pinned Locked Moved Unsolved QtWebEngine
2 Posts 2 Posters 501 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V Offline
    V Offline
    vinay21
    wrote on last edited by
    #1

    I have x86_64 host with 500GB RAM, on this I spinned up a podman continer for arm64 using qemu-user-static emulator. I couldn't use cross-compilers because of this issue(https://forum.qt.io/topic/163096/qt-6.8.3-build-fails-for-arm64-when-compiled-using-gcc-cross-compiler-x86_64-aarch64-toolchain./4).

    After Qtwebengine built almost, while compiling evaluate_prg_hwy file, it is failing with "g++: fatal error: Killed signal terminated program cc1plus". Even with 500GB RAM I couln't make progress with this. What exactly is this file. I am using cmake file to configure options
    (QT_CONFIGURE_OPTS =
    -DCMAKE_BUILD_TYPE=Release
    -DQT_BUILD_EXAMPLES=OFF
    -DQT_BUILD_TESTS=OFF \ etc)

    Can we disable this file/component which compiles from webengine. I need qtwebengine, can we disable compilation of evaluate_prg_hwy or its module from webengine alone? Can someone please help here

    1 Reply Last reply
    0
    • A Offline
      A Offline
      aymraic
      wrote last edited by
      #2

      Hello, i don't know which version of gcc you're using, but there is this know issues (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505#c18) with older version of gcc (seemingly pre 12.4 which prevent chromium from being built specifically for arm64 target. I had the same issues with the exact same file. The solutions in my case was to bump the gcc version (from 12.2.0 to 12.4.0) and compile again from scratch.

      1 Reply Last reply
      0

      • Login

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved