Rust 1.26.0 fails to build via homebrew on OS X 10.10.5 #50776
Comments
|
Any update? |
pnkfelix
added
the
T-compiler
|
Triage; @cilia Hello, are you still having this issue on the latest release? |
|
@Aaronepower Yes, just tried 1.29.1, still failing. Please see the error msg below
|
|
discussed at compiler team meeting. I don't know if anyone on the team claims responsibility for helping with homebrew (or relatively old version of OS X). Assigning to self to investigate. |
pnkfelix
added
P-medium
|
(marking as P-high to remind self to investigate circumstances of bug. But the particulars: Homebrew + old Mac OS X version could well lead to P-medium triaging.) |
|
while I wait for some trial runs to go forward on my machine, here is a potentially relevant question: @cilia , what version of XCode do you have installed on your system? (I think running |
|
In the meantime, I have successfully installed rust 1.30 from homebrew on Mac OS X 10.13 "High Sierra"; but I'm pretty sure that install was using prebuilt binaries. I'm trying again now with the In parallel, I have briefly experimented with trying to set up a VMWare image with Mac OS X 10.10 "Yosemite"; but it seems to be a bit of a pain to get such a configuration working. (It appears one might need to first download and install "Mountain Lion" on the VM, and then do an upgrade? Except the App Store won't let me download "Mountain Lion" because its not compatible with this laptop...) (Mac OS X 10.10 "Yosemite" was released Oct 2014, so it is pretty old at this point...) |
pnkfelix
changed the title
|
I was indeed able to do So this seems like a problem one needs to pull out an old OS to replicate... |
|
(I grabbed .dmg images of old installation media, since Apple does keep those available for download, but I was not able to use them with vmware, even after converting them to .iso's in Disk Utility... so, no progress yet in replicating this...) |
|
I don't know if its realistic for us to resolve this problem. Cc @rust-lang/release should we just officially state that we don't actively support building new versions of Rust atop such old versions of Mac OS X? If so, what should we say is minimum supported Mac OS X version? Nominated for discussion amongst T-release team. |
pnkfelix
added
T-release
|
So this is a bit of a complicated question. On the vendor side Apple does not ever announce a "end of life" for any of the major operating system versions, they simply stop updating them. Historically though if we're going by Apple's security updates, the last three releases, including the current one are supported. So today that would be Catalina (10.15), Mojave (10.14.6), and High Sierra (10.13.6). So for this issue Yosemite (10.10) would definitely fall out of the support window. Someone else who knows more about our current infra could probably answer to how difficult it is to build and test for older apple platforms. |
|
I am in favor of closing this as won't fix. It seems pretty clear that reproducing it (and so tracking down where the SIGSEGV is coming from) is pretty hard, so we probably can't easily track down the root cause and fix it; furthermore, I'd say that if the bug is strictly that homebrew can't build Rust then that's also likely out of scope for this issue tracker. I believe we currently support cross-compile targeting "64-bit OSX (10.7+, Lion+)" per the platform support page. But that's not where Rust itself can be built, right? |
|
closing as wont fix, following reasoning given by @Mark-Simulacrum |
|
follow-up discussion with @Mark-Simulacrum leads me to reopen. But I'm going to remove nomination label. cc rust-lang/release-team#2 |
|
I just wanted to add my experience to this. ==> Installing vala dependency: rust
==> ./configure --prefix=/usr/local/Cellar/rust/1.49.0_1 --release-channel=stable
==> make
==> make install
==> ./install.sh --prefix=/private/tmp/rust-20210201-21234-2auhx1/rustc-1.49.0-src/cargobootstrap
==> cargo install /usr/local/Cellar/rust/1.49.0_1 --features curl-sys/force-system-lib-on-osx
Last 15 lines from /Users/frak/Library/Logs/Homebrew/rust/05.cargo:
| this method call resolves to `&T`
|
= note: cannot satisfy `std::string::String: AsRef<_>`
error: aborting due to previous error
For more information about this error, try `rustc --explain E0283`.
error: could not compile `cargo`
To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: failed to compile `cargo v0.50.0 (/private/tmp/rust--cargo-20210201-21234-fgm2gx)`, intermediate artifacts can be found at `/private/tmp/rust--cargo-20210201-21234-fgm2gx/target`
Caused by:
build failed
Do not report this issue to Homebrew/brew or Homebrew/core!
These open issues may also help:
Rust-dependent formulae on Apple Silicon - upstream issue tracker https://github.com/Homebrew/homebrew-core/issues/68301
Error: You are using macOS 10.13.
We (and Apple) do not provide support for this old version.
You will encounter build failures with some formulae.
Please create pull requests instead of asking for help on Homebrew's GitHub,
Twitter or any other official channels. You are responsible for resolving
any issues you experience while you are running this
old version.I then installed rust manually via |
|
I have run into the exact same problem as you, although i was trying to upgrade ffmpeg. What has worked for me was to use the most up-to-date formula i could find that still had a bottle for high-sierra. Basically i ran Then i ran Hope this helps... |
|
@andrewleek-droplab |
|
@andrewleek-droplab answer didn't works for me, still having issues with rust or cargo :( @frakman1 : https://docs.brew.sh/Formula-Cookbook#homebrew-terminology |
|
@andrewleek-droplab -- worked for me, also trying to upgrade ffmpeg ! Mac OSX High Sierra 10.13.6 Had to brew edit formulas from the same repository for cargo-c and rav1e, but other dependencies worked, except had to force the current asciidoc to link (brew link --overwrite asciidoc) after brew upgrade ffmpeg completed. Really appreciate the tip, gave me a key window into the whole brew getup, have a sense now of how and where I can start trying to hack install processes like brew, an area I'd never gotten into. :-) |
|
@andrewleek-droplab's method doesn't seem to work anymore, at least not for me (on High Sierra). Now I get |
|
@andrewleek-droplab and such. Googling this particular error suggests the compiler is looking at a wrong header, belonging to another suite. I don't know how to change the header search path. Using macOS 10.10.6 (High Sierra), CommandLineTools 10.14 EDIT: wait the tool wasn't lld but llvm_ar for Seems Apple's clang, and gcc, got a bit farther than llvm. |
|
@Jerry1144 I’m having the exact same issue. Can’t seem to find a fix or workaround for it running High Sierra. |
|
I am facing the same issue. I am installing facebook watchman....while installing watchman it is installing its dependency which is rust....and brew is not able to install rust on high serria |
|
Is it perhaps possible to install rust from some other source and make Homebrew think it's already installed? |
|
LMAO I just downloaded the binaries from https://ffbinaries.com/downloads, threw them in the ffmpeg folder in the cellar and ran brew link ffmpeg |
|
I was able to successfully build rust via pyenv, and then use my pyenv version of Python to keep Homebrew happy, by following the instructions in this article: https://towardsdatascience.com/homebrew-and-pyenv-python-playing-pleasantly-in-partnership-3a342d86319b?gi=65a5fb85c2e1 . So there is evidence of one possible workaround... Running High Sierra 10.13.6, pyenv 2.1.0, python 3.9.7, current Homebrew (7.5.0) On edit: Or, one could also get the latest/greatest via rustup by doing "curl https://sh.rustup.rs -sSf | sh", copy the binaries into /usr/local/Cellar/rust/\version/bin (currently 1.55.0), and run "brew link rust". It also seems to work, and nothing has exploded into flames (yet). However, do this sort of nastiness at your own risk... Since rust is a dependency for so many things in the Homebrew world, please let me beg for clean High Sierra support for those of us who stay with that old version to still have legacy HFS+... We're not Luddites- we are simply multiply-burned and cautious. Bring back that bottle! |
|
I was having @Jerry1144's exact same issue, so I followed @skodises' suggestion:
Seems to kind of work, but every cargo dependency now has to be installed and linked in a similar way or we get this error: ==> cargo install
Last 15 lines from /Users/{user}/Library/Logs/Homebrew/{dependency}/01.cargo:
2021-11-14 15:14:43 +0000
cargo
install
--locked
--root
/usr/local/Cellar/{dependency}/{version}
--path
.
error: no override and no default toolchain set |
|
I was able to successfully install the latest rust version |
|
FYI: with some work for last week I've successfully build Future more, with some additional work it is possible to add 10.6 but it may requires a |
|
@pnkfelix is it possible to build (somehow) |
|
I was able to get brew to install rust version 1.56.1 on my High Sierra MacOS using the link from bvahdat. |
|
Big thanks to @carlocab. After a clean homebrew uninstall and reinstall, rust finally installed nicely on High Sierra without editing any files. |
|
Closing, presuming fixed on Homebrew side. |
Trying to compile and install Rust 1.26.0 on OSX 10.10.5 using Homebrew. Tried a couple of times, both failed with the same msgs, which seemed the failure happened at
cargoorstd. Please see msgs belowReddit discussion here
The text was updated successfully, but these errors were encountered: