generateOptparseApplicativeCompletion should do nothing if we are cross-compiling #174040
Labels
0.kind: bug
6.topic: cross-compilation
Building packages on a different platform than they will be used on
6.topic: haskell
Comments
sternenseemann
added
0.kind: bug
6.topic: haskell
6.topic: cross-compilation
13 tasks
sternenseemann
added a commit
to sternenseemann/nixpkgs
that referenced
this issue
Oct 6, 2022
Deprecate haskell.lib{,.compose}.generateOptparseApplicativeCompletion*
in favor of the newly added
haskell.packages.*.generateOptparseApplicativeCompletions (plural!)
which takes into account whether we are cross-compiling or not. If we
are, generating completions is disabled, since we can't execute software
built for a different platform.
The move is necessary, so we can receive the /same/ stdenv as the
package we are overriding in order to accurately check whether we can
execute produced binaries.
Resolves NixOS#174040.
Resolves NixOS#49648.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It works by executing the compiled and installed executable – something which won't work if we are cross compiling.
The fact that we are may be tricky to detect without introducing another dependency on
pkgsinhaskell.lib– something @Ericson2314 wanted to get rid of.The text was updated successfully, but these errors were encountered: