You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
Till Wegmüller
Toasterson
Love OpenSource and the Community. Maintainer for the OpenIndiana Project.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This guide is intended to get people started to Organise and maintain forks of illumos-gate similar to
illumos-omnios or illumos-joyent. While the reasons one might want to make a fork might be many or how
long that fork should exist, it is not in the scope of this guide to give information on why one should
do this. It is assumed this reasoning has already happened and the reader wants to maintain a temporarily or
full fork. All steps can be done with the GitHub CLI aswell but since that does not compile on illumos yet,
it is left out of this guide.
Starting the fork.
To start the fork with purely git, use github's fork button. Then Clone the new fork. replace my username toasterson
When we make applications and libraries interacting with illumos there are a couple of common things everybody needs to do.
On one hand operating the Systems tools to manage things like links but also to edit and manage files.
Configuration management is out of scope for this library but some of the parts of it should have idempotent components
(the Rust Standard library already has the others and we use those when needed)
When implmeneting some of these it will initially need a need that justifies it. But once that person has done it and contributed their work
we will see others making application because it gets easier.
This instructions are temporary and will later be simplified once we provide libstd and libc precompiled and as target installable via packages. But for now it outlines the process needed to get a standard rust compiler to compile unknown illumos arch combination like sparcv9-unknown-illumosaarch64-unknown-illumos and riscv64-unknown-illumos
Note: if your crate needs an external C Library you will have to fiddle with it a bit to properly set the include and cross build directives that crate supports.
Get Rustup via the normal channels (goto https://rustup.rs copy and paste OSX instructions)
Install Nightly toolchain
print an already existing illumos rustc target and adjust to the target CPU rustc +nightly -Z unstable-options --target=aarch64-unknown-linux --print target-spec-json
check other OS's spec files for that CPU to see what is OS specific (most) and what is CPU specific