RFR: 8262276: Debug build of WebKit fails
PrimosK
github.com+1519324+primosk at openjdk.java.net
Mon Mar 8 16:24:06 UTC 2021
On Mon, 8 Mar 2021 15:07:30 GMT, Johan Vos <jvos at openjdk.org> wrote:
>>> The build failed again. The only difference I can spot at this time is the line at which the build failed (it changed from 3445 to 3453):
>>> ...
>>>
>>> Please let me know if you need any further information.
>>
>> You might be running into a different problem then, since this patch solve the compilation problem for Arun, for me, and for our CI build systems, when building with `-PCONF=DebugNative` (as a side note, we have some problems running the unit tests, but that's a separate issue). I have a couple questions for you:
>>
>> 1. Does the build work if you build without `-PCONF=DebugNative`? If it still fails, then you are definitely running into a different problem, likely something in your environment.
>>
>> 2. Can you double-check the versions of the build tools that you are using? We build using Visual Studio 2019 rather than the 2017 that you are using, although it will build with the latest VS2017 update. The versions of the other tools should be:
>> * gradle 6.3
>> * cmake 3.13.3
>> * ninja 1.8.2
>>
>> 3. Have you tried building on a platform other than Windows?
>
> when passing `--info` to gradle, the build succeeds. Without passing `--info` it fails. I'll do more testing later.
> > The build failed again. The only difference I can spot at this time is the line at which the build failed (it changed from 3445 to 3453):
> > ...
> > Please let me know if you need any further information.
>
> You might be running into a different problem then, since this patch solve the compilation problem for Arun, for me, and for our CI build systems, when building with `-PCONF=DebugNative` (as a side note, we have some problems running the unit tests, but that's a separate issue). I have a couple questions for you:
>
> 1. Does the build work if you build without `-PCONF=DebugNative`? If it still fails, then you are definitely running into a different problem, likely something in your environment.
> 2. Can you double-check the versions of the build tools that you are using? We build using Visual Studio 2019 rather than the 2017 that you are using, although it will build with the latest VS2017 update. The versions of the other tools should be:
>
> * gradle 6.3
> * cmake 3.13.3
> * ninja 1.8.2
>
> 1. Have you tried building on a platform other than Windows?
**1.**
No, it doesn't work. As already stated in the [JDK-8262276](https://bugs.openjdk.java.net/browse/JDK-8262276), the build fails for me with the exactly same error also when I set:
COMPILE_WEBKIT = true
CONF = Release
in `gradle.properties`.
**2.**
ATM I am using these libraries:
- Javafx (`pull/417`)
- Java 15 (installed on Windows)
- Ant 1.10.5 (installed on Windows)
- **CMake 3.13.3** (installed on Windows)
- Visual Studio 2017 community edition (**Ninja 1.8.2**)
- **Gradlew 6.3**
- CygWin (installed on Windows) with the following packages:
- bison 3.0.4-1
- flex 2.6.4-2
- gcc-g++ 10.2.0-1
- git 2.30.0-1
- gperf 3.1-1
- make 4.3-1
- makedepend 1.0.6-1
- openssh 8.4p1-2
- perl 5.32.1-1
- python27 2.7.18-4
- ruby 2.6.4-1
- unzip 6.0-17
- zip 3.0-12
But I am seeing exactly the same error.
**3.**
No - I've tried it only with Windows as we need debug symbols there...
Side note:
Could you guys please provide me with the versions of the above libraries that are used in the case of your CI build system? Is now Visual Studio the only difference? I tried to check it by myself by going through the log files at https://github.com/arun-Joseph/jfx/runs/2028653928 but I couldn't found CygWin plugin versions (bison, flex...).
Tomorrow I will try building it using Visual Studio 2019.
-------------
PR: https://git.openjdk.java.net/jfx/pull/417
More information about the openjfx-dev
mailing list