redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2018-06-15T11:40:01Zhttps://gitlab.redox-os.org/redox-os/redox/-/issues/983can't build redux using docker2018-06-15T11:40:01ZJeremy Sollercan't build redux using docker*Created by: jinnzest*
**Reproduction**:
Following instructions described here https://github.com/redox-os/redox/blob/master/docker/README.md
**Expected behavior**: running redux in qemu
**Actual behavior**:
Step 3 of the inst...*Created by: jinnzest*
**Reproduction**:
Following instructions described here https://github.com/redox-os/redox/blob/master/docker/README.md
**Expected behavior**: running redux in qemu
**Actual behavior**:
Step 3 of the instruction is completed successfully.
But step 4 is failed:
`docker run --cap-add MKNOD --cap-add SYS_ADMIN --device /dev/fuse -e LOCAL_USER_ID="$(id -u)" -v "$(pwd):/src" --rm redox make all`
returned:
`Starting with UID : 502 `
`CARGO_HOME is /cargo`
`RUSTUP_HOME is /rustup`
`make: *** No rule to make target 'all'. Stop.`
**Redox release**: last master commit
**Misc**: I tried to run it on macos sierra
https://gitlab.redox-os.org/redox-os/redox/-/issues/984error: Could not compile `untrusted'2018-06-15T11:40:01ZJeremy Sollererror: Could not compile `untrusted'*Created by: gnfrazier*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
Ubuntu 17.10
$ curl -sf https://raw.githubusercontent.com/redox-os/redox/master/bootstrap.sh -o bootstrap.sh && bash -e boo...*Created by: gnfrazier*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
Ubuntu 17.10
$ curl -sf https://raw.githubusercontent.com/redox-os/redox/master/bootstrap.sh -o bootstrap.sh && bash -e bootstrap.sh
Completes
cd redox
make all
begins to compile
fails on untrusted
error: Could not compile `untrusted'
Terminal output: https://gist.github.com/gnfrazier/e377e2bfec85b83cc49c495a1cdf654d
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
Completed compile
**Actual behavior**: [describe the actual behavior, which is presented through the repro.].
Failed complile
https://gist.github.com/gnfrazier/e377e2bfec85b83cc49c495a1cdf654d
**Build information**: [only when using a self build version: output of `rustc -V`, `git rev-parse HEAD` `qemu-i386 -version`, `uname -a`, etc.]
rustc 1.16.0
cargo-0.17.0 (built 2017-03-24)
**Redox release**: [only when using a prebuild version: redox version]
Command not found
**Blocking/related**: [issues or PRs blocking or being related to this issue.]
**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/976Build fails, alloc::vec unresolved import2018-06-15T11:40:01ZJeremy SollerBuild fails, alloc::vec unresolved import*Created by: gjsman*
**Expected behavior**:
Expect the thing to build, obviously.
**Actual behavior**:
Despite making sure to put all dependencies in (and use nightly), I get:
```
Compiling orbclient v0.3.8
Compiling bgad v0....*Created by: gjsman*
**Expected behavior**:
Expect the thing to build, obviously.
**Actual behavior**:
Despite making sure to put all dependencies in (and use nightly), I get:
```
Compiling orbclient v0.3.8
Compiling bgad v0.1.0 (file:///home/gabriel/redox/cookbook/recipes/drivers/build/bgad)
error[E0432]: unresolved import `alloc::Vec`
--> /home/gabriel/.cargo/registry/src/github.com-1ecc6299db9ec823/orbclient-0.3.8/src/graphicspath.rs:1:5
|
1 | use alloc::Vec;
| ^^^^^^^^^^ no `Vec` in the root
error: aborting due to previous error(s)
error: Could not compile `orbclient`.
warning: build failed, waiting for other jobs to finish...
error: build failed
./repo.sh failed.mk/initfs.mk:2: recipe for target 'build/initfs.tag' failed
make: *** [build/initfs.tag] Error 1
```
**Build information**:
rustc 1.20.0-nightly (ab5bec255 2017-06-22)
Linux ubuntu 4.10.0-24-generic #28-Ubuntu SMP Wed Jun 14 08:14:34 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
**Redox release**: master
------
_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/975dockerfile misses README how to use it2018-06-15T11:40:01ZJeremy Sollerdockerfile misses README how to use it*Created by: jinnzest*
Dockerfile and entrypoint.sh is added but there is no README file how to use it.
@batonius could You add README?*Created by: jinnzest*
Dockerfile and entrypoint.sh is added but there is no README file how to use it.
@batonius could You add README?https://gitlab.redox-os.org/redox-os/redox/-/issues/1000It seem like can not Startup Arch2023-06-13T04:42:50ZJeremy SollerIt seem like can not Startup Arch*Created by: 3442853561*
I waited about ten minutes
Just stay in "Startup Arch"*Created by: 3442853561*
I waited about ten minutes
Just stay in "Startup Arch"https://gitlab.redox-os.org/redox-os/redox/-/issues/982user: pkg failed to unpack message2018-06-15T11:40:01ZJeremy Solleruser: pkg failed to unpack message*Created by: aspera-non-spernit*
**Reproduction**:
# pkg install <PACKAGE>
**Actual behavior**:
Redox lets user download pkg to /tmp but message doesn't quiet tell that user isn't allowed to install.
* Requesting...*Created by: aspera-non-spernit*
**Reproduction**:
# pkg install <PACKAGE>
**Actual behavior**:
Redox lets user download pkg to /tmp but message doesn't quiet tell that user isn't allowed to install.
* Requesting https://static.redox-os.org/pkg/x86_64-unknown-redox/games.sig
124 B / 124 B [===========================================] 100.00 % 5.38 KB/s
* Already downloaded games
pkg: install: games: failed: failed to unpack `/pkg/games.toml`
**Expected Behaviour**
A message that user cannot install packages, before download of package. Refer to fetchhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1001gawk does not build with the newest commit2018-06-15T11:40:01ZJeremy Sollergawk does not build with the newest commit*Created by: Csega*
**Reproduction**: use the latest bootstrap.sh, then cd redox, then make all
**Expected behavior**: build redox correctly
**Actual behavior**: gawk does not build
**Build information**: `rustc -V`: rustc 1.20...*Created by: Csega*
**Reproduction**: use the latest bootstrap.sh, then cd redox, then make all
**Expected behavior**: build redox correctly
**Actual behavior**: gawk does not build
**Build information**: `rustc -V`: rustc 1.20.0-nightly (ae98ebfcb 2017-07-20)
`git rev-parse HEAD`: c8d7b6d773a70170c312da7d21f2a506b578305b
`qemu-i386 -version`: qemu-i386 version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.14), Copyright (c) 2003-2008 Fabrice Bellard
`uname -a`: Linux csega-eos-loki 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
**Misc**: the exact output:
make[3]: Entering directory '/home/csega/redox/cookbook/recipes/gawk/build'
x86_64-elf-redox-gcc -g -O2 -DNDEBUG -o gawk array.o awkgram.o builtin.o cint_array.o command.o debug.o eval.o ext.o field.o floatcomp.o gawkapi.o gawkmisc.o int_array.o io.o main.o mpfr.o msg.o node.o profile.o re.o replace.o str_array.o symbol.o version.o support/libsupport.a -lm
main.o: In function `load_procinfo':
/home/csega/redox/cookbook/recipes/gawk/build/main.c:1003: undefined reference to `getppid'
collect2: error: ld returned 1 exit status
Makefile:648: recipe for target 'gawk' failed
make[3]: *** [gawk] Error 1
make[3]: Leaving directory '/home/csega/redox/cookbook/recipes/gawk/build'
Makefile:727: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/csega/redox/cookbook/recipes/gawk/build'
Makefile:552: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/csega/redox/cookbook/recipes/gawk/build'
./repo.sh failed.mk/filesystem.mk:2: recipe for target 'build/filesystem.bin' failed
make: *** [build/filesystem.bin] Error 1
------https://gitlab.redox-os.org/redox-os/redox/-/issues/979error: failed switching to "user:user": unable to find user user: no matching...2023-06-13T04:42:50ZJeremy Sollererror: failed switching to "user:user": unable to find user user: no matching entries in passwd file*Created by: aspera-non-spernit*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
Using the docker way of the redox installation as introduced in week 23, by invoking the following command:
do...*Created by: aspera-non-spernit*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
Using the docker way of the redox installation as introduced in week 23, by invoking the following command:
docker run --cap-add MKNOD --cap-add SYS_ADMIN --device /dev/fuse -e LOCAL_USER_ID='id -u' -v 'pwd':/src --rm redox make all
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
positive docker results
**Actual behavior**: [describe the actual behavior, which is presented through the repro.].
Starting with UID : id -u
CARGO_HOME is /cargo
RUSTUP_HOME is /rustup
useradd: invalid user ID 'id'
chown: invalid user: 'user:user'
chown: invalid user: 'user:user'
error: failed switching to "user:user": unable to find user user: no matching entries in passwd file
**Redox release**: [only when using a prebuild version: redox version]
25 June 17 srcs latest on github
**Misc**: [optional: for other relevant information that should be known or cannot be described in the other fields.]
I tried also to change id to user or to a local (host) user name.
I changed the ` ` to ' ' in the command because the ones given in the wiki lead to another error:
docker: Error response from daemon: create `pwd`: "`pwd`" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path.
See 'docker run --help'.
------
_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/999It still can't run in VMware(Windows 10)2023-06-13T04:42:50ZJeremy SollerIt still can't run in VMware(Windows 10)*Created by: 3442853561*
like https://github.com/redox-os/redox/issues/821*Created by: 3442853561*
like https://github.com/redox-os/redox/issues/821https://gitlab.redox-os.org/redox-os/redox/-/issues/977Is `x86_64-elf-redox-gcc` not installed?2018-06-15T11:40:01ZJeremy SollerIs `x86_64-elf-redox-gcc` not installed?*Created by: Olivered*
**Reproduction**:
make all
**Expected behavior**:
build succeeds
**Actual behavior**:
running: "x86_64-elf-redox-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-ffreestanding" "-m64" "-fno-bui...*Created by: Olivered*
**Reproduction**:
make all
**Expected behavior**:
build succeeds
**Actual behavior**:
running: "x86_64-elf-redox-gcc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-ffreestanding" "-m64" "-fno-builtin" "-fvisibility=hidden" "-fomit-frame-pointer" "-ffreestanding" "-DVISIBILITY_HIDDEN" "-o" "/var/folders/w2/4xzz78pd24sb2mmssx4_d3tw0000gp/T/xargo.xTq7FE6PUvQ7/target/x86_64-unknown-redox/release/build/compiler_builtins-5e8895d281cea536/out/compiler-rt/../compiler-rt/lib/builtins/absvdi2.o" "-c" "../compiler-rt/lib/builtins/absvdi2.c"
failed to execute command: No such file or directory (os error 2)
Is `x86_64-elf-redox-gcc` not installed?
**Build information**:
rustc 1.20.0-nightly (229d0d326 2017-06-23)
git rev 12f419e6d26a3444a5b0de3fa9566e305003372e
Darwin Macbook-Pro 16.6.0 Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 x86_64 i386 MacBookPro12,1 Darwin
xcode, redox-os/x86_64-elf packages installed
https://gitlab.redox-os.org/redox-os/redox/-/issues/994grub4dos & isolinux compatibility?2023-06-13T04:42:50ZJeremy Sollergrub4dos & isolinux compatibility?*Created by: leeoniya*
hi,
i decided to try booting `redox_0.3.0.iso` from my multi-boot drive. the typical bootable iso entry in `menu.lst` looks like this: https://gist.github.com/poppen/3161814
```
title redox_0.3.0.iso
find --set-...*Created by: leeoniya*
hi,
i decided to try booting `redox_0.3.0.iso` from my multi-boot drive. the typical bootable iso entry in `menu.lst` looks like this: https://gist.github.com/poppen/3161814
```
title redox_0.3.0.iso
find --set-root /img/redox_0.3.0.iso
map /img/redox_0.3.0.iso (0xff) || map --mem /img/redox_0.3.0.iso (0xff)
map --hook
chainloader (0xff)
```
redox appears to fail image decompression with "Not enough memory to decompress image". this grab is from QEMU, but i get the same result on my Lenovo T440s.
![redox-grub4dos-qemu](https://user-images.githubusercontent.com/43234/28174575-769e9688-67b7-11e7-8bba-3ccbf55533c5.png)
thanks!https://gitlab.redox-os.org/redox-os/redox/-/issues/974Build fails on openSUSE 42.22023-06-13T04:42:50ZJeremy SollerBuild fails on openSUSE 42.2*Created by: cbcoutinho*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
I followed the manual installation instructions for a first time install. After cloning the repo recursively and overwritin...*Created by: cbcoutinho*
**Reproduction**: [describe how you are able to reproduce ("trigger") this bug/issue.]
I followed the manual installation instructions for a first time install. After cloning the repo recursively and overwriting the rust toolchain with nightly, I executed `./bootstrap.sh -d`. The log of that output can be see [in this gist](https://gist.github.com/cbcoutinho/5d1225b0054cb169a857c2bc561a3257)
At a first glance, it looks like this script is going into a number of functions that I don't think it has any business doing - why is it detecting a Debian/Ubuntu system?
NOTE: I think you need to install xargo before running make - that should probably be reflected in the README
After bootstrapping, I executed `make` - [this gist is the output](https://gist.github.com/cbcoutinho/b68b63095b95df7a0e4d68c65e5007f3)
Make fails with the following error:
```
failed to execute command: No such file or directory (os error 2)
Is `x86_64-elf-redox-gcc` not installed?
```
This looks similar to #40, in that an OSX build failed due to a missing dependency. Is my system thinking it's OSX and behaving as such? There is no package in the openSUSE universe that I am aware of named `x86_64-elf-redox-gcc`
**Expected behavior**: [describe the behavior you would expect the repro to yield.]
Not failing
**Actual behavior**: [describe the actual behavior, which is presented through the repro.].
Build is failing
**Build information**: [only when using a self build version: output of `rustc -V`, `git rev-parse HEAD` `qemu-i386 -version`, `uname -a`, etc.]
```
user:[~/Software/redox] (master)$ rustc -V
rustc 1.20.0-nightly (445077963 2017-06-20)
user:[~/Software/redox] (master)$ git rev-parse HEAD
cc42cab9e2210a5c8167207a9d7c52373a992880
user:[~/Software/redox] (master)$ qemu-system-i386 -version
QEMU emulator version 2.6.2 (openSUSE Leap 42.2), Copyright (c) 2003-2008 Fabrice Bellard
user:[~/Software/redox] (master)$ qemu-system-x86_64 -version
QEMU emulator version 2.6.2 (openSUSE Leap 42.2), Copyright (c) 2003-2008 Fabrice Bellard
user:[~/Software/redox] (master)$ uname -a
Linux hostname 4.4.70-18.9-default #1 SMP Wed May 31 09:09:25 UTC 2017 (c1231a7) x86_64 x86_64 x86_64 GNU/Linux
```
**Redox release**: [only when using a prebuild version: redox version]
First time build, N/A
**Blocking/related**: [issues or PRs blocking or being related to this issue.]
I think related to #40 , possibly also related to #970
**Misc**: [optional: for other relevant information that should be known or cannot be described in the other fields.]https://gitlab.redox-os.org/redox-os/redox/-/issues/990Panic on killing processes2023-06-13T04:42:50ZJeremy SollerPanic on killing processes*Created by: xTibor*
**Reproduction**:
I could only reproduce it with the recently added `rustual-boy` emulator.
1. Login into Orbital
2. Open a Terminal window
3. Run `rustual-boy-cli /path/some_rom_anything.vb`.
4. Open an another Te...*Created by: xTibor*
**Reproduction**:
I could only reproduce it with the recently added `rustual-boy` emulator.
1. Login into Orbital
2. Open a Terminal window
3. Run `rustual-boy-cli /path/some_rom_anything.vb`.
4. Open an another Terminal window
5. Run `ps`. Find the two process ids of the emulator.
6. Run `kill 9 <first_process_id>`
7. Run `kill 9 <second_process_id>`
8. Panic
**Actual behavior**:
The kernel panics with the following message:
```
Signal handler: 9, 0
PANIC: unmap_inner(10000000000): p3 not found
FILE: src/paging/mapper.rs
LINE: 185
TRACE: FFFFFF40001C7D80
FFFFFF40001C7D80: FFFFFF0000151986
FFFFFF00001517A0+01E6
FFFFFF40001C7E30: FFFFFF00001A73E4
FFFFFF00001A7360+0084
FFFFFF40001C7EA0: FFFFFF0000151484
FFFFFF0000151210+0274
FFFFFF40001C7F20: FFFFFF0000179DB5
FFFFFF0000179780+0635
FFFFFF40001C8060: FFFFFF000017D856
FFFFFF000017D060+07F6
FFFFFF40001C81E0: FFFFFF000014CB73
FFFFFF000014C8B0+02C3
FFFFFF40001C8280: FFFFFF000014945C
FFFFFF0000149440+001C
FFFFFF40001C8390: FFFFFF0000169257
FFFFFF0000169010+0247
FFFFFF40001C8480: FFFFFF0000168FD4
FFFFFF0000168E10+01C4
FFFFFF40001C8520: FFFFFF000016A78A
FFFFFF000016A6D0+00BA
FFFFFF40001C8570: FFFFFF0000126087
FFFFFF0000125F00+0187
FFFFFF40001C85A0: FFFFFF00001739F3
FFFFFF0000173690+0363
FFFFFF40001C8650: FFFFFF000017F67A
FFFFFF000017EE70+080A
FFFFFF40001C89C0: FFFFFF000014FC8A
FFFFFF000014FC60+002A
FFFFFF40001C89E0: FFFFFF000014FC4D
FFFFFF000014FC30+001D
00000180000FC950: GUARD PAGE
HALT
```
**Build information**:
`rustc -V`: rustc 1.20.0-nightly (720c596ec 2017-07-08)
`git rev-parse HEAD`: 31671ae3d95b0aa88bc3793b9961578b28ca4b6bhttps://gitlab.redox-os.org/redox-os/redox/-/issues/970Build Fails (Solus Linux for missing x86_64-elf-redox-gcc)2023-06-13T04:42:50ZJeremy SollerBuild Fails (Solus Linux for missing x86_64-elf-redox-gcc)*Created by: BearzRobotics*
**Reproduction**: Follow build instructions for the bootstrap script to build Redox
**Expected behavior**: Redox is build
**Actual behavior**: Make Fails [Pastbin link](https://pastebin.com/CJLfpvq5)
...*Created by: BearzRobotics*
**Reproduction**: Follow build instructions for the bootstrap script to build Redox
**Expected behavior**: Redox is build
**Actual behavior**: Make Fails [Pastbin link](https://pastebin.com/CJLfpvq5)
**Build information**: [`rustc -V`, `git rev-parse HEAD` `qemu-i386 -version`, `uname -a`, etc.]
rustc 1.19.0-nightly (554c685b0 2017-06-14)
497b6fde96aa7d730565a8926c6fea171b6fb80e
qemu-i386 version 2.9.0
Linux plex 4.9.30-29.lts #1 SMP Sat May 27 10:29:10 UTC 2017 x86_64 GNU/Linux
**Blocking/related**:
failed to execute command: No such file or directory (os error 2)
Is `x86_64-elf-redox-gcc` not installed?
https://gitlab.redox-os.org/redox-os/redox/-/issues/991qemu does not work with the newest revision2018-06-15T11:40:00ZJeremy Sollerqemu does not work with the newest revision*Created by: Csega*
Hi guys,
I got the following problem with the last few version (including the latest master revision).
**Reproduction**: make a clean installation using the newest bootstrap.sh, then cd redox, then make all, th...*Created by: Csega*
Hi guys,
I got the following problem with the last few version (including the latest master revision).
**Reproduction**: make a clean installation using the newest bootstrap.sh, then cd redox, then make all, then make qemu kvm=no
**Expected behavior**: Successful build and a working system.
**Actual behavior**: the build is successful, however, the make qemu kvm=no has the following output:
make qemu kvm=no
SDL_VIDEO_X11_DGAMOUSE=0 qemu-system-x86_64 -serial mon:stdio -d cpu_reset -d guest_errors -smp 4 -m 2048 -machine q35 -device ich9-intel-hda -device hda-duplex -net nic,model=e1000 -net user -net dump,file=build/network.pcap -device nec-usb-xhci,id=xhci -device usb-tablet,bus=xhci.0 \
-drive file=build/harddrive.bin,format=raw \
-drive file=build/extra.qcow2
warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
warning: TCG doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
qemu-system-x86_64: cannot set up guest memory 'pc.ram': Cannot allocate memory
mk/qemu.mk:38: recipe for target 'qemu' failed
make: *** [qemu] Error 1
**Build information**: `rustc -V`: rustc 1.20.0-nightly (d84693b93 2017-07-09)
`git rev-parse HEAD`: ca4159b1eca9173d13c5c626ac2ec0b6087bfd7f
`qemu-i386 -version`: qemu-i386 version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.14), Copyright (c) 2003-2008 Fabrice Bellard
`uname -a`: Linux csega-eos-loki 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
What could be the problem?
Cheers,
Csegahttps://gitlab.redox-os.org/redox-os/redox/-/issues/967Bootstrap doesn't install xargo2018-06-15T11:40:00ZJeremy SollerBootstrap doesn't install xargo*Created by: jmikkola*
**Reproduction**:
- Clone the repo
- Init submodules
- Run the bootstrap script
- Run `make all`
**Expected behavior**: it compiles
**Actual behavior**:
```
./cook.sh: line 131: xargo: command no...*Created by: jmikkola*
**Reproduction**:
- Clone the repo
- Init submodules
- Run the bootstrap script
- Run `make all`
**Expected behavior**: it compiles
**Actual behavior**:
```
./cook.sh: line 131: xargo: command not found
./repo.sh failed.mk/initfs.mk:2: recipe for target 'build/initfs.tag' failed
make: *** [build/initfs.tag] Error 1
```
**Build information**:
- rustc 1.19.0-nightly (fe7227f6c 2017-06-16)
- HEAD = 56504fc8b179eeed0ae6001e01e9f923ae28526e
- uname -a: `Linux firefly 4.4.0-78-generic #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux`
I fixed this by running
cargo install xargohttps://gitlab.redox-os.org/redox-os/redox/-/issues/963OSX: undefined reference to `c_cpuid': make {virtualbox,qemu}2023-06-13T04:42:49ZJeremy SollerOSX: undefined reference to `c_cpuid': make {virtualbox,qemu}*Created by: adarqui*
**Reproduction**: bootstrap.sh; make qemu (or make virtualbox)
**Expected behavior**: Don't error.
**Actual behavior**: I receive the following error:
```
redox$ make virtualbox
x86_64-elf-ld --gc-sectio...*Created by: adarqui*
**Reproduction**: bootstrap.sh; make qemu (or make virtualbox)
**Expected behavior**: Don't error.
**Actual behavior**: I receive the following error:
```
redox$ make virtualbox
x86_64-elf-ld --gc-sections -z max-page-size=0x1000 -T kernel/linkers/x86_64.ld -o build/kernel build/libkernel.a
build/libkernel.a(raw_cpuid-9cf6b6e4636721a8.0.o): In function `raw_cpuid::CpuId::new::h7dfb0a7093d5537d':
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId3new17h7dfb0a7093d5537dE+0x35): undefined reference to `c_cpuid'
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId3new17h7dfb0a7093d5537dE+0x35): relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `c_cpuid'
build/libkernel.a(raw_cpuid-9cf6b6e4636721a8.0.o): In function `raw_cpuid::CpuId::get_vendor_info::hd4ca29f2f98219c9':
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId15get_vendor_info17hd4ca29f2f98219c9E+0x39): undefined reference to `c_cpuid'
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId15get_vendor_info17hd4ca29f2f98219c9E+0x39): relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `c_cpuid'
build/libkernel.a(raw_cpuid-9cf6b6e4636721a8.0.o): In function `raw_cpuid::CpuId::get_feature_info::h7b77103b518d3f0e':
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId16get_feature_info17h7b77103b518d3f0eE+0x3e): undefined reference to `c_cpuid'
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId16get_feature_info17h7b77103b518d3f0eE+0x3e): relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `c_cpuid'
build/libkernel.a(raw_cpuid-9cf6b6e4636721a8.0.o): In function `raw_cpuid::CpuId::get_extended_feature_info::hf22f499da193f407':
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId25get_extended_feature_info17hf22f499da193f407E+0x3e): undefined reference to `c_cpuid'
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId25get_extended_feature_info17hf22f499da193f407E+0x3e): relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `c_cpuid'
build/libkernel.a(raw_cpuid-9cf6b6e4636721a8.0.o): In function `raw_cpuid::CpuId::get_processor_frequency_info::hdbe7789140580e13':
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId28get_processor_frequency_info17hdbe7789140580e13E+0x3e): undefined reference to `c_cpuid'
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId28get_processor_frequency_info17hdbe7789140580e13E+0x3e): relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `c_cpuid'
build/libkernel.a(raw_cpuid-9cf6b6e4636721a8.0.o):raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId26get_extended_function_info17h808fd7c958fb4fc5E+0x4a): more undefined references to `c_cpuid' follow
build/libkernel.a(raw_cpuid-9cf6b6e4636721a8.0.o): In function `raw_cpuid::CpuId::get_extended_function_info::h808fd7c958fb4fc5':
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId26get_extended_function_info17h808fd7c958fb4fc5E+0x4a): relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `c_cpuid'
raw_cpuid.cgu-0.rs:(.text._ZN9raw_cpuid5CpuId26get_extended_function_info17h808fd7c958fb4fc5E+0x192): relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `c_cpuid'
make: *** [build/kernel] Error 1
```
**Build information**:
```
redox$ rustc -V
rustc 1.19.0-nightly (4bf5c99af 2017-06-10)
current git master as of: f5677cc76fbd7b9d96dc22b78fc9a25b2cac2e07
redox$ uname -a
Darwin redox 16.6.0 Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 x86_64
```
**More**
```
redox$ grep -r c_cpuid .
Binary file ./build/libkernel.a matches
Binary file ./kernel/target/x86_64-unknown-none/release/build/raw-cpuid-810e159428d76215/out/libcpuid.a matches
Binary file ./kernel/target/x86_64-unknown-none/release/build/raw-cpuid-810e159428d76215/out/src/cpuid.o matches
Binary file ./kernel/target/x86_64-unknown-none/release/deps/libraw_cpuid-9cf6b6e4636721a8.rlib matches
```
Any idea? Thanks!https://gitlab.redox-os.org/redox-os/redox/-/issues/966Rethink the network interfaces (network scheme, drivers)2023-06-13T04:42:49ZJeremy SollerRethink the network interfaces (network scheme, drivers)*Created by: real-unoriginal*
Currently (it seems) that redox has two nic drivers, each of which when ran mounts the **one** nic directly to the *network* scheme. The additional networking daemons that use the *network* scheme directly ...*Created by: real-unoriginal*
Currently (it seems) that redox has two nic drivers, each of which when ran mounts the **one** nic directly to the *network* scheme. The additional networking daemons that use the *network* scheme directly or indirectly also depend on the fact that there is only one interface (so there is no routing table for example).
This design makes using more than 1 physical nic at the same time impossible. Also since many networking protocols (eg: PPP(oE), WIREGUARD) that require setting up virtual network interfaces (that than will be used to route appropriate IP packets through), currently they cannot be implemented.
In order to fix this we would need to do something similar to the *disk* schemes, that mounts multiple disks as *disk:/1*. *disk:/2* etc. The following questions arise:
* How to name physical interfaces (traditional eth{x}, something like systemd does: "enp0s3" or the same as *disk* names disks /1 /2 /3 ...) ?
* Where do virtual interfaces are connected to? Do we mount them under the network scheme too or do we want to make a separete scheme for phisical nics, and virtual ones?
* Who maintains the routing table (ipd?)? When creating a new virtual interface that has an ip address and can reach a set of ip adresses how do we signal this to the daemon that maintains the routing table?https://gitlab.redox-os.org/redox-os/redox/-/issues/987"Privileged Ports Cause Climate Change"2023-06-13T04:42:50ZJeremy Soller"Privileged Ports Cause Climate Change"*Created by: leeoniya*
i'm too stupid and unfamiliar with Redox's architecture to know what insight might be gleaned from this article, but it's an interesting read nevertheless:
http://adamierymenko.com/privileged-ports-are-causing-...*Created by: leeoniya*
i'm too stupid and unfamiliar with Redox's architecture to know what insight might be gleaned from this article, but it's an interesting read nevertheless:
http://adamierymenko.com/privileged-ports-are-causing-climate-change/
HN thread: https://news.ycombinator.com/item?id=14712576https://gitlab.redox-os.org/redox-os/redox/-/issues/958MIT Licence doesn't suit OS Development2018-06-15T11:40:00ZJeremy SollerMIT Licence doesn't suit OS Development*Created by: anon8000*
Here the Redox Founder says he doesn't care about Licence:
https://youtu.be/eH5JgMlNE8o?t=2681
While he does make other nonsense comments about Free Software Projects and why he thinks they are in a bad shape an...*Created by: anon8000*
Here the Redox Founder says he doesn't care about Licence:
https://youtu.be/eH5JgMlNE8o?t=2681
While he does make other nonsense comments about Free Software Projects and why he thinks they are in a bad shape and such, he obviously has no Idea or is "paid" to not care.
That's a very bad move. Nobody in their right mind will join a OS Project after all what People have seen happening in with Free Software and everything surrounding it, unless they are to young to know or are misinformed.
I suggest changing to GPL3. It's litterally a Licence made for OS Development.
GPL Version 3 Background to Adoption: https://www.fsf.org/news/gpl3.html
A Quick Guide: http://www.gnu.org/licenses/quick-guide-gplv3.en.html
Here are some Videos about Free Software you have to watch:
https://www.youtube.com/watch?v=b3uX5XwdN_8
https://www.youtube.com/watch?v=POexV1k62_Y
That said, even if your one and only purpose for this Project is to advertise the Rust Language it's still a very bad move with the MIT Licence. Those who know how things go won't ever invest development time into this because they'd be just wasting it. I myself would start learning the Rust Language if Redox had a GPL3 complete Licence. At the moment it's basically the only interessting Project that uses that Language but it just doesn't make sense learning it for something that's broken because of licensing.