Location to store binaries

As many of you know, the standard Rust compiler is self-hosting. The upstream bootstrap compiler only works (unmodified) on 64-bit 10.9+. There is an attempt to build a bootstrap compiler that runs on older systems [1]. One stumbling block is where to build and store the bootstrap compilers. I am

Re: Location to store binaries

Right now, I put them in a release section of a fork of Rust: https://github.com/MarcusCalhoun-Lopez/rust/releases Could a similar fork be created under the auspices of the MacPorts project? -Marcus > On Apr 15, 2022, at 3:15 PM, Herby G w

Re: Location to store binaries

Unmodified, the upstream Rust compiler runs on 10.9 and newer. The current rust Portfile uses clever tricks to allow the the upstream Rust compiler to run back to 10.7. However, there is no known way to force the upstream Rust compiler to start using emulated thread-local-storage, so it cannot ru

Re: Location to store binaries

I am glad to know about this ticket, but I do not think it would solve the problem in all cases. If `${prefix}` were other than the default or `port` were invoked with the `-s` switch, then the buildbot would be bypassed entirely, and the rust Portfile would still have to download the Rust boots

Re: Location to store binaries

In the current pull request, there is no dependency. The bootstrap compilers are distfiles. On newer systems, the bootstrap compiler comes from upstream. On older systems, it comes from wherever we choose to put it (currently the less-than-ideal https://github.com/MarcusCalhoun-Lopez/rust/release

Re: Location to store binaries

I have been careful to submit all changes upstreams. So far, most of them have been merged already. The only changes I have not submitted are the ones that apply to systems prior to 10.7, which Rust does not support. These patches are small and can easily be kept as patch files within the port. H

Re: Location to store binaries

Sorry, I misunderstood. Cargo and the Rust Standard Library, which are both required to build Rust, have higher requirements than Rust itself. Back to 10.7, MacPorts gets around this by using, e.g., the MacPorts build of OpenSSL instead of the CommonCrypto system library. Prior to 10.7, MacPorts

Re: Location to store binaries

Have all the concerns about creating a MacPorts version of the Rust bootstrap compiler for older systems been addressed? If so, can we move ahead and ask an owner to create a fork of https://github.com/rust-lang/rust as part of the MacPorts organization? Presumable all MacPorts members would then

Re: The State of Rust in MacPorts Today

I am sorry I have not been a better maintainer for the Rust port. Life has been a little hectic. As has been discussed in this thread, there is definitely room for improvements in the Rust setup. Until a final consensus is reached, I opened a pull request to at least get Rust to its latest versi

Re: The State of Rust in MacPorts Today

Thank you for your efforts to improve the Rust port. I will ask on the mailing list about about moving the Rust binaries to a more suitable location. -Marcus > On Dec 20, 2022, at 9:53 PM, Herby G wrote: > > Thank you for the update, Marcus. I apologize for any harsh tone of mine in > this co

Location to store Rust binaries

As many of you know, the Rust compiler is self-hosting, so Rust is required to build Rust. The problem is that the Rust binaries provided by upstream only work on macOS 10.9 and above. To get around this, there is a rust-bootstrap port that build Rust binaries on 10.9+ intended to build Rust on

Re: Location to store Rust binaries

Please forgive me if I am misunderstanding your question. As Ken pointed out, the rust-bootstrap binaries are generated just fine. I suppose it might be possible to include https://packages.macports.org/ in the `master_sites` of the Rust port. I am afraid I would have to thing about that a little.

Re: Location to store Rust binaries

I am sure everyone who cares about Rust is already familiar with the issues involved, but just for the sake of documentation, I will try to provide an overview. The main issue is that a Rust compiler is required to build a Rust compiler. On an Apple silicon machine running macOS 13, the Rust Por

Re: Location to store Rust binaries

rust-bootstrap can not build on older systems because the upstream binaries won’t run. One downside to using the buildbots for distfiles is that there would be a time period when the 10.5-10.8 buildbots wold fail to build Rust because the 10.9 buildbot hadn’t finished building rust-bootstrap.

Re: qt 6.5.0 removes support for macOS 10.14 and macOS 10.15

Thanks for working on this. I have also been trying to work on the Qt 6 port. However, I have also been trying to modify the Qt 6 PortGroups as well. There are a few things I wish I had done differently in the Qt5 PG and Portfile. However, with so many different Qt5 ports and dependencies, making

Re: qt 6.5.0 removes support for macOS 10.14 and macOS 10.15

I have not looked at the specific issues with Qt 6.5. However, based on our experience with the Qt5 ports, I would suggest sticking to the upstream recommendations concerning supported versions. For Qt5, most of the incompatibilities were in parts of the OS that LegacySupport and other mechanism

Installing zstd CMake files

The package opencolorio uses CMake to find minizip-ng. The minizip-ng’s CMake files assume that the CMake files of zstd exist. However, the CMake files of zstd are installed if and only if zstd is built with CMake (*not* make). According to the README.md of zstd, "`make` is the officially maintain

Re: Installing zstd CMake files

Thank you for the suggestion. However, the variant would have to be default, which would still require cmake, which could still lead to circular dependency with clang. -Marcus > On May 10, 2023, at 9:35 AM, Jason Liu wrote: > > Would it make sense to make it into a variant, instead of a separa

Re: Help with Ticket #68015

Perhaps not. I am not quite sure what constitutes a genuine stack overflow. However, after building the offending binary using the backtrace_on_stack_overflow crate, and I saw no evidence of of infinite recursion (https://docs.rs/backtrace-on-stack-overflow/latest/backtrace_on_stack_overflow/).

Re: question for marcus about rust's compiler_builtins and macosx_deployment_target

Greetings. I am afraid it is very difficult to answer this question without having a much greater insight into Firefox builds. I am not quite sure what libgkrust.a is, but if it is copying files from the Rust supplied libcompiler_builtins-xxx.rlib, then it would make sense that there would be a