building the JDK on Windows using Cygwin

Thu Jul 11 15:50:45 UTC 2024

Anil,

I was also never able to build the JDK on my Windows 11 machine, having
encountered the same problems you are. The configure script was not finding
the boot JDK unless manually specified, nor could it find the installation
of Visual Studio 2022. I tried a few months ago and it still didn't work,
so you're not alone here. No fix worked, and the log didn't specify where
it was looking. I resorted to just developing on my Mac.

SWinxy

On Fri, Jul 5, 2024 at 4:51 PM Anil <1dropaflame at gmail.com> wrote:

> Here is the screenshot of my Installer - same version of VS as yours.
>
> [image: image.png]
>
> On Fri, Jul 5, 2024 at 3:40 PM Chen Liang <chen.l.liang at oracle.com> wrote:
>
>> To solve this, I have uninstalled VS, reinstalled VS community 2022
>> 17.10.3, selected "Desktop development with C++", which looks like in the
>> attached screenshot.
>>
>> After a fresh reinstallation like this, my "bash configure" then
>> succeeds; it failed to find vs before the installation. Can you try
>> following the steps I take, or at least compare your installation details
>> selection to mine?
>>
>> ------------------------------
>> *From:* build-dev <build-dev-retn at openjdk.org> on behalf of Anil <
>> 1dropaflame at gmail.com>
>> *Sent:* Friday, July 5, 2024 2:57 PM
>> *To:* Chen Liang <liangchenblue at gmail.com>
>> *Cc:* build-dev at openjdk.org <build-dev at openjdk.org>
>> *Subject:* Re: building the JDK on Windows using Cygwin
>>
>> [Chen] "try uncheck and recheck the box"
>>
>> How will that help?
>> Following your suggestion, I ran the Installer, then I unchecked the
>> "Desktop Components for C++" box and it says -6.81Gb
>> That shows it was installed.
>> Now I check the box again, and it says 0 Gb.
>> Now the Close button is enabled.
>> So No action is taken.
>>
>>
>> On Fri, Jul 5, 2024 at 2:03 PM Chen Liang <liangchenblue at gmail.com>
>> wrote:
>>
>> try uncheck and recheck the box. some optional components are required
>> for jdk, and uncheck and recheck will select those components if they
>> aren't already selected.
>>
>> On Fri, Jul 5, 2024, 12:17 PM Anil <1dropaflame at gmail.com> wrote:
>>
>> When I installed VS, I ensured that Desktop Development with C++ was
>> checked.
>> I ran the installer again, and it shows as checked and since the "Modify"
>> button is not enabled, but "Close" is enabled, it means that it is already
>> installed.
>> It is the only box checked.
>>
>>
>> On Fri, Jul 5, 2024 at 11:50 AM Chen Liang <liangchenblue at gmail.com>
>> wrote:
>>
>> Hi Anil, I had encountered the same problem before. Can you try install
>> VS's desktop development with c++ with its default selection? Last time I
>> unchecked some boxes and failed like you did. I don't think other big
>> components are required for jdk.
>>
>> On Fri, Jul 5, 2024, 11:46 AM Anil <1dropaflame at gmail.com> wrote:
>>
>> Over the past few days, I have tried a lot of things.
>> I reinstalled Cygwin. I used Git for Windows instead of Cygwin Git.
>> I uninstalled and reinstalled Visual Studio and in different locations,
>> but it didn't fix it.
>> I added my user name to the Administrator Group account because one post
>> said that is why I get access denied error but it still failed.
>> I set it back to being an ordinary user and now shortnames worked
>> I think the solution was simply to sign out of the Windows account so
>> that processes accessing PROGRA~1 would be stopped.
>> :) I am glad to be over that hurdle but now I see:
>>
>> $ bash configure --enable-debug
>> --with-toolchain-path=/cygdrive/c/PROGRA~1/MICROS~3/2022/Community/VC/Tools/MSVC/14.40.33807/bin/Hostx64/x64
>> configure: Using default toolchain microsoft (Microsoft Visual Studio)
>> configure: Found Visual Studio installation at
>> /cygdrive/c/progra~1/micros~3/2022/Community using well-known name
>> configure: Found Microsoft Visual Studio 2022
>> configure: Trying to extract Visual Studio environment variables for
>> x86_64
>> configure: using
>> /cygdrive/c/progra~1/micros~3/2022/Community/vc/auxiliary/build/vcvars64.bat
>> configure: Setting extracted environment variables for x86_64
>> fixpath: warning: Path '/cygdrive/c/minikube' does not exist
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows kits/10/windows
>> performance toolkit' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~1/mysql/mysql shell 8.0/bin'
>> contains space
>> fixpath: failure: Path
>> '/cygdrive/c/users/anil/appdata/local/programs/microsoft vs code/bin'
>> contains space
>> fixpath: failure: Path '/cygdrive/c/progra~1/jetbrains/intellij idea
>> community edition 2022.2.3/bin' contains space
>> fixpath: failure: Path
>> '/cygdrive/c/progra~1/micros~3/2022/community/common7/ide/commonextensions/microsoft/teamfoundation/team
>> explorer' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~1/micros~3/2022/community/team
>> tools/diagnosticshub/collector' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows
>> kits/10/bin/10.0.22621.0/x64' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows kits/10/bin/x64'
>> contains space
>> fixpath: warning: Path '/cygdrive/c/minikube' does not exist
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows kits/10/windows
>> performance toolkit' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~1/mysql/mysql shell 8.0/bin'
>> contains space
>> fixpath: failure: Path
>> '/cygdrive/c/users/anil/appdata/local/programs/microsoft vs code/bin'
>> contains space
>> fixpath: failure: Path '/cygdrive/c/progra~1/jetbrains/intellij idea
>> community edition 2022.2.3/bin' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows
>> kits/10/include/10.0.22621.0/ucrt' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows
>> kits/10/include/10.0.22621.0/um' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows
>> kits/10/include/10.0.22621.0/shared' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows
>> kits/10/include/10.0.22621.0/winrt' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows
>> kits/10/include/10.0.22621.0/cppwinrt' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows
>> kits/10/lib/10.0.22621.0/ucrt/x64' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows
>> kits/10/lib/10.0.22621.0/um/x64' contains space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows kits/10/' contains
>> space
>> fixpath: failure: Path '/cygdrive/c/progra~2/windows kits/10/' contains
>> space
>> checking that Visual Studio variables have been correctly extracted... ok
>> checking for cl... $FIXPATH
>> /cygdrive/c/progra~1/micros~3/2022/community/vc/tools/msvc/14.40.33807/bin/hostx64/x64/cl.exe
>> checking resolved symbolic links for CC... no symlink
>> configure: Using microsoft C compiler version 19.40.33811 [Microsoft (R)
>> C/C++ Optimizing Compiler Version 19.40.33811 for x64]
>> checking whether the C compiler works... no
>> configure: error: in '/cygdrive/c/users/anil/OpenJDK/jdk':
>> configure: error: C compiler cannot create executables
>> See 'config.log' for more details
>> configure exiting with result code 77
>>
>> I have attached my config.log
>> appreciate any help.
>> thanks,
>> Anil
>>
>>
>> On Wed, Jul 3, 2024 at 9:13 AM Anil <1dropaflame at gmail.com> wrote:
>>
>> Thank you.
>> Yes, the vcvars file is present in that folder.
>>
>> $ cygpath -d "C:\Program Files\Microsoft Visual
>> Studio\2022\Community\VC\Auxiliary\Build"
>> cygpath: cannot create short name of C:\Program Files\Microsoft
>> VisualStudio\2022\Community\VC\Auxiliary\Build
>>
>>
>>
>> On Wed, Jul 3, 2024 at 2:57 AM Daniel Jeliński <djelinski1 at gmail.com>
>> wrote:
>>
>> Hi Anil,
>> Can you check what the following command prints on your machine?
>> $ cygpath -d "C:\Program Files\Microsoft Visual
>> Studio\2022\Community\VC\Auxiliary\Build"
>>
>> I assume you have this directory on your machine, and it contains a
>> file named "vcvars64.bat"
>>
>> The above command should print a path without spaces. If the command
>> fails or there are any spaces in the output, that's where you should
>> focus your search.
>>
>> The other thing to check is if you have a case-sensitive file system.
>> Configure looks for file named (note lowercase in the last 3
>> directories):
>> "C:\Program Files\Microsoft Visual
>> Studio\2022\Community\vc\auxiliary\build\vcvars64.bat"
>>
>> and from the logs you provided it looks like that file can't be found.
>>
>> By the way, the above paths were used when I started configure with:
>> $ bash configure --with-tools-dir="C:\Program Files\Microsoft Visual
>> Studio\2022\Community\VC\Auxiliary\Build"
>>
>> ..and on my machine that configure command succeeded.
>> Regards,
>> Daniel
>>
>> wt., 2 lip 2024 o 23:16 Anil <1dropaflame at gmail.com> napisał(a):
>> >
>> > trimming earlier message as it was over 500Kb with attachment.
>> Including configure.log
>> >
>> >
>> > On Tue, Jul 2, 2024 at 2:00 PM Anil <1dropaflame at gmail.com> wrote:
>> >>
>> >> Thank you.
>> >> I have attached both config.log and configure.log to this email.
>> >> Anil
>> >>>
>> >>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/build-dev/attachments/20240711/389f10c0/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 93485 bytes
Desc: not available
URL: <https://mail.openjdk.org/pipermail/build-dev/attachments/20240711/389f10c0/image-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 135195 bytes
Desc: not available
URL: <https://mail.openjdk.org/pipermail/build-dev/attachments/20240711/389f10c0/image-0003.png>