- list_dependants.sh lists packages that depend on $1, eg. list-dependants.sh runtime/squeak-4
static inline void u_thread_setname( const char *name ) | |
{ | |
#if defined(HAVE_PTHREAD) | |
#if DETECT_OS_LINUX || DETECT_OS_CYGWIN | |
int ret = pthread_setname_np(pthread_self(), name); | |
if (ret == ERANGE) { | |
char buf[16]; | |
const size_t len = MIN2(strlen(name), ARRAY_SIZE(buf) - 1); | |
memcpy(buf, name, len); | |
buf[len] = '\0'; |
diff --git a/components/openindiana/gfx-drm/Makefile b/components/openindiana/gfx-drm/Makefile | |
index 7ab7d7e199..7acd07c379 100644 | |
--- a/components/openindiana/gfx-drm/Makefile | |
+++ b/components/openindiana/gfx-drm/Makefile | |
@@ -20,8 +20,8 @@ COMPONENT_NAME= gfx-drm | |
COMPONENT_SRC= $(COMPONENT_NAME) | |
GIT=git | |
-GIT_REPO=https://github.com/illumos/gfx-drm.git | |
-GIT_BRANCH=master |
See https://gist.github.com/Toasterson/90d19ecf4e0b69cfbcd9566a7c098eb8 for the steps.
The problem seems to come from gcc but I have no clue what could be wrong with aarch_aapcs64.s
error: failed to run custom build command for `psm v0.1.21`
Caused by:
process didn't exit successfully: `/var/lib/abuild/rust/build/x86_64-unknown-illumos/stage1-rustc/release/build/psm-61c9c6ef89c427d5/build-script-build` (exit status: 1)
--- stdout
# This file allows any cargo project to cross compile. | |
# Adjust paths to the tools as needed. | |
# place unser .cargo/config inside the project. | |
[target.aarch64-unknown-illumos] | |
linker = "/var/lib/abuild/arm64-gate/build/cross/bin/aarch64-unknown-solaris2.11-gcc" | |
rustflags = [ "-Clink-arg=--sysroot=/var/lib/abuild/arm64-gate/build/sysroot" ] |
- There was a tool request for a tool that takes metadata from recipies and shares them between repos and informs people about new versions of packages on (pkgsrc, oi-userland and omnios build tooling)
- https://repology.org/
- doesn’t notify maintainers
- provides a view of which packages are out of date
- Till has a prototype that will bump versions called “the forge” which will also add activitypub support for friendly forge formatted PR's to upstream activity pub
- https://repology.org/
- Docs
- priority is to guide new people into the process of contributing in various ways process
- What do people need on terms of full tutorials?
- Two diverging versions of IPS (with OI and OmniOS), but only the differing zone brands are a problem.
- Rust version is on the backburner - as it was figured out what the slow issue was in the sheer amount of userland incorporations built by the repo.
#!/bin/ksh93 | |
set -e | |
DISK=$PWD/qemu-setup/illumos-disk.img | |
POOL=armpool | |
MNT=/mnt | |
ROOTFS=ROOT/braich | |
ROOT=$MNT/$ROOTFS | |
DISKSIZE=8g |
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-illumos
aarch64-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
- use https://llvm.org/docs/LangRef.html#data-layout to adjust
data-layout
key according to platfo
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.