# Ship \`clang\` in rustup too **URL:** \ **Category:** tools and infrastructure\ **Created:** [November 23, 2024, 8:42pm UTC](https://internals.rust-lang.org/t/ship-clang-in-rustup-too/21908 "2024-11-23T20:42:11Z")\ **Posts on this page:** 1\ **Showing post:** 16
**Author:** ![NobodyXu](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/nobodyxu/32/9651_2.png) [@NobodyXu](https://internals.rust-lang.org/u/NobodyXu)\ **Post date:** [January 1, 2025, 3:18am UTC](https://internals.rust-lang.org/t/ship-clang-in-rustup-too/21908/16 "2025-01-01T03:18:00Z")
I think bundling zig-cc makes more sense than clang, with clang you'd still have cross compilation issue, zig-cc on the other hand makes it easy to cross compile. P.S. I didn't know there's already a discussion so I opened up a new one. > [@Bundle zig-cc in rustup by default](https://internals.rust-lang.org/t/bundle-zig-cc-in-rustup-by-default/22096): > > Motivation Having a C compiler is necessary for many crates, for example, https, tls, compression/decompression. For http, even if rustls is used, it would still have to pull in ring which has a build-script to compile the C code and assembly code. For compression/decompression, the most widely used algorithms such as zstd, libz/flate, xz are implemented in C and would require a C compiler to compile. This means that many rust users have to install a C compiler after experiencing confusing bu… --- _[View the full topic](https://internals.rust-lang.org/t/ship-clang-in-rustup-too/21908)._