Skip to content

Fix source build with MSVC (x64-mswin64) - #303

Open
hsbt wants to merge 1 commit into
bcrypt-ruby:masterfrom
hsbt:claude/suspicious-engelbart-80bb3d
Open

hsbt wants to merge 1 commit into
bcrypt-ruby:masterfrom
hsbt:claude/suspicious-engelbart-80bb3d

Conversation

@hsbt

@hsbt hsbt commented Sep 11, 2026

Copy link
Copy Markdown

gem install bcrypt --platform ruby fails on x64-mswin64 Ruby because extconf.rb unconditionally lists x86.o in $objs. The generated Makefile has no rule to build x86.S with cl.exe, so linking aborts with LNK1181: cannot open input file 'x86.obj'. The assembly in x86.S is only used on i386 (BF_ASM == 1 in crypt_blowfish.c) and assembles to an empty object everywhere else, so this change skips it on mswin and links the portable C implementation instead. mingw and other platforms keep the current object list.

Verified with Ruby 4.0 (x64-mswin64_140) and Visual Studio 2022 Build Tools: rake compile spec passes (39 examples, 0 failures) and installing the locally built gem succeeds end to end.

Generated with Claude Code

extconf.rb unconditionally listed x86.o, but MSVC has no rule to
build x86.S, so linking failed with LNK1181 (cannot open x86.obj).
The assembly is only used on i386 (BF_ASM == 1) and assembles to an
empty object everywhere else, so skip it on mswin and use the
portable C implementation in crypt_blowfish.c instead.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant