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

cc: Add cross_cpu arg to nixpkgs_cc_toolchain_config #401

Merged
merged 2 commits into from
Aug 15, 2023

Conversation

DolceTriade
Copy link
Contributor

Currently, we hardcode the CPU architecture of the toolchain to the host toolchain. However, this breaks cross compilation as we will probably want to set the CPU of the toolchain to the target architecture. The cross_cpu flag can be used to specify the target architecture. If the cross_cpu flag is not set, we will auto detect the host CPU architecture and use that for the toolchain.

This is part of an effort to address #347

@benradf
Copy link
Member

benradf commented Aug 14, 2023

The CI failures are because README.md needs to be updated with your changes. You can do this by running:

bazel run //docs:update-README.md

Currently, we hardcode the CPU architecture of the toolchain to the host toolchain.
However, this breaks cross compilation as we will probably want to set the CPU
of the toolchain to the target architecture. The `cross_cpu` flag can be used to
specify the target architecture. If the `cross_cpu` flag is not set, we will auto detect the
host CPU architecture and use that for the toolchain.

Is part of an effort to address tweag#347
@DolceTriade
Copy link
Contributor Author

Ah, thanks. Updated.

@DolceTriade
Copy link
Contributor Author

Hm, I'm not certain why my changes aren't showing up here: DolceTriade@17457f6

maybe I should close and re-open...

@DolceTriade DolceTriade changed the base branch from master to ah-test-113 August 15, 2023 08:11
@DolceTriade DolceTriade changed the base branch from ah-test-113 to master August 15, 2023 08:11
@benradf
Copy link
Member

benradf commented Aug 15, 2023

Not sure why CI isn't being triggered now (I don't even see an option to start it manually). Maybe the force push confused it?

I'll try closing the pull request and opening it again.

@benradf benradf closed this Aug 15, 2023
@benradf benradf reopened this Aug 15, 2023
@benradf benradf added the merge-queue merge on green CI label Aug 15, 2023
@mergify mergify bot merged commit 89626d0 into tweag:master Aug 15, 2023
11 checks passed
@mergify mergify bot removed the merge-queue merge on green CI label Aug 15, 2023
@DolceTriade DolceTriade deleted the cross branch August 15, 2023 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants