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: 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

On Apr 17, 2022, at 08:45, Marcus Calhoun-Lopez wrote: > 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 a

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

On Apr 16, 2022, at 10:36, Marcus Calhoun-Lopez wrote: > 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? Yes, it could be. We haven't done that for

Re: Location to store binaries

For the official Rust compiler, we are assured it comes from the official rust-lang Github repository. Rust is a critical build chain component just like gcc is. Introducing a bootstrap compiler means that we are introducing an external element that has the ability to potentially modify Rust itse

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

If a port has a dependency which cannot be compiled from source, shouldn’t -s fail? > On Apr 16, 2022, at 2:08 PM, mcalh...@macports.org wrote: > > 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

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

I think we’re basically discussing https://trac.macports.org/ticket/60878, right? > On Apr 16, 2022, at 11:38 AM, mcalh...@macports.org wrote: > > Unmodified, the upstream Rust compiler runs on 10.9 and newer. > The current rust Portfile uses clever tricks to allow the the upstream Rust > comp

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

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

Maybe i am missing some detail here, but why cannot this bootstrap compiler just be a port like everything else, and thus the binary hosting is just the same as any other binary tarball macports distributes ? > On 15 Apr 2022, at 11:16 pm, Herby G wrote: > >  > Since this would be adding a co

Re: Location to store binaries

Since this would be adding a component that affects the build of a very core build component to many MacPorts packages, perhaps a bit more care should be taken with where it will be stored. Maybe it makes sense for this new bootstrap compiler to live in a repository owned by the MacPorts Github or

Re: Location to store binaries

On 2022-4-15 02:16 , mcalh...@macports.org wrote: 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 whe