redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2018-07-15T19:31:58Zhttps://gitlab.redox-os.org/redox-os/coreutils/-/issues/79implement `sort` command2018-07-15T19:31:58ZJeremy Sollerimplement `sort` commandThere is no `sort` command.
It should sort alphabetically by default, and accept `-n` for sorting numerically
There is no `sort` command.
It should sort alphabetically by default, and accept `-n` for sorting numerically
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/78`sleep` should not accept negative durations2018-07-15T19:31:58ZJeremy Soller`sleep` should not accept negative durations*Created by: xTibor*
The `sleep` command currently accepts negative durations, for example `sleep -1s`, which causes the command to wait indefinitely (possibly integer wrap-around).
It should not accept these durations but should raise...*Created by: xTibor*
The `sleep` command currently accepts negative durations, for example `sleep -1s`, which causes the command to wait indefinitely (possibly integer wrap-around).
It should not accept these durations but should raise errors on them.
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/76Human readable sizes2018-07-15T19:31:58ZJeremy SollerHuman readable sizesHuman readable sizes in ls and du
Human readable sizes in ls and du
https://gitlab.redox-os.org/redox-os/ralloc/-/issues/37Build on nightly failing2018-06-27T15:36:22ZJeremy SollerBuild on nightly failing*Created by: syepes*
Hello,
Are there any plans on upgrading the "clippy" dependency? this is making the nightly build fail:
Env:
```
nightly-x86_64-unknown-linux-gnu (default)
rustc 1.14.0-nightly (9c31d76e9 2016-10-03)
```
Build:
...*Created by: syepes*
Hello,
Are there any plans on upgrading the "clippy" dependency? this is making the nightly build fail:
Env:
```
nightly-x86_64-unknown-linux-gnu (default)
rustc 1.14.0-nightly (9c31d76e9 2016-10-03)
```
Build:
```
Compiling clippy_lints v0.0.85
error[E0252]: a type named `TyArray` has already been imported in this module
--> /home/syepesfernandez/.cargo/registry/src/github.com-1ecc6299db9ec823/clippy_lints-0.0.85/src/array_indexing.rs:7:5
|
3 | use rustc::ty::TyArray;
| ------------------ previous import of `TyArray` here`
```
https://gitlab.redox-os.org/redox-os/termion/-/issues/50Panic on reading non-ascii symbols from async_stdin2018-10-15T22:28:37ZMichael Aaron Murphymmstick@pm.mePanic on reading non-ascii symbols from async_stdin*Created by: aleksander*
This minimum example
``` Rust
extern crate termion;
fn main() {
use termion::input::TermRead;
let mut stdin = termion::async_stdin().keys();
loop {
if let Some(Ok(termion::event::Key::Char('...*Created by: aleksander*
This minimum example
``` Rust
extern crate termion;
fn main() {
use termion::input::TermRead;
let mut stdin = termion::async_stdin().keys();
loop {
if let Some(Ok(termion::event::Key::Char('q'))) = stdin.next() {
break;
}
}
}
```
works as expected on input:
`echo "q" | RUST_BACKTRACE=1 ./target/debug/async_test`
but panics on this:
`echo "й" | RUST_BACKTRACE=1 ./target/debug/async_test`
Backtrace:
```
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', ../src/libcore/option.rs:317
stack backtrace:
1: 0x55eef2d60dc3 - std::sys::backtrace::tracing::imp::write::h46f28e67d38b4637
2: 0x55eef2d642cd - std::panicking::default_hook::{{closure}}::h1d3243f546573ff4
3: 0x55eef2d6383a - std::panicking::default_hook::h96c288d728df3ebf
4: 0x55eef2d63e38 - std::panicking::rust_panic_with_hook::hb1322e5f2588b4db
5: 0x55eef2d63cd2 - std::panicking::begin_panic::hfbeda5aad583dc32
6: 0x55eef2d63c10 - std::panicking::begin_panic_fmt::h4fe9fb9d5109c4bf
7: 0x55eef2d63b91 - rust_begin_unwind
8: 0x55eef2d99a2f - core::panicking::panic_fmt::h4395919ece15c671
9: 0x55eef2d9995b - core::panicking::panic::hc74ff52ed78364e1
10: 0x55eef2d34dba - <core::option::Option<T>>::unwrap::h15693cb33eb11843
at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libcore/macros.rs:21
11: 0x55eef2d437d5 - termion::event::parse_utf8_char::he796d2eaa24dc8c0
at /home/x/.cargo/registry/src/github.com-1ecc6299db9ec823/termion-1.0.8/src/event.rs:283
12: 0x55eef2d4120a - termion::event::parse_event::h6ac22cfa12aeaa31
at /home/x/.cargo/registry/src/github.com-1ecc6299db9ec823/termion-1.0.8/src/event.rs:264
13: 0x55eef2d43f94 - <termion::input::Events<I> as core::iter::iterator::Iterator>::next::h7ff33bf7c94953bc
at /home/x/.cargo/registry/src/github.com-1ecc6299db9ec823/termion-1.0.8/src/input.rs:40
14: 0x55eef2d43a7f - <termion::input::Keys<I> as core::iter::iterator::Iterator>::next::h178cb3a21de07e28
at /home/x/.cargo/registry/src/github.com-1ecc6299db9ec823/termion-1.0.8/src/input.rs:19
15: 0x55eef2d445b4 - async_test::main::h16c6b4cc4e0e7310
at /tmp/async_test/src/main.rs:6
16: 0x55eef2d6bd96 - __rust_maybe_catch_panic
17: 0x55eef2d630b1 - std::rt::lang_start::haaae1186de9de8cb
18: 0x55eef2d44873 - main
19: 0x7feae2be2740 - __libc_start_main
20: 0x55eef2d335d8 - _start
21: 0x0 - <unknown>
```
https://gitlab.redox-os.org/redox-os/redox/-/issues/709Build Error: AssertParamIsEq and AssertParamIsClone are 'undefined or not in ...2018-06-15T11:40:02ZJeremy SollerBuild Error: AssertParamIsEq and AssertParamIsClone are 'undefined or not in scope'*Created by: jeromefroe*
Hello, I'm having difficulties building redox. I pulled from master today and am using the nightly version of Rust but am getting an error when compiling rust/src/libcore/lib.rs as described below. I think the e...*Created by: jeromefroe*
Hello, I'm having difficulties building redox. I pulled from master today and am using the nightly version of Rust but am getting an error when compiling rust/src/libcore/lib.rs as described below. I think the error may be related to my linker not being able to find `AssertParamIsEq` and `AssertParamIsClone` in libcore. Has anyone seen an error like this before by chance? Thanks.
**Reproduction**: `make all`, more specifically the following command:
```
RUST_BACKTRACE=1 rustc --target=i386-unknown-redox.json --cfg redox -L \
build/i386-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C \
opt-level=3 -Z no-landing-pads -A dead_code -C ar=i386-elf-ar -C linker=i386-elf-gcc \
-o build/i386-unknown-redox/debug/libcore.rlib rust/src/libcore/lib.rs
```
**Expected behavior**: redox is built successfully
**Actual behavior**: I see the following errors related to `AssertParamIsEq` and `AssertParamIsClone` being `undefined or not in scope`. From what I can tell both `AssertParamIsEq` and `AssertParamIsClone`are defined in libcore so I believe this may be a problem with my linker. A sample of the output is as follows:
```
error[E0412]: type name `cmp::AssertParamIsEq` is undefined or not in scope
--> rust/src/libcore/num/mod.rs:46:70
|
46 | pub struct Wrapping<T>(#[stable(feature = "rust1", since = "1.0.0")] pub T);
| ^^^^^^ undefined or not in scope
|
= help: no candidates by the name of `AssertParamIsEq` found in your project; maybe you misspelled the name or forgot to import an external crate?
error[E0412]: type name `clone::AssertParamIsClone` is undefined or not in scope
--> rust/src/libcore/num/flt2dec/decoder.rs:27:5
|
27 | pub mant: u64,
| ^^^^^^^^^^^^^ undefined or not in scope
|
= help: no candidates by the name of `AssertParamIsClone` found in your project; maybe you misspelled the name or forgot to import an external crate?
error[E0412]: type name `clone::AssertParamIsClone` is undefined or not in scope
--> rust/src/libcore/num/flt2dec/decoder.rs:29:5
|
29 | pub minus: u64,
| ^^^^^^^^^^^^^^ undefined or not in scope
|
= help: no candidates by the name of `AssertParamIsClone` found in your project; maybe you misspelled the name or forgot to import an external crate?
error[E0412]: type name `clone::AssertParamIsClone` is undefined or not in scope
--> rust/src/libcore/num/flt2dec/decoder.rs:31:5
|
31 | pub plus: u64,
| ^^^^^^^^^^^^^ undefined or not in scope
|
= help: no candidates by the name of `AssertParamIsClone` found in your project; maybe you misspelled the name or forgot to import an external crate?
```
The same type of errors appears about forty or so more times.
**Build information**:
`rustc -V`: rustc 1.13.0-nightly (55bf6a4f8 2016-09-18)
`git rev-parse HEAD`: fdfa25858bae41516ab495a042d8cc8cf0d8c565
`qemu-system-i386 -version`: QEMU emulator version 2.7.0, Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers
`uname -a`: Darwin jeromefroe-C02RN36CFVH8 15.6.0 Darwin Kernel Version 15.6.0: Mon Aug 29 20:21:34 PDT 2016; root:xnu-3248.60.11~1/RELEASE_X86_64 x86_64
**Blocking/related**: N/A
**Misc**: N/A
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/73Date Formatting2018-07-15T19:31:58ZJeremy SollerDate Formatting*Created by: rushsteve1*
The `date` command currently just prints the unix timestamp, and while this works for basic functionality we should look into using something like [rust-chrono](https://github.com/lifthrasiir/rust-chrono) or our...*Created by: rushsteve1*
The `date` command currently just prints the unix timestamp, and while this works for basic functionality we should look into using something like [rust-chrono](https://github.com/lifthrasiir/rust-chrono) or our own implementation to format it into a human readable format.
https://gitlab.redox-os.org/redox-os/termion/-/issues/49Question: what is the proper way to poll events?2018-10-15T22:28:37ZMichael Aaron Murphymmstick@pm.meQuestion: what is the proper way to poll events?*Created by: little-dude*
Hi,
I'd like to read events in a non-blocking way, which is not possible with `termion::input::Events` since calling `next()` blocks. I tried the following:
``` rust
pub struct Input {
tx: mpsc::Sender<te...*Created by: little-dude*
Hi,
I'd like to read events in a non-blocking way, which is not possible with `termion::input::Events` since calling `next()` blocks. I tried the following:
``` rust
pub struct Input {
tx: mpsc::Sender<termion::event::Event>,
rx: mpsc::Receiver<termion::event::Event>,
}
impl Input {
pub fn new() -> Input {
let (tx, rx) = mpsc::channel();
Input {
tx: tx,
rx: rx,
}
}
pub fn run(&mut self) {
let tx = self.tx.clone();
thread::spawn(move || {
let events = input::Events {
// does not compile!
bytes: async_stdin().bytes()
};
loop {
match events.next() {
Some(result) => {
match result {
Ok(event) => {
tx.send(event);
},
Err(err) => {
error!("{:?}", err);
},
}
},
None => {},
}
}
});
}
}
```
Then I could do something like this:
``` rust
let mut input = Input::new();
input.run();
loop {
match input.rx.try_recv() {
Ok(event) => {
match event {
// TODO: handle the event
_ => {}
}
}
Err(_) => {
// Just wait a little bit before continuing so that we don't eat too much cpu
thread::sleep_ms(10);
}
}
// Do other stuff here
// [...]
}
```
However my code does not compile:
``` rust
error[E0451]: field `bytes` of struct `termion::input::Events` is private
--> src/main.rs:66:17
|
66 | bytes: async_stdin().bytes()
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ field `bytes` is private
```
I assume this field is private for a good reason, and I'm doing things the wrong way.
What would be the "right" way to poll events?
Sorry if the code is not very good, I'm still struggling with rust basics.
https://gitlab.redox-os.org/redox-os/redox/-/issues/708libfuse problems (does it need a specific version from libfuse?)2023-06-13T04:42:47ZJeremy Sollerlibfuse problems (does it need a specific version from libfuse?)*Created by: vpereira*
by `make all` the fuse crate complains about some missing functions from libfuse. I suspect that I have to have a specific version from libfuse? However searching on the master branch from libfuse I couldn't find ...*Created by: vpereira*
by `make all` the fuse crate complains about some missing functions from libfuse. I suspect that I have to have a specific version from libfuse? However searching on the master branch from libfuse I couldn't find those "missing functions" either.
I'm using Linux openSUSE, here are the packages that I have installed (related with libfuse):
vpereira@kimura:~/dev/redox> lsmod | grep fuse
fuse 106496 3
vpereira@kimura:~/dev/redox> zypper info fuse-devel
Loading repository data...
Reading installed packages...
## Information for package fuse-devel:
Repository: openSUSE-42.1-0
Name: fuse-devel
Version: 2.9.3-8.2
Arch: x86_64
Vendor: openSUSE
Installed: Yes
Status: up-to-date
Installed Size: 280.7 KiB
Summary: Development package for FUSE (userspace filesystem) modules
Description:
This package contains all include files, libraries and configuration
files needed to develop programs that use the fuse (FUSE) library to
implement kernel-default (Linux) file systems in user space.
With fuse-devel, administrators can compile and install other user
space file systems which can be found at
http://fuse.sourceforge.net/wiki
vpereira@kimura:~/dev/redox> zypper info fuse
Loading repository data...
Reading installed packages...
## Information for package fuse:
Repository: openSUSE-42.1-0
Name: fuse
Version: 2.9.3-8.2
Arch: x86_64
Vendor: openSUSE
Installed: Yes
Status: up-to-date
Installed Size: 242.4 KiB
Summary: User space File System
Description:
With FUSE, a user space program can export a file system through the
kernel-default (Linux kernel).
User space file systems which are implemented using FUSE are provided
by the following packages:
- curlftpfs (mount FTP servers),
- encfs (layered file encryption),
- fuseiso (mount iso, img, bin, mdf and nrg CD-ROM images),
- fusepod (mount iPods),
- fusesmb (mount a fully browseable network neighborhood),
- gphotofs (mount gphoto-supported cameras),
- ntfs-3g (mount NTFS volumes read-write),
- obexfs (mount of bluetooth devices),
- sshfs (mount over ssh),
- wdfs (mount of WebDAV shares)
This package contains the mount binaries for fuse (might not be needed
by some FUSE filesystems like ntfs-3g) and the documentation for FUSE.
After installing fuse-devel, administrators can compile and install
other user space file systems which can be found at
http://fuse.sourceforge.net/wiki
Backtrace from `make all`
echo exit | cargo run --manifest-path crates/redoxfs/Cargo.toml --bin redoxfs-utility build/i386-unknown-redox/debug/filesystem.bin
Finished debug [unoptimized + debuginfo] target(s) in 0.0 secs
Running `crates/redoxfs/target/debug/redoxfs-utility build/i386-unknown-redox/debug/filesystem.bin`
redoxfs: created filesystem build/i386-unknown-redox/debug/filesystem.bin
redoxfs# mkdir -p build/i386-unknown-redox/debug/filesystem/
cargo run --manifest-path crates/redoxfs/Cargo.toml --bin redoxfs-fuse build/i386-unknown-redox/debug/filesystem.bin build/i386-unknown-redox/debug/filesystem/ &
sleep 2
Compiling redoxfs v0.1.0 (file:///home/vpereira/dev/redox/crates/redoxfs)
error: linking with `cc` failed: exit code: 1
|
= note: "cc" "-Wl,--as-needed" "-Wl,-z,noexecstack" "-m64" "-L" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/redoxfs_fuse.0.o" "-o" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/redoxfs_fuse" "-Wl,--gc-sections" "-pie" "-nodefaultlibs" "-L" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/deps" "-L" "/usr/lib64" "-L" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-Wl,-Bstatic" "-Wl,-Bdynamic" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/deps/libredoxfs.rlib" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/deps/libfuse-d47811d01e926407.rlib" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/deps/libtime-750bfdd52feafcb7.rlib" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/deps/liblog-bf16bb9a4912b11d.rlib" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/deps/liblibc-1417726cb94dbc83.rlib" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/deps/liblibc-0c57a2126eb1e7e8.rlib" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/deps/libsystem.rlib" "/home/vpereira/dev/redox/crates/redoxfs/target/debug/deps/libthread_scoped-6ad7d7414456fed5.rlib" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd-411f48d3.rlib" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libpanic_unwind-411f48d3.rlib" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libunwind-411f48d3.rlib" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librand-411f48d3.rlib" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcollections-411f48d3.rlib" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_unicode-411f48d3.rlib" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/liballoc-411f48d3.rlib" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/liballoc_jemalloc-411f48d3.rlib" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/liblibc-411f48d3.rlib" "/home/vpereira/.multirust/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore-411f48d3.rlib" "-l" "fuse3" "-l" "util" "-l" "c" "-l" "m" "-l" "dl" "-l" "pthread" "-l" "gcc_s" "-l" "pthread" "-l" "c" "-l" "m" "-l" "rt" "-l" "util" "-l" "compiler-rt"
= note: /home/vpereira/dev/redox/crates/redoxfs/target/debug/deps/libfuse-d47811d01e926407.rlib(fuse-d47811d01e926407.0.o): In function `fuse::channel::unmount::libc_umount':
/home/vpereira/.cargo/registry/src/github.com-1ecc6299db9ec823/fuse-0.2.8/src/channel.rs:186: undefined reference to`fuse_unmount_compat22'
/home/vpereira/dev/redox/crates/redoxfs/target/debug/deps/libfuse-d47811d01e926407.rlib(fuse-d47811d01e926407.0.o): In function `fuse::channel::{{impl}}::new::{{closure}}::{{closure}}':
/home/vpereira/.cargo/registry/src/github.com-1ecc6299db9ec823/fuse-0.2.8/src/channel.rs:85: undefined reference to`fuse_mount_compat25'
collect2: error: ld returned 1 exit status
error: aborting due to previous error
error: Could not compile `redoxfs`.
To learn more, run the command again with --verbose.
cp -RL filesystem/\* build/i386-unknown-redox/debug/filesystem/
sync
fusermount -u build/i386-unknown-redox/debug/filesystem/
fusermount: entry for /home/vpereira/dev/redox/build/i386-unknown-redox/debug/filesystem not found in /etc/mtab
Makefile:671: recipe for target 'build/i386-unknown-redox/debug/filesystem.bin' failed
make: [build/i386-unknown-redox/debug/filesystem.bin] Error 1 (ignored)
rm -rf build/i386-unknown-redox/debug/filesystem/
nasm -f bin -o build/i386-unknown-redox/debug/harddrive.bin -l build/i386-unknown-redox/debug/harddrive.list -D ARCH_i386 -D TIME="`date "+%F %T"`" -ibuild/i386-unknown-redox/debug/ -ikernel/ -ifilesystem/ kernel/harddrive.asm
https://gitlab.redox-os.org/redox-os/redox/-/issues/705build failed: Makefile:248: recipe for target 'build/i386-unknown-redox/debug...2018-06-15T11:40:03ZJeremy Sollerbuild failed: Makefile:248: recipe for target 'build/i386-unknown-redox/debug/ion-shell.bin' failed*Created by: basiliscos*
```
make all
CARGO_TARGET_DIR=build RUSTC="./rustc-i386.sh" cargo rustc --manifest-path crates/ion/Cargo.toml --bin ion-shell --verbose --target=i386-unknown-redox.json -- --cfg redox -L build/i386-unknown-redox...*Created by: basiliscos*
```
make all
CARGO_TARGET_DIR=build RUSTC="./rustc-i386.sh" cargo rustc --manifest-path crates/ion/Cargo.toml --bin ion-shell --verbose --target=i386-unknown-redox.json -- --cfg redox -L build/i386-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=3 -Z no-landing-pads -A dead_code
Compiling peg v0.3.15
Fresh glob v0.2.11
Fresh termion v1.0.8
Fresh unicode-width v0.1.3
Running `./rustc-i386.sh /home/basiliscos/.cargo/registry/src/github.com-1ecc6299db9ec823/peg-0.3.15/src/peg_syntax_ext.rs --crate-name peg_syntax_ext --crate-type dylib -C prefer-dynamic -g -C metadata=75b7c4fc7124fb6c -C extra-filename=-75b7c4fc7124fb6c --out-dir /home/basiliscos/development/rust/redox/redox/build/debug/deps --emit=dep-info,link -L dependency=/home/basiliscos/development/rust/redox/redox/build/debug/deps --cap-lints allow`
Fresh liner v0.1.3
error: no method named `meta_list_item_word` found for type `&mut syntax::ext::base::ExtCtxt<'_>` in the current scope
--> /home/basiliscos/.cargo/registry/src/github.com-1ecc6299db9ec823/peg-0.3.15/src/peg_syntax_ext.rs:80:12
|
80 | cx.meta_list_item_word(DUMMY_SP, token::InternedString::new("non_snake_case")),
| ^^^^^^^^^^^^^^^^^^^
error: no method named `meta_list_item_word` found for type `&mut syntax::ext::base::ExtCtxt<'_>` in the current scope
--> /home/basiliscos/.cargo/registry/src/github.com-1ecc6299db9ec823/peg-0.3.15/src/peg_syntax_ext.rs:81:12
|
81 | cx.meta_list_item_word(DUMMY_SP, token::InternedString::new("unused")),
| ^^^^^^^^^^^^^^^^^^^
error: aborting due to 2 previous errors
error: Could not compile `peg`.
Caused by:
Process didn't exit successfully: `./rustc-i386.sh /home/basiliscos/.cargo/registry/src/github.com-1ecc6299db9ec823/peg-0.3.15/src/peg_syntax_ext.rs --crate-name peg_syntax_ext --crate-type dylib -C prefer-dynamic -g -C metadata=75b7c4fc7124fb6c -C extra-filename=-75b7c4fc7124fb6c --out-dir /home/basiliscos/development/rust/redox/redox/build/debug/deps --emit=dep-info,link -L dependency=/home/basiliscos/development/rust/redox/redox/build/debug/deps --cap-lints allow` (exit code: 101)
Makefile:248: recipe for target 'build/i386-unknown-redox/debug/ion-shell.bin' failed
make: *** [build/i386-unknown-redox/debug/ion-shell.bin] Error 101
```
https://gitlab.redox-os.org/redox-os/rusttype/-/issues/26What does it mean when PositionedGlyph::draw call back give value of negative...2018-06-13T17:19:47ZJeremy SollerWhat does it mean when PositionedGlyph::draw call back give value of negative float?*Created by: bombless*
I tried a Chinese character "试" and the third argument of the call back gives some negative value like
```
-0.3671875
-0.3671875
-0.3671875
-0.50561523
-0.625
-0.01739502
-0.37109375
-0.37109375
```
I'm using a ...*Created by: bombless*
I tried a Chinese character "试" and the third argument of the call back gives some negative value like
```
-0.3671875
-0.3671875
-0.3671875
-0.50561523
-0.625
-0.01739502
-0.37109375
-0.37109375
```
I'm using a font file "simsunb.ttf" from Windows 10.
https://gitlab.redox-os.org/redox-os/rusttype/-/issues/25Update crates.io version2018-06-13T17:19:47ZJeremy SollerUpdate crates.io version*Created by: ozkriff*
ndarray 0.3 is not building on nightly rust: https://travis-ci.org/ozkriff/zoc/jobs/157466320 :(
*Created by: ozkriff*
ndarray 0.3 is not building on nightly rust: https://travis-ci.org/ozkriff/zoc/jobs/157466320 :(
https://gitlab.redox-os.org/redox-os/rusttype/-/issues/23Use docs.rs for documentation2018-06-13T17:19:47ZJeremy SollerUse docs.rs for documentation*Created by: ozkriff*
https://docs.rs/rusttype
*Created by: ozkriff*
https://docs.rs/rusttype
https://gitlab.redox-os.org/redox-os/playbot/-/issues/1Currently broken2019-06-28T16:54:58ZJeremy SollerCurrently broken*Created by: ticki*
The upstream's request interface changed.
*Created by: ticki*
The upstream's request interface changed.
https://gitlab.redox-os.org/redox-os/redox/-/issues/702build failed ( recipe for target 'build/i386-unknown-redox/debug/libcore.rlib...2018-06-15T11:40:03ZJeremy Sollerbuild failed ( recipe for target 'build/i386-unknown-redox/debug/libcore.rlib' failed )*Created by: basiliscos*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
make all
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
compiled redox
**Actual beh...*Created by: basiliscos*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
make all
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
compiled redox
**Actual behavior**: [describe the actual behavior, which is presented through the repro.].
```
make all
mkdir -p build/i386-unknown-redox/debug
RUST_BACKTRACE=1 rustc --target=i386-unknown-redox.json --cfg redox -L build/i386-unknown-redox/debug -C no-prepopulate-passes -C no-stack-check -C opt-level=3 -Z no-landing-pads -A dead_cod
e -o build/i386-unknown-redox/debug/libcore.rlib rust/src/libcore/lib.rs
error[E0433]: failed to resolve. Could not find `Carrier` in `ops`
--> rust/src/libcore/num/dec2flt/mod.rs:217:40
|
217 | ParseResult::Valid(decimal) => convert(decimal)?,
| ^^^^^^^^^^^^^^^^^ Could not find `Carrier` in `ops`
....
error[E0093]: unrecognized intrinsic function: `init_dropped`
--> rust/src/libcore/intrinsics.rs:258:5
|
258 | pub fn init_dropped<T>() -> T;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ unrecognized intrinsic
error: aborting due to previous error
Makefile:510: recipe for target 'build/i386-unknown-redox/debug/libcore.rlib' failed
make: *** [build/i386-unknown-redox/debug/libcore.rlib] Error 101
```
**Build information**: [output of `rustc -V`, `git rev-parse HEAD`, `qemu-i386 -version`, `uname -a`, etc.]
rustc -V
rustc 1.13.0-nightly (198713106 2016-08-26)
git rev-parse HEAD
ea5a43e63e5855e06d19f4708f3d4bdca4e91d6b
qemu-i386 -version
zsh: command not found: qemu-i386
uname -a
Linux hydra 4.4.11 #2 SMP Thu Jul 7 13:03:52 MSK 2016 x86_64 Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz GenuineIntel GNU/Linux
rustup --version
rustup 0.6.1 (71f7482 2016-08-24)
**Misc**: [optional: for other relevant information that should be known or cannot be described in the other fields.]
---
_If the above does not fit the nature of the issue feel free to modify it._
https://gitlab.redox-os.org/redox-os/redox/-/issues/701Sessions Types for Microkernel Message Passing2023-06-13T04:42:45ZJeremy SollerSessions Types for Microkernel Message Passing*Created by: joehillen*
_Since it has been a week and I didn't get any responses [here](https://discourse.redox-os.org/t/sessions-types-for-microkernel-message-passing/354), I'm reposting this here for visibility. Please close this if I...*Created by: joehillen*
_Since it has been a week and I didn't get any responses [here](https://discourse.redox-os.org/t/sessions-types-for-microkernel-message-passing/354), I'm reposting this here for visibility. Please close this if I'm being impertinent._
I want to propose sessions types to whoever designs the message passing for Redox. As near as I can tell, Redox does not yet have its message passing system laid out (after a quick check of the code, forum, and book). I think there is a strong case to be made for leveraging session types in a microkernel, the biggest of which is to **prevent deadlocks at compile time**. I think it's important to introduce session types early into the design process, because it would be infeasible to add later to an established kernel.
Here are some resources for researching the topic:
- [Thesis: Practical Session Types in Rust](http://munksgaard.me/papers/munksgaard-laumann-thesis.pdf) [PDF]
- [Session Types for Rust (Short Version)](http://munksgaard.me/papers/laumann-munksgaard-larsen.pdf) [PDF]
- [Session Types:
Towards safe and fast reconfigurable programming](https://www.doc.ic.ac.uk/%7Ecn06/pub/2012/heart/paper.pdf) [PDF]
- [ICFP 2015 - Session Types for Rust](https://www.youtube.com/watch?v=0wDSjpx1Wz0) [Video]
- [Moonconf 2016 - Session Types for Me and You and Everyone We Know](https://www.youtube.com/watch?v=8GJ2AnCjCvU) [Video]
I hate to come to any project as an "ideas guy"; I'd much rather contribute with RFCs and PRs, but this has been bugging me for weeks. It will be at least a year before I will have time to contribute to Redox.
https://gitlab.redox-os.org/redox-os/redox/-/issues/699Program sandboxing approach2023-06-13T04:42:47ZJeremy SollerProgram sandboxing approach*Created by: DemiMarie*
**Related**: #634
This is a proposal for program sandboxing. It is related to #634.
Linux gives all programs, by default, the full privileges of the invoking user. This is **not** something that Redox should...*Created by: DemiMarie*
**Related**: #634
This is a proposal for program sandboxing. It is related to #634.
Linux gives all programs, by default, the full privileges of the invoking user. This is **not** something that Redox should replicate. A much better approach is the model used by app stores: programs are sandboxed, and cannot access files that don't belong to them without explicit user permission.
I propose to use capability-based security to achieve this. [Capsicum] is a good place to start, except that I propose to use capabilities for the entire OS.
Specifically:
1. Each program has a single application directory, per-user. This contains:
- A temporary directory. The program has read/write access to this directory, but it is emptied at system boot.
- A directory containing all (and only) the files that the program was installed with. For programs installed system-wide, this is a symbolic link to a system-wide directory. The program has read-only access to this directory, and can execute files that are marked as executable.
- A directory that contains data files that the program is working on. The program has read/write access to this directory, and it persists across system boots.
2. Programs can get access to other files by creating a dialog that allows the user to provide a capability to a user-selected file. Each user has a session manager, which handles this process (by passing a capability).
https://gitlab.redox-os.org/redox-os/orbital/-/issues/1README and LICENSE2018-06-15T00:17:45ZIan Douglas ScottREADME and LICENSENow that this has its own repo, it needs README and LICENSE files.
Now that this has its own repo, it needs README and LICENSE files.
https://gitlab.redox-os.org/redox-os/redox/-/issues/696Modern GUI (window manager, toolkit, etc)2023-06-13T04:42:45ZJeremy SollerModern GUI (window manager, toolkit, etc)*Created by: ids1024*
#569 discusses ways to produce a modern terminal interface (which is a great idea, by the way), but I haven't seen any discussion of a modern graphical interface.
The current interface provided by orbital is usabl...*Created by: ids1024*
#569 discusses ways to produce a modern terminal interface (which is a great idea, by the way), but I haven't seen any discussion of a modern graphical interface.
The current interface provided by orbital is usable, but primitive. It is just a typical Windows 95-like interface with a start menu equivalent at the bottom left, windows stacked on top of each other with an exit button at the top right, etc. This is fine for now, but ideally Redox would offer something better.
This issue has received more mainstream attention than a modern terminal, and software on other operating systems has done various things to modernize their user interfaces. Gnome 3, Unity, and Windows 8/10 stand out as examples.
Of course, there is not really any consensus on what the best interface would be, and the above mentioned examples all received a fair amount of criticism. I personally prefer tilling window managers over stacking window managers, but others will likely disagree.
One feature that seems quite nice to me is (some varient of) Unity's [HUD](https://wiki.ubuntu.com/Unity/HUD), but frankly I haven't used Unity enough to see if this is really so useful. I certainly think the general idea of replacing the old menu bar paradigm with something newer is a good idea at least.
I'm not suggesting that this should be a huge priority, but it is worth discussing anyway.
https://gitlab.redox-os.org/redox-os/redox/-/issues/692No such remote ref crates/ralloc2018-06-15T11:40:02ZJeremy SollerNo such remote ref crates/ralloc*Created by: et4te*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
curl -sf https://raw.githubusercontent.com/redox-os/redox/master/bootstrap.sh -o bootstrap.sh && bash -e bootstrap.sh
**Expecte...*Created by: et4te*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
curl -sf https://raw.githubusercontent.com/redox-os/redox/master/bootstrap.sh -o bootstrap.sh && bash -e bootstrap.sh
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
I expect this command to bootstrap redox.
**Actual behavior**: [describe the actual behavior, which is presented through the repro.].
error: no such remote ref 470d5810c5f4d0329f666438ee3bdf8d8e4b2913
Fetched in submodule path 'crates/ralloc', but it did not contain 470d5810c5f4d0329f666438ee3bdf8d8e4b2913. Direct fetching of that commit failed.
**Build information**: [output of `rustc -V`, `git rev-parse HEAD`, `qemu-i386 -version`, `uname -a`, etc.]
rustc 1.12.0-nightly (1225e122f 2016-07-30)
qemu-i386 version 2.6.0, Copyright (c) 2003-2008 Fabrice Bellard
Linux nixos 4.6.5 #1-NixOS SMP Wed Jul 27 15:42:34 UTC 2016 x86_64 GNU/Linux
**Blocking/related**: [issues or PRs blocking or being related to this issue.]
N/A
**Misc**: [optional: for other relevant information that should be known or cannot be described in the other fields.]
---
_If the above does not fit the nature of the issue feel free to modify it._