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

we need a pkgsCross smoke test #243320

Closed
ghost opened this issue Jul 13, 2023 · 1 comment · Fixed by #243321
Closed

we need a pkgsCross smoke test #243320

ghost opened this issue Jul 13, 2023 · 1 comment · Fixed by #243321
Labels
0.kind: bug Something is broken 6.topic: llvm/clang Issues related to llvmPackages, clangStdenv and related

Comments

@ghost
Copy link

ghost commented Jul 13, 2023

Until recently, nixpkgs' cross-compilation infrastructure was considered a sort of exotic/best-effort thing, without much CI or testing until things got to Hydra. That's no longer the case, and we are starting to depend on pkgsCross for increasingly important stuff.

We need a package-sized (i.e. not needing hydra-eval-jobs) build that people can run when refactoring our cross-compilation infrastructure.

When I wrote #238154 I tested it thouroughly on all the targetPlatforms I encounter on a regular basis, but since I don't use LLVM much or Windows at all I neglected to try pkgsLLVM and pkgsCross.<various-windows-flavors>. That's not cool.

@ghost
Copy link
Author

ghost commented Jul 13, 2023

Can we cross-compile from x86_64-linux to Darwin without Apple-proprietary tooling? If so, this should include some basic test of that.

@ghost ghost closed this as completed in #243321 Jul 15, 2023
@rrbutani rrbutani added the 6.topic: llvm/clang Issues related to llvmPackages, clangStdenv and related label May 28, 2024
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: bug Something is broken 6.topic: llvm/clang Issues related to llvmPackages, clangStdenv and related
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant