Cross compilation fails (wrong capnp invoked) #939
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#939
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
Since
8a5a477ca3
, cross-compiling Lix from x86_64-linux to armv7l-linux fails because the build tries invoking the armv7l build ofcapnp
.Steps To Reproduce
nix-build -E 'with (import <nixpkgs> {}).pkgsCross.armv7l-hf-multiplatform; callPackage ./package.nix { stdenv = clangStdenv; }'
Expected behavior
Successful build
nix --version
outputAdditional context
In
package.nix
,capnproto-lix
is correctly placed in bothnativeBuildInputs
(for running at build time) andbuildInputs
(for linking against). However,capnproto-lix
is provided from the package function's default args and is thus not spliced as the cross-capablecallPackage
(applied topackage.nix
) would usually do. We thus only have thearmv7l
build available, and this is used fornativeBuildInputs
as well.This issue was mentioned on Gerrit on the following CLs: