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

[luajit] The generated <triplet>\tools\luajit.exe is broken on Windows. #43367

Closed
jamarr81 opened this issue Jan 20, 2025 · 0 comments · Fixed by #43374
Closed

[luajit] The generated <triplet>\tools\luajit.exe is broken on Windows. #43367

jamarr81 opened this issue Jan 20, 2025 · 0 comments · Fixed by #43374
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@jamarr81
Copy link

jamarr81 commented Jan 20, 2025

Describe the bug
The luajit.exe tool does not have access to its own modules on Windows, which breaks most of its extended functionality.

I assume this is because vcpkg_copy_tools(luajit) does not copy the src\jit modules to the <triplet>\tools\luajit\ directory as required when Installing LuaJIT on Windows. Attempting to use any of the modules, including the arguably most crucial module -b, results in an error.

Environment

  • OS: Windows 11
  • Compiler: MSVS 2022

To Reproduce
Steps to reproduce the behavior:

  1. Add the luajit dependency.
  2. Build luajit for <triplet>.
  3. Run <x-install-root>\<triplet>\tools\luajit.exe -b

Expected behavior
In the simplest use case, it should return a usage message like this:

Save LuaJIT bytecode: luajit -b[options] input output

Instead, it returns this error:

luajit.exe: unknown luaJIT command or jit.* modules not installed

Failure logs
n/a

Additional context
To fix this, it seems portfile.cmake should only need to copy src\jit to the same location as luajit.exe is copied.

D:...\tools\luajit>luajit.exe -v
LuaJIT 2.1.0-beta3 -- Copyright (C) 2005-2022 Mike Pall. https://luajit.org/

@JonLiu1993 JonLiu1993 added the category:port-bug The issue is with a library, which is something the port should already support label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants