stripping binaries installed by rustup results in "Illegal instruction" error message

[sa2ajj]

I just installed rustup on my machine using the curl magic (Debian/testing, x86_64).

After installation I checked the content of the ~/.cargo/bin directory, e.g.:

$ file ~/.cargo/bin/cargo
~/.cargo/bin/cargo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.9, not stripped

and cargo works just fine:

$ cargo 
Rust's package manager

Usage:
    cargo <command> [<args>...]
    cargo [options]

Options:
    -h, --help          Display this message
    -V, --version       Print version info and exit
    --list              List installed commands
    --explain CODE      Run `rustc --explain CODE`
    -v, --verbose       Use verbose output
    -q, --quiet         No output printed to stdout
    --color WHEN        Coloring: auto, always, never

Some common cargo commands are:
    build       Compile the current project
    clean       Remove the target directory
    doc         Build this project's and its dependencies' documentation
    new         Create a new cargo project
    init        Create a new cargo project in an existing directory
    run         Build and execute src/main.rs
    test        Run the tests
    bench       Run the benchmarks
    update      Update dependencies listed in Cargo.lock
    search      Search registry for crates
    publish     Package and upload this project to the registry
    install     Install a Rust binary

See 'cargo help <command>' for more information on a specific command.

However if I strip the binary

$ strip ~/.cargo/bin/cargo
$ file ~/.cargo/bin/cargo
~/.cargo/bin/cargo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.9, stripped

I can't run it any more:

$ cargo
Illegal instruction
$ echo $?
132

[brson]

I can reproduce.

[sa2ajj]

As a side note, I tried locally to build a simple binary:

cargo new --bin check
cd check
cargo build
cargo build --release

both binaries run successfully without and with stripping (for some reason, even release binary is not stripped)

[brson]

Likewise, when I build rustup locally and then strip it it works just fine.

[kinnison]

This is fascinating (I'm issue-spelunking) -- is this reproducible with modern releases of rustup?

[workingjubilee]

@rustbot label: +O-linux