racket / racket/racket

Build Failure on Windows 11, Visual Studio Developer Tools

Open
#5,315 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Racket
Stars
5.2k
Forks
698
Avg merge
18h 34m
Merged PRs (30d)
5

Description

What version of Racket are you using?
git main branch

What program did you run?
nmake

What should have happened?
Build properly

If you got an error message, please include it here.
https://pastebin.com/9p8bZdPe

I tried again, and got a slightly different error

raco setup: --- installing collections ---                         [11:05:08]
raco setup: installing: <collects>/racket
raco setup: --- post-installing collections ---                    [11:05:08]
raco setup: --- checking package dependencies ---                  [11:05:08]
racket\Racket.exe -G racket\etc -X racket\collects -U -G build\config\ -l- pkg/dirs-catalog --link --check-metadata --immediate racket\share\pkgs-catalog pkgs racket\src\expander racket\src\zuo\zuo-doc
Finding packages
racket\Racket.exe -G racket\etc -X racket\collects -U -G build\config\ racket\src\pkgs-config.rkt --pkgs-catalog https://pkgs.racket-lang.org https://pkgs.racket-lang.org
Updating build-stamp in racket\etc\config.rktd
racket\Racket.exe -G racket\etc -X racket\collects racket\src\pkgs-check.rkt racket\share\pkgs-catalog
Package links are in sync
racket\Racket.exe -G racket\etc -X racket\collects -N raco -l- raco pkg update --all --auto --no-setup --scope installation
No updates available; no packages installed in installation scope
racket\Racket.exe -G racket\etc -X racket\collects -N raco -l- raco pkg install --no-setup --pkgs --skip-installed --scope installation --deps search-auto racket-lib main-distribution main-distribution-test
00: Resolved "racket-lib" via file:///C:/github/racket/racket/share/pkgs-catalog
01: Resolving "main-distribution" via https://pkgs.racket-lang.org
Resolving "main-distribution-test" via https://pkgs.racket-lang.org
Using cached17548488941754848894141 for git://github.com/racket/main-distribution
Downloading repository git://github.com/racket/main-distribution-test commit 8d2afad3ef35760da305fdcb372276ab0c2d691b
01: Resolved "base" via file:///C:/github/racket/racket/share/pkgs-catalog
01: Resolving "racket-win32-i386-3" via https://pkgs.racket-lang.org
00: Resolving "db-win32-i386" via https://pkgs.racket-lang.org
failed
 in in-place {2}
 in build-one
 in loop
NMAKE : fatal error U1077: ' racket\src\build\zuo.exe . in-place MAKE="C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.44.35207\bin\HostX86\x86\nmake.exe"  VM="cs"  JOBS=""  CPUS=""  CONFIGURE_ARGS_qq=''  CONFIGURE_ARGS=""  CS_CROSS_SUFFIX=""  RACKET=""  PLAIN_RACKET=""  BOOTFILE_RACKET=""  SCHEME=""  CS_HOST_WORKAREA_PREFIX=""  PB_BRANCH="v10.3.0-pre-release.2-1"  PB_REPO="https://github.com/racket/pb"  SINGLE_BRANCH_FLAG="--single-branch"  EXTRA_REPOS_BASE=""  PKGS="main-distribution main-distribution-test"  PKG_UPDATE_OPTIONS=""  PLT_SETUP_OPTIONS=""  SRC_CATALOG="https://pkgs.racket-lang.org"  SETUP_MACHINE_FLAGS=""  PREFIX=""  RACKETBC_SUFFIX="bc"  RACKETCS_SUFFIX=""  DESTDIR=""' : return code '0x1'
Stop.

C:\github\racket>

Please include any other relevant details
Windows 11, Visual Studio 2022

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked Pastebin error together with the shown nmake output, focusing on the failing in-place build step and the Windows 11/Visual Studio 2022 environment. Reproduce the failure with nmake and determine what causes the nonzero return code; done means the git main branch build completes successfully on that setup.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, operating-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.