[SOLVED] odd problem at building qt5 on slackware64 current

nobodino · 03-07-2022, 01:42 PM

I've built a new machine quite powerful with a Ryzen 9 3950x, thinking it would help building SFS much more efficiently, but I'm confronted to something quite unusual, I'm unable to build qt5 on slackware64 current or SFS with exactly the same message:

Code:

./../../3rdparty/chromium/third_party/blink/renderer/core/dom/document.cc:36: attention: «*#pragma clang max_tokens_here*» ignoré [-Wunknown-pragmas]
   36 | #pragma clang max_tokens_here 900000
      | 
ninja: build stopped: subcommand failed.
make[4]: *** [Makefile.gn_run:1363 : run_ninja] Erreur 1
make[4]*: on quitte le répertoire «*/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine/src/core*»
make[3]: *** [Makefile:82 : sub-gn_run-pro-make_first] Erreur 2
make[3]*: on quitte le répertoire «*/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine/src/core*»
make[2]: *** [Makefile:80 : sub-core-make_first] Erreur 2
make[2]*: on quitte le répertoire «*/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine/src*»
make[1]: *** [Makefile:49 : sub-src-make_first] Erreur 2
make[1]*: on quitte le répertoire «*/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine*»
make: *** [Makefile:1088 : module-qtwebengine-make_first] Erreur 2

which is not the case with my old intel machine i7 6700.
Any idea to solve that problem?
It's a pure slackware system, with nothing else.

Windu · 03-07-2022, 02:13 PM

Do you have the llvm 13.0.1 installed from Slackware-current?

nobodino · 03-07-2022, 02:18 PM

Yes, it's a pure and complete Slackware installation.

andrew.46 · 03-09-2022, 02:19 AM

For what its worth I built QT5 on -current just to test and it compiled cleanly here.

giomat · 03-09-2022, 02:51 AM

i know it sounds absurd but maybe you have too many cores? have you tried building with less threads?

nobodino · 03-09-2022, 03:09 AM

It's not a matter of number of cores. I had tested it about 1 month ago before the upgrade to glibc-2.35 and it built normaly. At that time I borrowed a graphic card to make that test, because I hadn't one. Now the machine is complete, but I'm stuck with this problem.

Windu · 03-09-2022, 03:34 AM

In the qt5.SlackBuild you see this section:

Code:

# Sometimes a failure happens when parallelizing make.  Try again if make fails,
# but make a failure the second time around (single threaded) a fatal error:
#### DEBUG
make $NUMJOBS || exit 1
#make $NUMJOBS || make || exit

Have you already tried that last line instead of the line before? I.e. try again without paralellism? There could be a change in the software which is now affected by compiling on multiple cores. It does not hurt trying.

Also, I would check again if Slackware's clang is actually the first in your $PATH ... The "clang -v" command should return 13.0.1. Your error is typical in the case of a too-old clang compiler.

andrew.46 · 03-09-2022, 03:35 AM

I beg your pardon, my -current was not actually fully up to date. With the latest QT5 and -current as of March 9th I get the following:

Code:

ninja: build stopped: subcommand failed.
make[4]: *** [Makefile.gn_run:1363: run_ninja] Error 1
make[4]: Leaving directory '/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine/src/core'
make[3]: *** [Makefile:82: sub-gn_run-pro-make_first] Error 2
make[3]: Leaving directory '/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine/src/core'
make[2]: *** [Makefile:80: sub-core-make_first] Error 2
make[2]: Leaving directory '/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine/src'
make[1]: *** [Makefile:49: sub-src-make_first] Error 2
make[1]: Leaving directory '/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine'
make: *** [Makefile:1088: module-qtwebengine-make_first] Error 2
root@ilium/home/andrew/ssd2/Slackware/slackware64-current/source/l/qt5#

So same as your experience...

Windu · 03-09-2022, 03:50 AM

Are there errors before this text the both of you shared here? The 'unknown pragma' is a warning, so I do not understand why it would make ninja fail the build.

nobodino · 03-09-2022, 04:06 AM

Well I'm glad some else caught the same error.
@andrew.46: what are the specs of your machine?

@Windu: my install is a "quite" fresh install, from slackware-15.0 release.

gmgf · 03-09-2022, 04:07 AM

Quote:

Originally Posted by nobodino

I've built a new machine quite powerful with a Ryzen 9 3950x, thinking it would help building SFS much more efficiently, but I'm confronted to something quite unusual, I'm unable to build qt5 on slackware64 current or SFS with exactly the same message:

Code:

./../../3rdparty/chromium/third_party/blink/renderer/core/dom/document.cc:36: attention: «*#pragma clang max_tokens_here*» ignoré [-Wunknown-pragmas]
   36 | #pragma clang max_tokens_here 900000
      | 
ninja: build stopped: subcommand failed.
make[4]: *** [Makefile.gn_run:1363 : run_ninja] Erreur 1
make[4]*: on quitte le répertoire «*/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine/src/core*»
make[3]: *** [Makefile:82 : sub-gn_run-pro-make_first] Erreur 2
make[3]*: on quitte le répertoire «*/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine/src/core*»
make[2]: *** [Makefile:80 : sub-core-make_first] Erreur 2
make[2]*: on quitte le répertoire «*/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine/src*»
make[1]: *** [Makefile:49 : sub-src-make_first] Erreur 2
make[1]*: on quitte le répertoire «*/tmp/qt-everywhere-src-5.15.3_20220304_a657406f/qtwebengine*»
make: *** [Makefile:1088 : module-qtwebengine-make_first] Erreur 2

which is not the case with my old intel machine i7 6700.
Any idea to solve that problem?
It's a pure slackware system, with nothing else.

Me, too, I have problems for compiled, qt-webengine on my AMD machines, and I have only two AMD machines, it seems this is due to Clang.

nobodino · 03-09-2022, 04:09 AM

Welcome on board @gmgf

gmgf · 03-09-2022, 04:18 AM

Another exemple, for build qt6-tools, I am obliged to rebuild LLVM with these options

-DLLVM_BUILD_LLVM_DYLIB=ON \
-DLLVM_LINK_LLVM_DYLIB=ON \
-DBUILD_SHARED_LIBS=OFF \

ppr:kut · 03-09-2022, 04:28 AM

I don't see an actual error. So far I only see a warning.

nobodino · 03-09-2022, 04:39 AM

@ppr:kut : do you have Intel or AMD proc?
It seems related to AMD proc.
My Intel machine works normally, not the AMD one.