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

rustup fails with fatal: libgcc_s.so.1: open failed: No such file or directory on Sun 10 #3857

Closed
2 tasks done
shanebishop opened this issue Jun 4, 2024 · 3 comments
Closed
2 tasks done
Labels

Comments

@shanebishop
Copy link

shanebishop commented Jun 4, 2024

Verification

Problem

rustup fails on Sun 10.

There are multiple problems that occur:

  1. The /bin/sh that comes with Sun 10 does not support $(...) syntax for subshells. This can be worked around by changing the shebang to /bin/bash, but then there are still the problems below.
  2. Invocations of uname with -o fail with /usr/bin/uname: illegal option -- o.
  3. Invocations of grep with -q fail with grep: illegal option -- q.
  4. Most importantly, rustup fails with
ld.so.1: rustup-init: fatal: libgcc_s.so.1: open failed: No such file or directory
rustup.sh: line 521:  3578 Killed                  "$@"

Steps

  1. Download rustup 1.27.1
  2. Change the shebang to #/bin/bash (to avoid issue 1 above)
  3. SCP the rustup file with the new shebang to a Sun 10 machine
  4. Run chmod +x on the script to give it executable permissions
  5. Run the script

Possible Solution(s)

No response

Notes

I am aware that Sun 10 is not one of the platforms supported by Rust (Rust's support for Sun/Solaris starts with Sun 11). However, I would expect the rustup script to work on Sun 10, in order to allow people to use the script to download a Rust compiler for using custom targets to build on the platform. (But maybe I am assuming too much - maybe there is no pre-built Sun 10 rustc.)

Rustup version

1.27.1

Installed toolchains

The output of rustup show isn't meaningful (there are a bunch of errors).

OS version

Sun 10
@shanebishop shanebishop added the bug label Jun 4, 2024
@rami3l
Copy link
Member

rami3l commented Jun 4, 2024

@shanebishop Thanks a lot for filing this issue!

As you've already found out, according to our current target policy, Solaris 10 is not supported by the Rust project as a whole (i.e. neither as a host nor as a target), so even if Rustup happens to work, there will be no officially distributed rustc and other components, thus it's out of our project's scope to make it possible for a Solaris 10 machine to be used as a compilation host.

If you would like to run Rust programs on such a machine, I personally recommend using the "custom target" feature on a supported host platform, and then find a way to cross-compile for the target in question.

Thanks a lot for your comprehension, and have a nice day!

@rami3l rami3l closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2024
@shanebishop
Copy link
Author

Thanks @rami3l.

In that case, are there instructions somewhere on how to build rustc from source?

@rami3l
Copy link
Member

rami3l commented Jun 4, 2024

@shanebishop Here are some links that might be relevant to your custom target cross-compilation usage:

OTOH compiling rustc itself would be a more involved process, I suggest you make a new post on the Zulip server (https://rust-lang.zulipchat.com) if that's what you need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants