-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Use crosstool-ng for dist-arm-linux-musl #143763
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
base: master
Are you sure you want to change the base?
Conversation
Almost all of the musl dist jobs use crosstool-ng, only the aarch64 and x86_64 jobs use musl-cross-make. Let's start transitioning the remaining jobs over to crosstool-ng and start dropping musl-cross-make. Signed-off-by: Jens Reidel <adrian@travitia.xyz>
r? @marcoieni rustbot has assigned @marcoieni. Use |
I think you can just rename it (together with the corresponding docker image). You can do it in another PR, too. I'm reviewing the PR 👀 |
CT_ARCH_ARCH="armv6" | ||
CT_ARCH_FLOAT_SW=y | ||
CT_ARCH_64=y | ||
# CT_DEMULTILIB is not set |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we explain why this is not set? 🤔
CT_BINUTILS_V_2_32=y | ||
CT_GLIBC_V_2_17=y | ||
CT_GCC_V_8=y | ||
CT_LINUX_V_4_19=y |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why we increased this version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This crosstool-ng config was unused before and for ARMv7. The musl-cross-make toolchain used before had 4.19 headers
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And no, I don't know why it was here or why it was for a 32-bit glibc toolchain :) Some of these dist jobs are a mess, which is why I'm trying to clean them up a bit
@bors try |
Use crosstool-ng for dist-arm-linux-musl Almost all of the musl dist jobs use crosstool-ng, only the aarch64 and x86_64 jobs use musl-cross-make. Let's start transitioning the remaining jobs over to crosstool-ng and start dropping musl-cross-make. I noticed that this job is called `dist-arm-linux-musl`, but the GNU pendant is called `dist-aarch64-linux`. How would I go about renaming `dist-arm-linux-musl` to `dist-aarch64-linux-musl`? Is there any external effort required or can I just rename it in the repo? try-job: dist-arm-linux-musl
☀️ Try build successful - checks-actions |
I downloaded the try build artifacts and compared them with the auto build artifacts from the last commit on master.
Is this size increase expected? |
Seems a bit weird. I downloaded them and at first glance, only the rustc binary is a tiny bit larger indeed. autobuild:
try-build:
I have a feeling that this is related to the changed CFLAGS. |
Almost all of the musl dist jobs use crosstool-ng, only the aarch64 and x86_64 jobs use musl-cross-make. Let's start transitioning the remaining jobs over to crosstool-ng and start dropping musl-cross-make.
I noticed that this job is called
dist-arm-linux-musl
, but the GNU pendant is calleddist-aarch64-linux
. How would I go about renamingdist-arm-linux-musl
todist-aarch64-linux-musl
? Is there any external effort required or can I just rename it in the repo?try-job: dist-arm-linux-musl