-
Notifications
You must be signed in to change notification settings - Fork 1.8k
1.88.0 Build failed on Windows 11 Intel x64 and x86 (32-bit) #1036
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
1.87.0 also did the same execution order but same result. I used Visual Studio 2010, so I ran b2 by specifying the version as below, but the result was the same. |
I use Visual Studio Professional 2022. |
I tried to download the source from GitHub and build it, but it was downloaded to an empty directory called "boost\tools\build", so I couldn't even try to build it. So far, I've tried to build Please give me a lot of advice. For reference, this is the Korean version of Windows 11. |
Solved. a malware called Trojan/Win.Generic.C57736304. If not, please remove the malware from the file. Below is the normal build packaging URL |
OS: Windows 11
Language: Visual Studio 2022 MFC
I downloaded version 1.88.0 from your official site and unzipped it.
After that, I ran bootstrap.bat in the unzipped directory.
And based on my experience building in 1.81.0, I ran "b2 -j4 -a --toolset=msvc-14.3 variant=debug,release link=static threading=multi address-model=32"
and "b2 -j4 -a --toolset=msvc-14.3 variant=debug,release link=static threading=multi address-model=64" in the same directory.
However, the following error occurred:
".b2", "share", "share/b2/", "share/b2/src" were not generated when building 1.81.0. However, the build was successful.
Unable to load B2
No '' was found by searching for:
C:/D_Drive/KPWorkSpace/boost_1_88_0/boost_1_88_0/.b2/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/share/b2/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/share/b2/src/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/boost_1_88_0/src/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/boost_1_88_0/tools/build/src/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/boost_1_88_0/src/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/src/build-system.jam
C:/D_Drive/KPWorkSpace/src/build-system.jam
C:/D_Drive/src/build-system.jam
C:/src/build-system.jam
Please consult the documentation at 'https://www.bfgroup.xyz/b2/'.
.
However, it was successfully installed in 1.81.0.
However, the following error occurs in 1.88.0.
However, ".b2", "share", "share/b2/", "share/b2/src", which are specified as not being loaded below, were not created when running "bootstrap.bat" in 1.81.0, and there was no error below.
The following error occurs in 1.85.0/1.87.0/1.88.0.
Below is the error message.
Unable to load B2
No '' was found by searching for:
C:/D_Drive/KPWorkSpace/boost_1_88_0/boost_1_88_0/.b2/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/share/b2/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/share/b2/src/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/boost_1_88_0/src/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/boost_1_88_0/tools/build/src/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/boost_1_88_0/src/build-system.jam
C:/D_Drive/KPWorkSpace/boost_1_88_0/src/build-system.jam
C:/D_Drive/KPWorkSpace/src/build-system.jam
C:/D_Drive/src/build-system.jam
C:/src/build-system.jam
Please consult the documentation at 'https://www.bfgroup.xyz/b2/'.
If you explore the contents specified in the above, the
"build-system.jam"
file exists in the directory below. However, it says it cannot find it. "C:/D_Drive/KPWorkSpace/boost_1_88_0/boost_1_88_0/tools/build/src"
How can I solve it?
I tried this because I wanted to use the Connect Pool included in the current version without developing a separate Mysql Connect Pool.
I also used Visual Studio Professional 2022 and did the same thing from x64 native tools command prompt but the result was the same.
The text was updated successfully, but these errors were encountered: