-
-
Notifications
You must be signed in to change notification settings - Fork 14k
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
llvmPackages_{15,16,17}.lldb: broken, "ModuleNotFoundError: No module named 'lldb'" #166604
Comments
Hmm, seems the packaging of the python bits is broken. We expect python bits to all be in the "lib" output. We wrap lldb to find its python bits in However, all the python bits end up in the primary output, which is probably why this is broken. Hmm. EDIT: okay, the installCheckPhase isn't running, since checks aren't enabled by default (:disappointed:), but we can set So main thing is just convincing LLDB to install its python bits where we expect them (or move them, etc.). |
Also, the file we check for is The cc @Ericson2314 (thanks, sorry!). |
WIP fix, discussed here: #166730 (comment) . |
Throws errors on startup, see NixOS#166604. Should be marked broken but fixes in the works.
Throws errors on startup, see NixOS#166604 for same with LLVM14. Should be marked broken, but fixes in the works.
@dtzWill Any chance you could PR your WIP fix? Even if it's not perfect, it's better than the current state of LLDB 14 in nixpkgs. |
This issue has been mentioned on NixOS Discourse. There might be relevant details there: |
This still seems to be an issue for
the wrapper sets the which does not actually exist The path it it should be looking for is
The symlink for There seems to be some kind of mixup between |
Is there a workaround? |
Not fixed
|
Hm, I’m getting an even more egregious error with 16. I think this issue is about 14 though, which doesn’t have this issue for me. (I’m using
|
15 has the module not found error, though, for me |
what I really want is lldb 17 |
Describe the bug
lldb
fromllvmPackages_14.lldb
seems to be broken, reporting:This error is present in all invocations of
lldb
I've tried: with no arguments, pointed at an executable, and debugging a coredump (SYSTEMD_DEBUGGER=lldb
forcoredumpctl debug
(/gdb), FWIW).Coredump usage is worse, with something like:
Steps To Reproduce
Steps to reproduce the behavior:
lldb --version
or otherlldb
invocations, until this is fixed this works:nix run nixpkgs#llvmPackages_14.lldb -- --version
.Expected behavior
LLDB doesn't show this error, and presumably whatever functionality triggering this isn't working properly but I haven't tried using it after the error(s) are printed.
Additional context
Another LLVM14 package to fix before this is ready for use:
cc #165701
Notify maintainers
@lovek323 @7c6f434c @dtzWill @primeos
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.The text was updated successfully, but these errors were encountered: