-
-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Cannot run x86 binaries on x86_64 (Exec format error) #51097
Comments
This might be from 4a8fc5b. Could you see if it works without that commit? Also verify that /nix/store/4qj9vzggfzsc34ci79ckaim5cjrwc6ns-bash-4.4-p23/bin/bash executes. I can run it on my system. You can run this to verify that your store is not corrupted:
|
I solved it now for me. Instead of using the 'linuxPackages_testing_hardened' 4.20 linux kernel I switched back to 'linuxPackages_4_19' 4.19.2 kernel and now executing 32 binaries work again. So I guess the hardened kernel does not support executing 32 bit binaries. Does it make sense to have some kind of visible warning here? I normally would not have used the hardened kernel, if that wouldn't have been the only 4.20 version is I get. Its not clear to me when and how those changes in master appear in my nixpkgs/nixos channel (I am on unstable). I would like to use the master branch directly, but I haven't figured out how to best do that yet. |
The same here, hardened kernel 4.18.17 and build failed. building '/nix/store/6h9asn7rc93dbwfcs6xaj3k0qgxmg0vh-libtxc_dxtn-1.0.1.drv'... Thanks |
Maybe the hardened kernel shouldn't set |
It should be 64 bit for the x86_64-linux stdenv. But some packages use the i686 stdenv. |
I am not too familiar with stdenv. Is this expected behaviour that a 64-bit system uses 32-bit binaries? This issue is reproducible building |
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
This should be resolved by #82006 - please reopen if there's still a problem. |
Issue description
I currently cannot execute any 32 bit Linux binaries on my 64 bit system and this breaks updates, since I have 32 bit support enabled in the nix options:
I remember that this worked about a week ago, so something has changed.
I am new to NixOS, so its possible that I have done something wrong. I used ArchLinux for about 9 years before that and now NixOS for just 3 months and its concepts are still foreign for me.
As a long term linux user (about 15 years) I do feel a bit out of place in NixOS. So I am not sure how to fix that myself.
Steps to reproduce
Not sure. I have wine installed and support for 32 bit games enabled.
Then I normally do just 'nixos-rebuild switch --upgrade' to upgrade, and sometimes 'nix-channel --update'. I also regularly do 'nix-collect-garbage -d'.
No idea if that is reproducible or not.
Technical details
The text was updated successfully, but these errors were encountered: