Closed treeshateorcs closed 6 months ago
It works well on our side.
Could you please provide us with the Configuration summary? It my be takn from the log produced by the script configure
after the line
====================================================
@treeshateorcs I suppose you're building on some new Linux distro (like Fedora 40, for example). Unfortunately, it's not a standard build environment for jbr21. Please use --disable-warnings-as-errors in the configure script to build on such a system.
@vprovodin
here's what you've requested
The existing configuration has been successfully updated in
/home/tho/dev/JetBrainsRuntime/build/linux-x86_64-server-release
using default settings.
Configuration summary:
* Name: linux-x86_64-server-release
* Debug level: release
* HS debug level: product
* JVM variants: server
* JVM features: server: 'cds compiler1 compiler2 epsilongc g1gc jfr jni-check jvmci jvmti management parallelgc serialgc services shenandoahgc vm-structs zgc'
* OpenJDK target: OS: linux, CPU architecture: x86, address length: 64
* Version string: 21.0.3-internal-adhoc.tho.JetBrainsRuntime (21.0.3-internal)
* Source date: 1716800427 (2024-05-27T09:00:27Z)
Tools summary:
* Boot JDK: openjdk version "21.0.3" 2024-04-16 OpenJDK Runtime Environment (build 21.0.3+9) OpenJDK 64-Bit Server VM (build 21.0.3+9, mixed mode, sharing) (at /usr/lib/jvm/java-21-openjdk)
* Toolchain: gcc (GNU Compiler Collection)
* C Compiler: Version 14.1.1 (at /usr/bin/gcc)
* C++ Compiler: Version 14.1.1 (at /usr/bin/g++)
Build performance summary:
* Build jobs: 16
* Memory limit: 31397 MB
WARNING: The result of this configuration has overridden an older
configuration. You *should* run 'make clean' to make sure you get a
proper build. Failure to do so might result in strange build problems.
@avu yes, i'm using arch, after adding that line it builds successfully. thank you!
I think it's worth keeping the issue open, because --disable-warnings-as-errors
is just a workaround, not a solution. I've filed JBR-7214 to keep tracking the state.
@treeshateorcs, I apologize for confusing you, but there's no need to keep the issue on GH opened - our primary tracker is YouTrack, and there's already such an issue there. Therefore, I'm closing this one.