State of Rust on DragonFly

[Zachary Crownover]

That won't happen unless we have an active maintainer for it with Rust that
can get the project to move DragonFly from tier 3 to at least tier 2. I'd
like to take an active role in that though.

On Jun 29, 2017 9:55 AM, "Carsten Mattner" <carstenmattner at gmail.com> wrote:

> On Wed, Jun 28, 2017 at 6:49 AM, Michael Neumann <mneumann at ntecs.de>
> wrote:
> > Hi,
> >
> > I am working on getting Rust 1.18.0 into the ports. There was an issue
> > with errors happening in parallel builds triggered by cargo (Rust's
> > package manager also used to build Rust itself). By disabling parallel
> > builds I were able to successfully bootstrap Rust 1.18.0 from 1.17.0.
> >
> > I need to produce dependency-free versions of cargo before I can work on
> > integrating everything into the ports tree.
> >
> > All scripts to bootstrap can be found on [1]. To build Rust 1.18.0, just
> > run "sh build-1.18.0.sh /working/directory/for/build". Because of the
> > version of cargo I am currently using, this might only work if you have
> > the same version of DragonFly (I am working on a statically linked
> > version of cargo).
> >
> > I will keep you updated on the progress. And sorry for the delay. I just
> > found the issue with cargo two days ago. This issue blocked all my
> > further efforts.
>
> Great work Michael!
>
> Please keep it up and ideally get it to the level of FreeBSD so
> that we can just use rustup to have all of the versions and
> toolchains and targets available. That would be a dream.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20170629/413d5b98/attachment-0003.htm>