Skip to content
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

[SR-15203] Building Swift toolchain on Windows fails with "no libxml2" #57525

Closed
swift-ci opened this issue Sep 16, 2021 · 6 comments
Closed
Assignees
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. build Windows Platform: Windows

Comments

@swift-ci
Copy link
Collaborator

Previous ID SR-15203
Radar None
Original Reporter Stefan Springer (JIRA User)
Type Bug
Status Closed
Resolution Invalid

Attachment: Download

Environment

Windows Home 64 Bit running in a Parallels VM, using sources checkout-out with tag "5.4.3-RELEASE".

Additional Detail from JIRA
Votes 0
Component/s Project Infrastructure
Labels Bug, Windows, build
Assignee @shahmishal
Priority Medium

md5: 384aed368c84597fa826fac5e2b93688

Issue Description:

UPDATE: Issue resolved see my comment "RESOLVED: ..." from Sep. 18, 2021. (The instructions on https://github.com/apple/swift/blob/main/docs/WindowsBuild.md should be improved accordingly.)

UPDATE 2: No, I had to change from VS 2022 to VS 2019 because of a "expected Clang 12.0.0 or newer" error, and there it is again, the old "no libxml2" error despite of correct copying of the files. Note: I had to use MSVC\14.29.30133, because using Windows10SDK.17763 what only work without "Universal Windows App Development", as on https://github.com/apple/swift/blob/main/docs/WindowsBuild.md is listed as necessary. But maybe I just remove "Universal Windows App Development" and try again with Windows10SDK.17763.

When trying to build the Swift toolchain, the test for Clang ends with an "no libxml2" error:

[4149/6194] Performing configure step for 'libdispatch'
FAILED: tools/swift/libdispatch-prefix/src/libdispatch-stamp/libdispatch-configure
cmd.exe /C "cd /D S:\build\5.4.3-RELEASE\tools\swift\libdispatch-prefix\src\libdispatch-build && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" "-DCMAKE_AR=C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/lib.exe" -DCMAKE_BUILD_TYPE=Debug -DCMAKE_C_COMPILER=S:/build/5.4.3-RELEASE/bin/clang-cl.exe "-DCMAKE_C_FLAGS=/bigobj /Zc:inline /Zc:strictStrings /Oi /W4 -wd4141 -wd4146 -wd4244 -wd4267 -wd4291 -wd4351 -wd4456 -wd4457 -wd4458 -wd4459 -wd4503 -wd4624 -wd4722 -wd4100 -wd4127 -wd4512 -wd4505 -wd4610 -wd4510 -wd4702 -wd4245 -wd4706 -wd4310 -wd4701 -wd4703 -wd4389 -wd4611 -wd4805 -wd4204 -wd4577 -wd4091 -wd4592 -wd4319 -wd4709 -wd4324 -w14062 -we4238" -DCMAKE_CXX_COMPILER=S:/build/5.4.3-RELEASE/bin/clang-cl.exe "-DCMAKE_CXX_FLAGS=/bigobj /Zc:inline /Zc:strictStrings /Oi /Zc:rvalueCast /W4 -wd4141 -wd4146 -wd4244 -wd4267 -wd4291 -wd4351 -wd4456 -wd4457 -wd4458 -wd4459 -wd4503 -wd4624 -wd4722 -wd4100 -wd4127 -wd4512 -wd4505 -wd4610 -wd4510 -wd4702 -wd4245 -wd4706 -wd4310 -wd4701 -wd4703 -wd4389 -wd4611 -wd4805 -wd4204 -wd4577 -wd4091 -wd4592 -wd4319 -wd4709 -wd4324 -w14062 -we4238 /we4062 /wd4068 /permissive- -DOBJC_OLD_DISPATCH_PROTOTYPES=0" -DCMAKE_MAKE_PROGRAM=C:/PROGRA~2/MICROS~2/2019/COMMUN~1/Common7/IDE/COMMON~1/MICROS~1/CMake/Ninja/ninja.exe -DCMAKE_INSTALL_LIBDIR=lib -DCMAKE_INSTALL_PREFIX=S:/build/5.4.3-RELEASE/tools/swift/libdispatch-prefix "-DCMAKE_LINKER=C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/link.exe" -DCMAKE_RANLIB=: -DCMAKE_TOOLCHAIN_FILE= -DBUILD_SHARED_LIBS=YES -DENABLE_SWIFT=NO -DENABLE_TESTING=NO -GNinja S:\swift-corelibs-libdispatch && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -E touch S:/build/5.4.3-RELEASE/tools/swift/libdispatch-prefix/src/libdispatch-stamp/libdispatch-configure"
-- The C compiler identification is Clang 11.1.0 with MSVC-like command-line
-- The CXX compiler identification is Clang 11.1.0 with MSVC-like command-line
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: S:/build/5.4.3-RELEASE/bin/clang-cl.exe
-- Check for working C compiler: S:/build/5.4.3-RELEASE/bin/clang-cl.exe - broken
CMake Error at C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.20/Modules/CMakeTestCCompiler.cmake:66 (message):
  The C compiler

    "S:/build/5.4.3-RELEASE/bin/clang-cl.exe"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: S:/build/5.4.3-RELEASE/tools/swift/libdispatch-prefix/src/libdispatch-build/CMakeFiles/CMakeTmp

    Run Build Command(s):C:/PROGRA~2/MICROS~2/2019/COMMUN~1/Common7/IDE/COMMON~1/MICROS~1/CMake/Ninja/ninja.exe cmTC_3b729 && [1/2] Building C object CMakeFiles\cmTC_3b729.dir\testCCompiler.c.obj
    [2/2] Linking C executable cmTC_3b729.exe
    FAILED: cmTC_3b729.exe
    cmd.exe /C "cd . && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_3b729.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\rc.exe --mt=C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\llvm-mt.exe --manifests  -- C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_3b729.dir\testCCompiler.c.obj  /out:cmTC_3b729.exe /implib:cmTC_3b729.lib /pdb:cmTC_3b729.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    MT: command "C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr\bin\llvm-mt.exe /nologo /manifest CMakeFiles\cmTC_3b729.dir/intermediate.manifest /out:CMakeFiles\cmTC_3b729.dir/embed.manifest /notify_update" failed (exit code 0x1) with the following output:
    llvm-mt: error: no libxml2
    llvm-mt: ignoring unsupported 'notify_update' option
    ninja: build stopped: subcommand failed.

I am using libxml2 from https://github.com/stefanspringer1/Libxml2Validation.git (which is quite a current compilation, from this year), checked-out to `S:\Library\Libxml2Validation`, and `S:\Library\Libxml2Validation\Binaries\Windows.Intel` containing `libxml2.lib` and the DLLs added to the PATH environment variable, my command for building the whole toolchain is:

cmake -B "S:\build\5.4.3-RELEASE" ^
  -C S:\swift\cmake\caches\Windows-x86_64.cmake ^
  -D CMAKE_BUILD_TYPE=Debug ^
  -D CMAKE_INSTALL_PREFIX=C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr ^
  -D LLVM_DEFAULT_TARGET_TRIPLE=x86_64-unknown-windows-msvc ^
  -D LLVM_ENABLE_PDB=YES ^
  -D LLVM_EXTERNAL_CMARK_SOURCE_DIR=S:\cmark ^
  -D LLVM_EXTERNAL_SWIFT_SOURCE_DIR=S:\swift ^
  -D CMAKE_C_FLAGS="/bigobj" ^
  -D CMAKE_CXX_FLAGS="/bigobj" ^
  -D LLVM_PARALLEL_LINK_JOBS=1 ^
  -D DLLVM_PARALLEL_LINK_JOBS=1 ^
  -D SWIFT_PATH_TO_LIBDISPATCH_SOURCE=S:\swift-corelibs-libdispatch ^
  -D SWIFT_WINDOWS_x86_64_ICU_I18N_INCLUDE=S:\Library\icu-67\usr\include ^
  -D SWIFT_WINDOWS_x86_64_ICU_I18N=S:\Library\icu-67\usr\lib\icuin67.lib ^
  -D SWIFT_WINDOWS_x86_64_ICU_UC_INCLUDE=S:\Library\icu-67\usr\include ^
  -D SWIFT_WINDOWS_x86_64_ICU_UC=S:\Library\icu-67\usr\lib\icuuc67.lib ^
  -D LIBXML2_LIBRARY=C:\Users\stefan\Projects\Swift\Library\Libxml2Validation\Binaries\Windows.Intel\libxml2.lib ^
  -D LIBXML2_INCLUDE_DIR=C:\Users\stefan\Projects\Swift\Library\Libxml2Validation\header-files ^
  -G Ninja ^
  -S S:\llvm-project\llvm

ninja -C S:\build\5.4.3-RELEASE

With `-D LIBXML2_LIBRARY` and `-D LIBXML2_INCLUDE_DIR` and the addition to PATH I could resolve another "no libxml2" error at an earlier step, I got `-D LIBXML2_LIBRARY` and `-D LIBXML2_INCLUDE_DIR` from https://github.com/apple/swift/blob/main/docs/WindowsBuild.md under "Build swift-corelibs-foundation", was was not sure about whether to also add the `-D LIBXML2_DEFINITIONS="/DLIBXML_STATIC"` (got one message about that something is not static when using it).

I am also not sure about how really use the stuff in `S:\Library`, if more should be added to PATH.

(On the good side: it is "[4149/6194]", so I have already come a long way, cf. https://forums.swift.org/t/swift-package-manager-spm-still-not-working-on-windows/51388/38, it would be nice if I get the building done, many thanks in advance.)

@swift-ci
Copy link
Collaborator Author

Comment by Stefan Springer (JIRA)

I tried again with a configuration matching very close the one given on https://github.com/apple/swift/blob/main/docs/WindowsBuild.md (also with CMAKE_BUILD_TYPE=Release this time):

cmake -B "S:\b\1" ^
  -C S:\swift\cmake\caches\Windows-x86_64.cmake ^
  -D CMAKE_BUILD_TYPE=Release ^
  -D CMAKE_INSTALL_PREFIX=C:\Library\Developer\Toolchains\unknown-Asserts-development.xctoolchain\usr ^
  -D LLVM_DEFAULT_TARGET_TRIPLE=x86_64-unknown-windows-msvc ^
  -D LLVM_ENABLE_PDB=YES ^
  -D LLVM_EXTERNAL_CMARK_SOURCE_DIR=S:\cmark ^
  -D LLVM_EXTERNAL_SWIFT_SOURCE_DIR=S:\swift ^
  -D CMAKE_C_FLAGS="/bigobj" ^
  -D CMAKE_CXX_FLAGS="/bigobj" ^
  -D LLVM_PARALLEL_LINK_JOBS=2 ^
  -D DLLVM_PARALLEL_LINK_JOBS=2 ^
  -D SWIFT_PATH_TO_LIBDISPATCH_SOURCE=S:\swift-corelibs-libdispatch ^
  -D SWIFT_WINDOWS_x86_64_ICU_I18N_INCLUDE=S:\Library\icu-67\usr\include ^
  -D SWIFT_WINDOWS_x86_64_ICU_I18N=S:\Library\icu-67\usr\lib\icuin67.lib ^
  -D SWIFT_WINDOWS_x86_64_ICU_UC_INCLUDE=S:\Library\icu-67\usr\include ^
  -D SWIFT_WINDOWS_x86_64_ICU_UC=S:\Library\icu-67\usr\lib\icuuc67.lib ^
  -G Ninja ^
  -S S:\llvm-project\llvm

The only difference to the configuration given on https://github.com/apple/swift/blob/main/docs/WindowsBuild.md is the addition of the following lines:

  -D CMAKE_C_FLAGS="/bigobj" ^
  -D CMAKE_CXX_FLAGS="/bigobj" ^
  -D LLVM_PARALLEL_LINK_JOBS=2 ^
  -D DLLVM_PARALLEL_LINK_JOBS=2 ^

I also reduced the additions to the PATH environment variable to a minimum:

  • C:\Program Files\Git\cmd

  • C:\Program Files\Git\usr\bin

  • C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64

(So no paths to an existing Swift installation etc.) Further, Python files are associated with py.exe installed by pylauncher (https://bitbucket.org/vinay.sajip/pylauncher/downloads/). No further configuration besides the ones listed on https://github.com/apple/swift/blob/main/docs/WindowsBuild.md.

The current error message (practically the same as the old one above):

FAILED: tools/swift/libdispatch-prefix/src/libdispatch-stamp/libdispatch-configure
cmd.exe /C "cd /D S:\b\1\tools\swift\libdispatch-prefix\src\libdispatch-build && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" "-DCMAKE_AR=C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/lib.exe" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=S:/b/1/bin/clang-cl.exe "-DCMAKE_C_FLAGS=/bigobj /Zc:inline /Zi /Zc:strictStrings /Oi /W4 -wd4141 -wd4146 -wd4244 -wd4267 -wd4291 -wd4351 -wd4456 -wd4457 -wd4458 -wd4459 -wd4503 -wd4624 -wd4722 -wd4100 -wd4127 -wd4512 -wd4505 -wd4610 -wd4510 -wd4702 -wd4245 -wd4706 -wd4310 -wd4701 -wd4703 -wd4389 -wd4611 -wd4805 -wd4204 -wd4577 -wd4091 -wd4592 -wd4319 -wd4709 -wd4324 -w14062 -we4238 /Gw" -DCMAKE_CXX_COMPILER=S:/b/1/bin/clang-cl.exe "-DCMAKE_CXX_FLAGS=/bigobj /Zc:inline /Zi /Zc:strictStrings /Oi /Zc:rvalueCast /W4 -wd4141 -wd4146 -wd4244 -wd4267 -wd4291 -wd4351 -wd4456 -wd4457 -wd4458 -wd4459 -wd4503 -wd4624 -wd4722 -wd4100 -wd4127 -wd4512 -wd4505 -wd4610 -wd4510 -wd4702 -wd4245 -wd4706 -wd4310 -wd4701 -wd4703 -wd4389 -wd4611 -wd4805 -wd4204 -wd4577 -wd4091 -wd4592 -wd4319 -wd4709 -wd4324 -w14062 -we4238 /Gw /we4062 /wd4068 /permissive- -DOBJC_OLD_DISPATCH_PROTOTYPES=0" -DCMAKE_MAKE_PROGRAM=C:/PROGRA~2/MICROS~2/2019/COMMUN~1/Common7/IDE/COMMON~1/MICROS~1/CMake/Ninja/ninja.exe -DCMAKE_INSTALL_LIBDIR=lib -DCMAKE_INSTALL_PREFIX=S:/b/1/tools/swift/libdispatch-prefix "-DCMAKE_LINKER=C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/link.exe" -DCMAKE_RANLIB=: -DCMAKE_TOOLCHAIN_FILE= -DBUILD_SHARED_LIBS=YES -DENABLE_SWIFT=NO -DENABLE_TESTING=NO -GNinja S:\swift-corelibs-libdispatch && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -E touch S:/b/1/tools/swift/libdispatch-prefix/src/libdispatch-stamp/libdispatch-configure"
-- The C compiler identification is Clang 11.1.0 with MSVC-like command-line
-- The CXX compiler identification is Clang 11.1.0 with MSVC-like command-line
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: S:/b/1/bin/clang-cl.exe
-- Check for working C compiler: S:/b/1/bin/clang-cl.exe - broken
CMake Error at C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/share/cmake-3.20/Modules/CMakeTestCCompiler.cmake:66 (message):
  The C compiler

    "S:/b/1/bin/clang-cl.exe"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: S:/b/1/tools/swift/libdispatch-prefix/src/libdispatch-build/CMakeFiles/CMakeTmp

    Run Build Command(s):C:/PROGRA~2/MICROS~2/2019/COMMUN~1/Common7/IDE/COMMON~1/MICROS~1/CMake/Ninja/ninja.exe cmTC_93264 && [1/2] Building C object CMakeFiles\cmTC_93264.dir\testCCompiler.c.obj
    [2/2] Linking C executable cmTC_93264.exe
    FAILED: cmTC_93264.exe
   cmd.exe /C "cd . && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -E vs_link_exe --intdir=CMakeFiles\cmTC_93264.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100190~1.0\x64\rc.exe --mt=S:\b\1\bin\llvm-mt.exe --manifests  -- C:\PROGRA~2\MICROS~2\2019\COMMUN~1\VC\Tools\MSVC\1429~1.301\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_93264.dir\testCCompiler.c.obj  /out:cmTC_93264.exe /implib:cmTC_93264.lib /pdb:cmTC_93264.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    MT: command "S:\b\1\bin\llvm-mt.exe /nologo /manifest CMakeFiles\cmTC_93264.dir/intermediate.manifest /out:CMakeFiles\cmTC_93264.dir/embed.manifest /notify_update" failed (exit code 0x1) with the following output:
    llvm-mt: error: no libxml2
    llvm-mt: ignoring unsupported 'notify_update' option
    ninja: build stopped: subcommand failed.

UPDATE: Bringing back those three lines with LIBXML2_... on that basis does not help, still the same "no libxml2" error on [4196/6194]. I do not think I can variate much more. Please help. Thanks.

@swift-ci
Copy link
Collaborator Author

Comment by Stefan Springer (JIRA)

See attached my log from the configuration step (last version). conf.log

@swift-ci
Copy link
Collaborator Author

Comment by Stefan Springer (JIRA)

UPDATE: Without the following lines, the "no libxml2" error already comes earlier at "[10/1997]":

  -D LLVM_ENABLE_PDB=YES ^
  -D CMAKE_C_FLAGS="/bigobj" ^
  -D CMAKE_CXX_FLAGS="/bigobj" ^

@swift-ci
Copy link
Collaborator Author

Comment by Stefan Springer (JIRA)

RESOLVED:

The commands listed under "One-time Setup (re-run on Visual Studio upgrades)" on https://github.com/apple/swift/blob/main/docs/WindowsBuild.md did not work, because – of course – making a symbolic link does not work if at the path of the link file a file already exists, you need to delete it first. Unfortunately, it did not see the error message.

I now use the the following commands instead (not all deletions are actually needed, only two of them):

if exist "%UniversalCRTSdkDir%Include\%UCRTVersion%\ucrt\module.modulemap" del /Q "%UniversalCRTSdkDir%Include\%UCRTVersion%\ucrt\module.modulemap"
mklink "%UniversalCRTSdkDir%Include\%UCRTVersion%\ucrt\module.modulemap" S:\swift\stdlib\public\Platform\ucrt.modulemap
if exist "%UniversalCRTSdkDir%Include\%UCRTVersion%\um\module.modulemap" del /Q "%UniversalCRTSdkDir%Include\%UCRTVersion%\um\module.modulemap"
mklink "%UniversalCRTSdkDir%Include\%UCRTVersion%\um\module.modulemap" S:\swift\stdlib\public\Platform\winsdk.modulemap
if exist "%VCToolsInstallDir%include\module.modulemap" del /Q "%VCToolsInstallDir%include\module.modulemap"
mklink "%VCToolsInstallDir%include\module.modulemap" S:\swift\stdlib\public\Platform\visualc.modulemap
if exist "%VCToolsInstallDir%include\visualc.apinotes" del /Q "%VCToolsInstallDir%include\visualc.apinotes"
mklink "%VCToolsInstallDir%include\visualc.apinotes" S:\swift\stdlib\public\Platform\visualc.apinotes

@compnerd
Copy link
Collaborator

This seems like a setup issue, not an actual issue with the tooling.

@swift-ci
Copy link
Collaborator Author

Comment by Stefan Springer (JIRA)

This seems like a setup issue, not an actual issue with the tooling.

On https://github.com/stefanspringer1/BuildingSwiftOnWindows.git, I documented the exact steps I have done on a fresh Windows installation, it is basically what https://github.com/apple/swift/blob/main/docs/WindowsBuild.md says but with some checks and correction, incorporating the problems I had and described on https://forums.swift.org/t/swift-package-manager-spm-still-not-working-on-windows/51388.

It might be a setup problem but that is exactly what all this is about: Trying to describe the steps that are necessary for the Swift toolchain to be built. The description on https://github.com/apple/swift/blob/main/docs/WindowsBuild.md is at least uncomplete. The configuration step says:

```text

    • Could NOT find Backtrace (missing: Backtrace_LIBRARY Backtrace_INCLUDE_DIR)

    • Could NOT find OCaml (missing: OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH)

    • Could NOT find LibEdit (missing: LibEdit_INCLUDE_DIRS LibEdit_LIBRARIES)

    • Could NOT find CursesAndPanel (missing: CURSES_INCLUDE_DIRS CURSES_LIBRARIES PANEL_LIBRARIES)

    • Could NOT find LibLZMA (missing: LIBLZMA_LIBRARY LIBLZMA_INCLUDE_DIR LIBLZMA_HAS_AUTO_DECODER LIBLZMA_HAS_EASY_ENCODER LIBLZMA_HAS_LZMA_PRESET)

    • Could NOT find Lua (missing: LUA_LIBRARIES LUA_INCLUDE_DIR) (Required is at least version "5.3")

    • Could NOT find LuaAndSwig (missing: LUA_LIBRARIES LUA_INCLUDE_DIR)

    • Could NOT find SWIG (missing: SWIG_DIR) (Required is at least version "2.0")

    • Could NOT find LibXml2 (missing: LIBXML2_LIBRARY LIBXML2_INCLUDE_DIR) (Required is at least version "2.8")

    • Could NOT find Backtrace (missing: Backtrace_LIBRARY Backtrace_INCLUDE_DIR)

    • Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)

    • Could NOT find LibXml2 (missing: LIBXML2_LIBRARY LIBXML2_INCLUDE_DIR)

    • Could NOT find LibEdit (missing: LibEdit_INCLUDE_DIRS LibEdit_LIBRARIES)
      ```

I am willing to see and try what works and maybe enhance the description or complete my description for the may less experts. I think it is a real problem if the description for building the Swift toolchain is not enough for the "average" person to really execute it, and just to close this bug is not a solution.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. build Windows Platform: Windows
Projects
None yet
Development

No branches or pull requests

2 participants