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

Remove cross-compilation from linux x86 in Rust CI #190

Open
4 tasks
marcoieni opened this issue Jan 20, 2025 · 2 comments
Open
4 tasks

Remove cross-compilation from linux x86 in Rust CI #190

marcoieni opened this issue Jan 20, 2025 · 2 comments

Comments

@marcoieni
Copy link
Member

GitHub introduced free arm runners, which are faster than x86 free runners.

There are many jobs where we use the x86 free runner to cross compile because a free arm runner wasn't available at the time.

Tasks

Remove cross-compilation from x86 to arm

Remove cross-compilation from x86 to all other architectures

  • list all linux jobs that cross compile from x86 to the other architectures (e.g. powerpc)
  • convert those jobs if the new runner is faster and cheaper

Additional context

Discussed in zulip.

@nikic
Copy link

nikic commented Jan 20, 2025

I find the description in this issue quite confusing. If I'm understanding correctly, what you're actually proposing is to use arm runners instead of x86 runners as the host for builds that use cross-compilation, not to remove the cross-compilation. For dist-arm-linux, you'd still cross-compile from ARM to ARM, right? You're not proposing to remove the use of crosstool-ng?

@marcoieni
Copy link
Member Author

If I'm understanding correctly, what you're actually proposing is to use arm runners instead of x86 runners as the host for builds that use cross-compilation, not to remove the cross-compilation.

Yes

For dist-arm-linux, you'd still cross-compile from ARM to ARM, right?

This issue doesn't regard dist-arm-linux as the host is not x86. 👍

You're not proposing to remove the use of crosstool-ng?

No

So I think you got it right, sorry for the poor explanation!

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

No branches or pull requests

2 participants