[OpenIndiana-discuss] Tasks to focus on

[Carsten Grzemba]

Am 08.01.21 05:15 schrieb Chris  <oidev at bsdos.info>: 
> 
> On 2021-01-07 19:06, Till Wegmueller wrote:
> >On 07.01.21 23:47, Joshua M. Clulow via openindiana-discuss wrote:
> >>On Thu, 7 Jan 2021 at 13:57, Till Wegmueller <toasterson at gmail.com> wrote:
> >>>I will get myself a Physical host with Hetzner with a ton of RAM and CPU
> >>>so we can dedicate some zones and VM's to OpenIndiana building packages.
> >>>Olaf has been working on a revised Jenkins pipeline which fully
> >>>automates PR builds and allows to push them into seperate repos for
> >>>testing with others. So others can just use that repo for testing and
> >>>don't need to build. We will implement that Capability there.
> >>
> >>Before you spend any money, or at least in parallel with doing so, I
> >>would encourage you to see if Fosshost will provide some resources for
> >>the project. They have reached out to illumos in the past, and I
> >>think OpenIndiana meets all of their eligibility criteria (open
> >>source, no commercial backing, etc):
> >>
> >> https://fosshost.org
> >>
> >>It seems they will provide one or more virtual machines to projects
> >>for hosting of web resources and builds and such.
> >>
> >
> >Oh nice will have a talk with them also. That one server is not just for OI, it is
> >also to replace my failed HomeLab server and move stuff from that out to a DC. And
> >then also to host some company resources and others. But Of course I would not
> >need that much RAM for that.
> >
> >Let's see what they can do. But having infrastructure under our control is the
> >Goal. Evercity is doing a very good sponsoring but we need to do updates to the
> >Jenkins infrastructure and redo the setup. So having somewhere where we can do
> >that without needing to burden work onto others is one of our goals with this. And
> >we will also need a couple of package servers.
> You might also be interested in what Oregon State University is offering
> (free to opren source && includes IPv6)
> https://osuosl.org/services/hosting/
> 
> >
> >>>We also talked about making a rustup.mk which will use jmclulows rustup
> >>>work to bootstrap a rust compiler to build rust software and rust itself.
> >>
> >>If you hit any trouble with Rust, I'd love to hear about it! We have
> >>a good relationship with the Rust project itself, so we should be able
> >>to get things fixed as they arise, without needing to float additional
> >>patches.
> 

I try to build firefox 78esr for openindiana. The problems with Rust are much smaller than a while ago. 
 
But I stopped to use the rustc installed with rustup because this use a toolchain naming like x86_64-unknown-illumos.
 
For that the rustc sources build instruction have to extent for target_os "solaris" to target_os "illumos", which is an additional effort.
 
So I updated the oi-userland build reciept for rust to provide an newer version (1.41.1) where the target tripple x86_64-sun-solaris is used. 
 
So there are no patching of lib.rs and others is necessary. 
Or it is possible with rustup to get the target  toolchain x86_64-sun-solaris also?
  
 

> 
> 
> >
> >Will let you know how it went in any case. I expect no big problems though.
> >
> >-Till
> >
> >_______________________________________________
> >openindiana-discuss mailing list
> >openindiana-discuss at openindiana.org
> >https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
> -- 
> ~40yrs of UNIX and counting
> 
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
> 
-- 
Carsten Grzemba