redox-os issueshttps://gitlab.redox-os.org/groups/redox-os/-/issues2019-07-09T02:34:18Zhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1259Build error: could not compile `panic_abort` and `unwind`2019-07-09T02:34:18ZVitalyRBuild error: could not compile `panic_abort` and `unwind`## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
Could not compile `panic_abort` and `unwind` after running `make all`.
## Environment info
<!-- To understand where your issue originates, p...## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
Could not compile `panic_abort` and `unwind` after running `make all`.
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
Linux Rex 5.1.8-1-MANJARO #1 SMP PREEMPT Sun Jun 9 20:44:14 UTC 2019 x86_64 GNU/Linux
<!-- **Logs?** Posting a log can help developers find your particular issue more easily. Please wrap your code in code blocks using triple back-ticks ``` to increase readability. -->
```bash
make all
rm -f build/libkernel.a
rm -rf build/initfs
mkdir -p build/initfs
export PATH="/home/vitalyr/projects/rust/redox/prefix/x86_64-unknown-redox/relibc-install/bin:$PATH" && \
cargo run --manifest-path installer/Cargo.toml -- --cookbook=cookbook -c initfs.toml build/initfs/
Finished dev [unoptimized + debuginfo] target(s) in 0.11s
Running `installer/target/debug/redox_installer --cookbook=cookbook -c initfs.toml build/initfs/`
Install Config {
general: GeneralConfig {
prompt: false,
},
packages: {
"drivers": PackageConfig {
version: None,
git: None,
path: None,
},
"init": PackageConfig {
version: None,
git: None,
path: None,
},
"nulld": PackageConfig {
version: None,
git: None,
path: None,
},
"randd": PackageConfig {
version: None,
git: None,
path: None,
},
"redoxfs": PackageConfig {
version: None,
git: None,
path: None,
},
"zerod": PackageConfig {
version: None,
git: None,
path: None,
},
},
files: [
FileConfig {
path: "/etc/init.rc",
data: "export PATH /bin\nexport TMPDIR /tmp\nnulld\nzerod\nrandd\nvesad T T G\nstdio display:1\nps2d us\npcid /etc/pcid/initfs.toml\nredoxfs --uuid $REDOXFS_UUID file\ncd file:\nexport PATH file:/bin\nrun.d /etc/init.d\n",
symlink: false,
directory: false,
mode: None,
uid: None,
gid: None,
},
],
users: {},
} to build/initfs/
repo - building drivers
cook - drivers build
Updating crates.io index
Compiling cc v1.0.37
Compiling core v0.0.0 (/home/vitalyr/projects/rust/redox/rust/src/libcore)
Compiling libc v0.2.54 (/home/vitalyr/projects/rust/redox/cookbook/patches/liblibc)
Compiling unwind v0.0.0 (/home/vitalyr/projects/rust/redox/rust/src/libunwind)
Compiling compiler_builtins v0.1.16
Compiling std v0.0.0 (/home/vitalyr/projects/rust/redox/rust/src/libstd)
Compiling rustc-std-workspace-core v1.0.0 (/home/vitalyr/projects/rust/redox/rust/src/tools/rustc-std-workspace-core)
warning: the feature `cfg_target_vendor` has been stable since 1.33.0 and no longer requires an attribute to enable
--> /home/vitalyr/projects/rust/redox/cookbook/patches/liblibc/src/lib.rs:22:13
|
22 | feature(cfg_target_vendor, link_cfg, no_core)
| ^^^^^^^^^^^^^^^^^
|
= note: #[warn(stable_features)] on by default
warning: unused attribute
--> /home/vitalyr/projects/rust/redox/cookbook/patches/liblibc/src/lib.rs:27:1
|
27 | #![no_std]
| ^^^^^^^^^^
|
= note: #[warn(unused_attributes)] on by default
warning: crate-level attribute should be in the root module
--> /home/vitalyr/projects/rust/redox/cookbook/patches/liblibc/src/lib.rs:27:1
|
27 | #![no_std]
| ^^^^^^^^^^
Compiling alloc v0.0.0 (/home/vitalyr/projects/rust/redox/rust/src/liballoc)
Compiling rustc-demangle v0.1.15
Compiling panic_abort v0.0.0 (/home/vitalyr/projects/rust/redox/rust/src/libpanic_abort)
error[E0432]: unresolved imports `libc::c_int`, `libc::c_void`, `libc::uintptr_t`
--> /home/vitalyr/projects/rust/redox/rust/src/libunwind/libunwind.rs:8:12
|
8 | use libc::{c_int, c_void, uintptr_t};
| ^^^^^ ^^^^^^ ^^^^^^^^^ no `uintptr_t` in the root
| | |
| | no `c_void` in the root
| no `c_int` in the root
error[E0425]: cannot find function `abort` in this scope
--> /home/vitalyr/projects/rust/redox/rust/src/libpanic_abort/lib.rs:45:5
|
45 | abort();
| ^^^^^ not found in this scope
help: possible candidates are found in other modules, you can import them into scope
|
24 | use core::intrinsics::abort;
|
24 | use core::intrinsics::abort;
|
error[E0308]: mismatched types
--> /home/vitalyr/projects/rust/redox/rust/src/libpanic_abort/lib.rs:44:61
|
44 | pub unsafe extern fn __rust_start_panic(_payload: usize) -> u32 {
| ------------------ ^^^ expected u32, found ()
| |
| this function's body doesn't return
45 | abort();
| - help: consider removing this semicolon
|
= note: expected type `u32`
found type `()`
error: aborting due to 2 previous errors
Some errors occurred: E0308, E0425.
For more information about an error, try `rustc --explain E0308`.
error: Could not compile `panic_abort`.
warning: build failed, waiting for other jobs to finish...
error: aborting due to previous error
For more information about this error, try `rustc --explain E0432`.
error: Could not compile `unwind`.
warning: build failed, waiting for other jobs to finish...
error: build failed
error: `"cargo" "build" "--release" "--manifest-path" "/tmp/xargo.1B6OcA0jHrrW/Cargo.toml" "--target" "x86_64-unknown-redox" "-p" "std"` failed with exit code: Some(101)
note: run with `RUST_BACKTRACE=1` for a backtrace
./repo.sh failed.make: *** [mk/initfs.mk:5:build/initfs.tag] 错误 1
```
Related to:
- #1257https://gitlab.redox-os.org/redox-os/drivers/-/issues/26Unable to update mio-uds#2936ef822019-07-09T02:30:25ZNicolas PoirotUnable to update mio-uds#2936ef82I believe this is related to https://gitlab.redox-os.org/redox-os/mio-uds/issues/1
It seems to me reference to mio-uds 0.6.6 (Cargo.lock:335) was either from local repo or the mio-uds git has been rebased since then.
Anyway, I believe ...I believe this is related to https://gitlab.redox-os.org/redox-os/mio-uds/issues/1
It seems to me reference to mio-uds 0.6.6 (Cargo.lock:335) was either from local repo or the mio-uds git has been rebased since then.
Anyway, I believe the current referenced commit (mio-uds 0.6.6) should be 8ee05160
[0001-drivers-Fix-mio-uds-git-commit-reference.patch](/uploads/397010f9dd31220c21929776de13509d/0001-drivers-Fix-mio-uds-git-commit-reference.patch)https://gitlab.redox-os.org/redox-os/netstack/-/issues/31Unable to update mio-uds#2936ef822019-07-09T02:30:23ZNicolas PoirotUnable to update mio-uds#2936ef82I believe this is related to https://gitlab.redox-os.org/redox-os/mio-uds/issues/1
It seems to me reference to mio-uds 0.6.6 (Cargo.lock:274) was either from local repo or the mio-uds git has been rebased since then.
Anyway, I believe ...I believe this is related to https://gitlab.redox-os.org/redox-os/mio-uds/issues/1
It seems to me reference to mio-uds 0.6.6 (Cargo.lock:274) was either from local repo or the mio-uds git has been rebased since then.
Anyway, I believe the current referenced commit (mio-uds 0.6.6) should be 8ee05160
[0001-netstack-Fix-mio-uds-git-commit-reference.patch](/uploads/78ea5364a309c071964526f96ddd5fff/0001-netstack-Fix-mio-uds-git-commit-reference.patch)https://gitlab.redox-os.org/redox-os/redox/-/issues/1257Error while compiling on Ubuntu 18.04 and Pop!_Os2019-07-09T02:28:58ZArtúr KovácsError while compiling on Ubuntu 18.04 and Pop!_OsWhen building on an Ubuntu 18.04 and Pop!_Os 18.04 I get a `SIGABRT: process abort signal` while compiling `panic_abort`. (It is quite ironic)
Both happened on a fresh install on a virtual machine. I did update the operating system afte...When building on an Ubuntu 18.04 and Pop!_Os 18.04 I get a `SIGABRT: process abort signal` while compiling `panic_abort`. (It is quite ironic)
Both happened on a fresh install on a virtual machine. I did update the operating system after installation and I did install build-essential and rust but nothing else. After this I followed the [Getting Started](https://gitlab.redox-os.org/redox-os/redox/wikis/Getting-Started) guide.
Here is the last few lines of `make all`.
```
repo - fetching drivers
cook - drivers fetch
Cloning into 'source'...
remote: Enumerating objects: 2069, done.
remote: Counting objects: 100% (2069/2069), done.
remote: Compressing objects: 100% (1195/1195), done.
remote: Total 2069 (delta 901), reused 1967 (delta 854)
Receiving objects: 100% (2069/2069), 552.00 KiB | 789.00 KiB/s, done.
Resolving deltas: 100% (901/901), done.
Already up to date.
repo - preparing drivers
cook - drivers prepare
repo - building drivers
cook - drivers build
Updating crates.io index
Updating git repository `https://gitlab.redox-os.org/redox-os/liblibc.git`
Compiling cc v1.0.37
Compiling core v0.0.0 (/home/aert/Documents/software/redox/rust/src/libcore)
Compiling libc v0.2.54 (https://gitlab.redox-os.org/redox-os/liblibc.git?branch=redox#e26b93f2)
Compiling unwind v0.0.0 (/home/aert/Documents/software/redox/rust/src/libunwind)
Compiling compiler_builtins v0.1.15
Compiling std v0.0.0 (/home/aert/Documents/software/redox/rust/src/libstd)
Compiling rustc-std-workspace-core v1.0.0 (/home/aert/Documents/software/redox/rust/src/tools/rustc-std-workspace-core)
Compiling alloc v0.0.0 (/home/aert/Documents/software/redox/rust/src/liballoc)
Compiling panic_abort v0.0.0 (/home/aert/Documents/software/redox/rust/src/libpanic_abort)
rustc: /mnt/build/redox/rust/src/llvm-project/llvm/include/llvm/Support/Casting.h:255: typename llvm::cast_retty<X, Y*>::ret_type llvm::cast(Y*) [with X = llvm::Function; Y = llvm::Value; typename llvm::cast_retty<X, Y*>::ret_type = llvm::Function*]: Assertion `isa<X>(Val) && "cast<Ty>() argument of incompatible type!"' failed.
error: Could not compile `panic_abort`.
Caused by:
process didn't exit successfully: `rustc --edition=2018 --crate-name panic_abort /home/aert/Documents/software/redox/rust/src/libpanic_abort/lib.rs --color always --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C metadata=6bed04f146c879b6 -C extra-filename=-6bed04f146c879b6 --out-dir /tmp/xargo.DG5zg18MVUsQ/target/x86_64-unknown-redox/release/deps --target x86_64-unknown-redox -C linker=x86_64-unknown-redox-gcc -L dependency=/tmp/xargo.DG5zg18MVUsQ/target/x86_64-unknown-redox/release/deps -L dependency=/tmp/xargo.DG5zg18MVUsQ/target/release/deps --extern compiler_builtins=/tmp/xargo.DG5zg18MVUsQ/target/x86_64-unknown-redox/release/deps/libcompiler_builtins-2e6e30a7ed891a3f.rlib --extern core=/tmp/xargo.DG5zg18MVUsQ/target/x86_64-unknown-redox/release/deps/libcore-e8871951dc179544.rlib --extern libc=/tmp/xargo.DG5zg18MVUsQ/target/x86_64-unknown-redox/release/deps/liblibc-bef514465428e65c.rlib -L /home/aert/Documents/software/redox/prefix/x86_64-unknown-redox/relibc-install/x86_64-unknown-redox/lib --sysroot /home/aert/Documents/software/redox/cookbook/xargo -Z force-unstable-if-unmarked -L native=/tmp/xargo.DG5zg18MVUsQ/target/x86_64-unknown-redox/release/build/compiler_builtins-8ce39310e6c94e40/out` (signal: 6, SIGABRT: process abort signal)
warning: build failed, waiting for other jobs to finish...
error: build failed
error: `"cargo" "build" "--release" "--manifest-path" "/tmp/xargo.DG5zg18MVUsQ/Cargo.toml" "--target" "x86_64-unknown-redox" "-p" "std"` failed with exit code: Some(101)
note: run with `RUST_BACKTRACE=1` for a backtrace
./repo.sh failed.mk/initfs.mk:2: recipe for target 'build/initfs.tag' failed
make: *** [build/initfs.tag] Error 1
```https://gitlab.redox-os.org/redox-os/redox/-/issues/1253build fails on compiler_builtins2019-07-09T02:28:31ZNoah Palmerbuild fails on compiler_builtins<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report....<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report. You can also preview this report before submitting it. Feel free to modify/remove sections to fit the nature of your issue. -->
<!-- Please search to check that your issue has not been created already. By preventing duplicate issues, you can help keep the repository organized. If your current issue has already been created and is still unresolved, you can contribute by commenting there. -->
<!-- Replace the empty checkbox [ ] below with a checked one [x] if you have already searched for your issue. -->
- [x] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
When compiling from source the build fails after when building drivers.
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
Stock Fedora 30 installed today. followed manual build instructions in the readme
<!-- If you are using a pre-built release of Redox, please specify the release version below. -->
<!-- If you have built Redox OS yourself, please provide the following information: -->
- Operating system:
Fedora 30
- `uname -a`:
`Linux localhost.localdomain 5.0.9-301.fc30.x86_64 #1 SMP Tue Apr 23 23:57:35 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
`
- `rustc -V`:
`rustc 1.35.0-nightly (acd8dd6a5 2019-04-05)`
- `git rev-parse HEAD`:
`3e847cd43a9091b8e948a29ae9b863a61e1e86cd`
<!-- Depending on your issue, additional information about your environment (network config, package versions, dependencies, etc.) can also help. You can list that below. -->
## Steps to reproduce
<!-- If possible, please list the steps to reproduce ("trigger") your issue below. Being detailed definitely helps speed up bug fixes. -->
1. download source
2. bootstrap
3. rustup
4. cargo install xargo
5. git submodule
6. make all
## Behavior
<!-- It may seem obvious to know what to expect, but isolating the behavior from everything else simplifies the development process. Remember to provide a single issue in this report. You can use the References section below to link your issues together. -->
<!-- Describe the behavior you expect your steps should yield (i.e., correct behavior). -->
- **Expected behavior**:
Compilation succeeds
<!-- Describe the behavior you observed when running your steps (i.e., buggy behavior). -->
- **Actual behavior**:
compilation fails
<!-- **Logs?** Posting a log can help developers find your particular issue more easily. Please wrap your code in code blocks using triple back-ticks ``` to increase readability. -->
```
[killbox@localhost redox]$ make all
mkdir -p build
nasm -f bin -o build/bootloader -D ARCH_x86_64 -ibootloader/x86_64/ bootloader/x86_64/disk.asm
rm -f build/libkernel.a
rm -rf build/initfs
mkdir -p build/initfs
export PATH="/home/killbox/src/redox/prefix/x86_64-unknown-redox/relibc-install/bin:$PATH" && \
cargo run --manifest-path installer/Cargo.toml -- --cookbook=cookbook -c initfs.toml build/initfs/
Compiling typenum v1.10.0
Compiling proc-macro2 v0.4.27
Compiling cc v1.0.34
Compiling libc v0.2.51
Compiling matches v0.1.8
Compiling byteorder v1.3.1
Compiling unicode-xid v0.1.0
Compiling smallvec v0.6.9
Compiling version_check v0.1.5
Compiling cfg-if v0.1.7
Compiling untrusted v0.6.2
Compiling lazy_static v1.3.0
Compiling syn v0.15.30
Compiling winapi-build v0.1.1
Compiling httparse v1.3.3
Compiling quote v0.3.15
Compiling crc32fast v1.2.0
Compiling percent-encoding v1.0.1
Compiling autocfg v0.1.2
Compiling safemem v0.3.0
Compiling serde v1.0.90
Compiling pkg-config v0.3.14
Compiling unicode-xid v0.0.4
Compiling arrayvec v0.4.10
Compiling failure_derive v0.1.5
Compiling nodrop v0.1.13
Compiling byteorder v0.5.3
Compiling unicode-width v0.1.5
Compiling traitobject v0.1.0
Compiling typeable v0.1.2
Compiling language-tags v0.2.2
Compiling winapi v0.2.8
Compiling numtoa v0.1.0
Compiling adler32 v1.0.3
Compiling pkgutils v0.1.1 (https://gitlab.redox-os.org/redox-os/pkgutils.git#c1836b03)
Compiling bitflags v1.0.4
Compiling libc v0.2.46 (https://gitlab.redox-os.org/redox-os/liblibc.git?branch=redox#d4d3ef37)
Compiling fixedbitset v0.1.9
Compiling constant_time_eq v0.1.3
Compiling bytecount v0.3.2
Compiling ordermap v0.3.5
Compiling rustc-demangle v0.1.13
Compiling thread-scoped v1.0.2
Compiling bidir-map v0.6.0
Compiling serde v0.8.23
Compiling redox_syscall v0.1.53
Compiling ordermap v0.2.13
Compiling version-compare v0.0.4
Compiling scoped_threadpool v0.1.9
Compiling spin v0.4.10
Compiling arg_parser v0.1.0 (https://gitlab.redox-os.org/redox-os/arg-parser.git#75035318)
Compiling unicode-bidi v0.3.4
Compiling unicode-normalization v0.1.8
Compiling unicase v1.4.2
Compiling log v0.4.6
Compiling kernel32-sys v0.2.2
Compiling ring v0.13.5
Compiling backtrace-sys v0.1.28
Compiling backtrace v0.3.15
Compiling fuse v0.3.1
Compiling syn v0.10.8
Compiling textwrap v0.11.0
Compiling petgraph v0.4.13
Compiling log v0.3.9
Compiling toml v0.2.1
Compiling clap v2.33.0
Compiling time v0.1.42
Compiling rand v0.4.6
Compiling num_cpus v1.10.0
Compiling termion v1.5.1 (https://gitlab.redox-os.org/redox-os/termion#5992932c)
Compiling xattr v0.1.11
Compiling termion v1.5.1
Compiling idna v0.1.5
Compiling serde_codegen_internals v0.11.3
Compiling mime v0.2.6
Compiling base64 v0.9.3
Compiling libflate v0.1.21
Compiling generic-array v0.2.1
Compiling quote v0.6.11
Compiling blake2-rfc v0.2.18
Compiling rand v0.3.23
Compiling tar v0.4.13 (https://gitlab.redox-os.org/redox-os/tar-rs#b71c2202)
Compiling liner v0.4.5 (https://gitlab.redox-os.org/redox-os/liner#c3bc4640)
Compiling liner v0.1.5
Compiling toml v0.4.10
Compiling serde_codegen v0.8.23
Compiling url v1.7.2
Compiling pbr v1.0.0 (https://github.com/ids1024/pb?branch=duration#abe4d6e4)
Compiling static-buffer v0.2.0
Compiling argon2rs v0.2.5
Compiling uuid v0.5.1
Compiling sct v0.4.0
Compiling webpki v0.18.1
Compiling serde_derive v0.8.23
Compiling octavo-digest v0.1.2 (https://github.com/libOctavo/octavo.git#2eff2009)
Compiling hyper v0.10.15
Compiling redoxfs v0.3.2
Compiling webpki-roots v0.15.0
Compiling rustls v0.13.1
Compiling octavo v0.1.1 (https://github.com/libOctavo/octavo.git#2eff2009)
Compiling synstructure v0.10.1
Compiling serde_derive v1.0.90
Compiling hyper-rustls v0.6.2
Compiling failure v0.1.5
Compiling redox_installer v0.2.0 (/home/killbox/src/redox/installer)
Finished dev [unoptimized + debuginfo] target(s) in 1m 33s
Running `installer/target/debug/redox_installer --cookbook=cookbook -c initfs.toml build/initfs/`
Install Config {
general: GeneralConfig {
prompt: false,
},
packages: {
"drivers": PackageConfig {
version: None,
git: None,
path: None,
},
"init": PackageConfig {
version: None,
git: None,
path: None,
},
"redoxfs": PackageConfig {
version: None,
git: None,
path: None,
},
},
files: [
FileConfig {
path: "/etc/init.rc",
data: "export PATH /bin\nexport TMPDIR /tmp\nvesad T T G\nstdio display:1\nps2d us\npcid /etc/pcid/initfs.toml\nredoxfs --uuid $REDOXFS_UUID file\ncd file:\nexport PATH file:/bin\nrun.d /etc/init.d\n",
symlink: false,
directory: false,
mode: None,
uid: None,
gid: None,
},
],
users: {},
} to build/initfs/
repo - preparing drivers
cook - drivers prepare
repo - building drivers
cook - drivers build
Updating crates.io index
Updating git repository `https://gitlab.redox-os.org/redox-os/liblibc.git`
Compiling cc v1.0.37
Compiling core v0.0.0 (/home/killbox/src/redox/rust/src/libcore)
Compiling libc v0.2.54 (https://gitlab.redox-os.org/redox-os/liblibc.git?branch=redox#e26b93f2)
Compiling unwind v0.0.0 (/home/killbox/src/redox/rust/src/libunwind)
Compiling compiler_builtins v0.1.15
Compiling std v0.0.0 (/home/killbox/src/redox/rust/src/libstd)
error: failed to run custom build command for `compiler_builtins v0.1.15`
process didn't exit successfully: `/tmp/xargo.Kf2fyQ7nAx5D/target/release/build/compiler_builtins-f68f7081218dffb5/build-script-build` (exit code: 101)
--- stdout
cargo:rerun-if-changed=build.rs
cargo:compiler-rt=/home/killbox/.cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.15/compiler-rt
--- stderr
thread 'main' panicked at 'RUST_COMPILER_RT_ROOT is not set', /home/killbox/.cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.15/build.rs:420:21
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
warning: build failed, waiting for other jobs to finish...
error: build failed
error: `"cargo" "build" "--release" "--manifest-path" "/tmp/xargo.Kf2fyQ7nAx5D/Cargo.toml" "--target" "x86_64-unknown-redox" "-p" "std"` failed with exit code: Some(101)
note: run with `RUST_BACKTRACE=1` for a backtrace
./repo.sh failed.make: *** [mk/initfs.mk:5: build/initfs.tag] Error 1
```https://gitlab.redox-os.org/redox-os/redox/-/issues/1252Compile error in nghttp22019-07-09T02:25:48ZSam12121Compile error in nghttp2I am not able to compile nghttp2 please help me with this issue
checking for x86_64-unknown-redox-gcc... x86_64-unknown-redox-gcc
checking whether the C compiler works... no
configure: error: in `/root/Desktop/rp/redox/cookbook/recipe...I am not able to compile nghttp2 please help me with this issue
checking for x86_64-unknown-redox-gcc... x86_64-unknown-redox-gcc
checking whether the C compiler works... no
configure: error: in `/root/Desktop/rp/redox/cookbook/recipes/nghttp2/build':
configure: error: C compiler cannot create executables
See `config.log' for more details
./repo.sh failed.make: *** [mk/filesystem.mk:16: build/filesystem.bin] Error 1https://gitlab.redox-os.org/redox-os/redox/-/issues/1251ld: final link failed: bad value2019-07-09T02:24:41ZAariold: final link failed: bad value`make all` fails with:
```
/home/redox/redox/prefix/x86_64-unknown-redox/relibc-install/bin/../lib/gcc/x86_64-unknown-redox/8.2.0/../../../../x86_64-unknown-redox/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit s...`make all` fails with:
```
/home/redox/redox/prefix/x86_64-unknown-redox/relibc-install/bin/../lib/gcc/x86_64-unknown-redox/8.2.0/../../../../x86_64-unknown-redox/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
configure:5293: $? = 1
configure:5331: result: no
```
And then:
```
configure: error: in `/home/redox/redox/cookbook/recipes/xz/build':
configure: error: C compiler cannot create executables
See `config.log' for more details
./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/1254Build fails on amd ryzen threadripper2019-07-09T02:23:12ZnandhiniBuild fails on amd ryzen threadripper## Description
When compiling from source the build fails after when building drivers.
## Environment info
Stock Fedora 30 installed today. followed manual build instructions in the readme
* Operating system: Ubuntu 18.04
* `uname -a...## Description
When compiling from source the build fails after when building drivers.
## Environment info
Stock Fedora 30 installed today. followed manual build instructions in the readme
* Operating system: Ubuntu 18.04
* `uname -a`: `Linux Marvin 4.18.0-20-generic #21~18.04.1-Ubuntu SMP Wed May 8 08:43:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux`
* `rustc -V`: `rustc 1.32.0`
* `git rev-parse HEAD`: `3e847cd43a9091b8e948a29ae9b863a61e1e86cd`
## Steps to reproduce
1. download source
1. bootstrap
1. rustup
1. cargo install xargo
1. git submodule
1. make all
## Behavior
* **Expected behavior**: Compilation succeeds
* **Actual behavior**: compilation fails
Here's the error message when i try to compile redox with Ubuntu 18.04, on AMD RYZEN 1950x threadripper.
Any suggestions/clues as to what's causing the issue?
```
oracle@Marvin:~/Downloads/OSImages/redox/redox$ export RUST_BACKTRACE=1
oracle@Marvin:~/Downloads/OSImages/redox/redox$ make all
rm -f build/libkernel.a
rm -rf build/initfs
mkdir -p build/initfs
export PATH="/home/oracle/Downloads/OSImages/redox/redox/prefix/x86_64-unknown-redox/relibc-install/bin:$PATH" && \
cargo run --manifest-path installer/Cargo.toml -- --cookbook=cookbook -c initfs.toml build/initfs/
Finished dev [unoptimized + debuginfo] target(s) in 0.14s
Running `installer/target/debug/redox_installer --cookbook=cookbook -c initfs.toml build/initfs/`
Install Config {
general: GeneralConfig {
prompt: false,
},
packages: {
"drivers": PackageConfig {
version: None,
git: None,
path: None,
},
"init": PackageConfig {
version: None,
git: None,
path: None,
},
"redoxfs": PackageConfig {
version: None,
git: None,
path: None,
},
},
files: [
FileConfig {
path: "/etc/init.rc",
data: "export PATH /bin\nexport TMPDIR /tmp\nvesad T T G\nstdio display:1\nps2d us\npcid /etc/pcid/initfs.toml\nredoxfs --uuid $REDOXFS_UUID file\ncd file:\nexport PATH file:/bin\nrun.d /etc/init.d\n",
symlink: false,
directory: false,
mode: None,
uid: None,
gid: None,
},
],
users: {},
} to build/initfs/
repo - building drivers
cook - drivers build
Updating crates.io index
Updating git repository `https://gitlab.redox-os.org/redox-os/liblibc.git`
Compiling cc v1.0.37
Compiling libc v0.2.54 (https://gitlab.redox-os.org/redox-os/liblibc.git?branch=redox#e26b93f2)
Compiling core v0.0.0 (/home/oracle/Downloads/OSImages/redox/redox/rust/src/libcore)
Compiling unwind v0.0.0 (/home/oracle/Downloads/OSImages/redox/redox/rust/src/libunwind)
Compiling compiler_builtins v0.1.15
Compiling std v0.0.0 (/home/oracle/Downloads/OSImages/redox/redox/rust/src/libstd)
error: failed to run custom build command for `compiler_builtins v0.1.15`
process didn't exit successfully: `/tmp/xargo.JiKkDuRhTGBm/target/release/build/compiler_builtins-27084e789580f8a1/build-script-build` (exit code: 101)
--- stdout
cargo:rerun-if-changed=build.rs
cargo:compiler-rt=/home/oracle/.cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.15/compiler-rt
--- stderr
thread 'main' panicked at 'RUST_COMPILER_RT_ROOT is not set', /home/oracle/.cargo/registry/src/github.com-1ecc6299db9ec823/compiler_builtins-0.1.15/build.rs:420:21
stack backtrace:
0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
1: std::sys_common::backtrace::print
2: std::panicking::default_hook::{{closure}}
3: std::panicking::default_hook
4: std::panicking::rust_panic_with_hook
5: std::panicking::begin_panic
6: build_script_build::c::compile
7: build_script_build::main
8: std::rt::lang_start::{{closure}}
9: std::panicking::try::do_call
10: __rust_maybe_catch_panic
11: std::rt::lang_start_internal
12: main
13: __libc_start_main
14: _start
warning: build failed, waiting for other jobs to finish...
error: build failed
error: `"cargo" "build" "--release" "--manifest-path" "/tmp/xargo.JiKkDuRhTGBm/Cargo.toml" "--target" "x86_64-unknown-redox" "-p" "std"` failed with exit code: Some(101)
stack backtrace:
0: error_chain::make_backtrace::he04abbb2470a8fa6 (0x556bf65cc307)
1: <error_chain::State as core::default::Default>::default::h1c211366ae551399 (0x556bf65cc395)
2: <std::process::Command as xargo::extensions::CommandExt>::run::h394390101558ba1e (0x556bf6596d1f)
3: xargo::sysroot::build::hea71205886db3679 (0x556bf658d3c2)
4: xargo::sysroot::update::h52be25bdfe70e3c5 (0x556bf658f2f4)
5: xargo::main::he8bb031e05c872c4 (0x556bf6580d09)
6: std::rt::lang_start::{{closure}}::he855e745e556a7da (0x556bf657d2c2)
7: std::panicking::try::do_call::hbfef2ca7875c6284 (0x556bf65f4c92)
8: __rust_maybe_catch_panic (0x556bf66037c9)
9: std::rt::lang_start_internal::h1046fd32b686a071 (0x556bf65e17ea)
10: main (0x556bf65817f4)
11: __libc_start_main (0x7fe799bd9b96)
12: _start (0x556bf6572dd9)
13: <unknown> (0x0)
./repo.sh failed.mk/initfs.mk:2: recipe for target 'build/initfs.tag' failed
make: *** [build/initfs.tag] Error 1
```https://gitlab.redox-os.org/redox-os/relibc/-/issues/53unistd: Implement exec functions2019-07-09T02:20:44ZDan Robertsonunistd: Implement exec functionsThe [exec] functions in [unistd] are currently unimplemented.
- [x] `execl`
- [x] `execv`
- [x] `execle`
- [x] `execve`
- [ ] `execlp`
- [ ] `execvp`
Note that `execl`, `execle`, and `execlp` will require the use of a `va_list`. ...The [exec] functions in [unistd] are currently unimplemented.
- [x] `execl`
- [x] `execv`
- [x] `execle`
- [x] `execve`
- [ ] `execlp`
- [ ] `execvp`
Note that `execl`, `execle`, and `execlp` will require the use of a `va_list`. See `printf`, `open`, and `fcntl` for existing functions that use `va_list`.
[unistd]: http://pubs.opengroup.org/onlinepubs/009695399/basedefs/unistd.h.html
[exec]: http://pubs.opengroup.org/onlinepubs/009695399/functions/exec.htmlhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1255[Feature] [License] Switch to Public Domain2019-07-09T01:57:20Zhkj[Feature] [License] Switch to Public Domain**Feature**: Switch license to public domain for future code
Not sure if it is too late but I think this might be a great use case for public domain,
giving users complete and unrestricted access to the code.
Even if, segments must st...**Feature**: Switch license to public domain for future code
Not sure if it is too late but I think this might be a great use case for public domain,
giving users complete and unrestricted access to the code.
Even if, segments must still remain under the MIT license.
Licenses to look into:
* [Unlicense](https://www.wikipedia.org/wiki/Unlicense)
* [WTFPL](https://www.wikipedia.org/wiki/WTFPL)
* [CC0](https://www.wikipedia.org/wiki/Creative_Commons_license#Zero_/_public_domain)https://gitlab.redox-os.org/redox-os/relibc/-/issues/155CI script fails on Redox build2019-07-08T19:45:47ZPeter Limkilde SvendsenCI script fails on Redox buildRecent Redox CI builds of relibc fail with the following error:
```
[...]
$ export PATH="$PWD/prefix/bin:$PATH"
$ export RUSTUP_TOOLCHAIN="$PWD/prefix"
$ cargo install xargo
cargo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' no...Recent Redox CI builds of relibc fail with the following error:
```
[...]
$ export PATH="$PWD/prefix/bin:$PATH"
$ export RUSTUP_TOOLCHAIN="$PWD/prefix"
$ cargo install xargo
cargo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by cargo)
ERROR: Job failed: exit code 1
```
(The Linux build still succeeds.)https://gitlab.redox-os.org/redox-os/ion/-/issues/884Pipelines create new scopes2019-07-08T14:18:59ZAdminXVIIPipelines create new scopes```
echo bar | cat | cat | cat | read foo
echo $foo
```
Does not find the foo variable.```
echo bar | cat | cat | cat | read foo
echo $foo
```
Does not find the foo variable.https://gitlab.redox-os.org/redox-os/ion/-/issues/883Typos - Already fixed but I dunno your workflow2019-07-03T21:32:37ZIlmuTypos - Already fixed but I dunno your workflowI made these into separate commits and pushed them here:
https://gitlab.redox-os.org/ilmu/ion/commits/typos
Should I be making a pull request?
(I was just reading the Redox books and making notes of what I noticed was wrong. I figured ...I made these into separate commits and pushed them here:
https://gitlab.redox-os.org/ilmu/ion/commits/typos
Should I be making a pull request?
(I was just reading the Redox books and making notes of what I noticed was wrong. I figured I could fix it but I'm not sure where to proceed from here, fyi I'm using [this](https://doc.redox-os.org/book/contributing/best_practices/git.html) as my guide so far).https://gitlab.redox-os.org/redox-os/relibc/-/issues/153Static executables using TLS crash with SIGSEGV on Linux2019-07-01T03:32:39ZMateusz MikułaStatic executables using TLS crash with SIGSEGV on Linux```
$ cat tls.c
__thread int i;
int main() {
i = 42;
}
```
```
(gdb) r
Starting program: /home/mateusz/a.out
Program received signal SIGSEGV, Segmentation fault.
main () at tls.c:4
4 i = 42;
(gdb) bt
#0 main () at tls.c:4
(gdb) ...```
$ cat tls.c
__thread int i;
int main() {
i = 42;
}
```
```
(gdb) r
Starting program: /home/mateusz/a.out
Program received signal SIGSEGV, Segmentation fault.
main () at tls.c:4
4 i = 42;
(gdb) bt
#0 main () at tls.c:4
(gdb) disas
Dump of assembler code for function main:
0x0000000000233030 <+0>: push %rbp
0x0000000000233031 <+1>: mov %rsp,%rbp
0x0000000000233034 <+4>: xor %eax,%eax
=> 0x0000000000233036 <+6>: movl $0x2a,%fs:0xffffffffffffffe8
0x0000000000233042 <+18>: pop %rbp
0x0000000000233043 <+19>: retq
End of assembler dump.
```
Convenient way to test is available at https://gitlab.redox-os.org/mati865/relibc/commit/44d6c62374b184b0927f82df2a981b395e7391bf. Running `make test` will fail with:
```
# tls #
Segmentation fault (core dumped)
```Jeremy SollerJeremy Sollerhttps://gitlab.redox-os.org/redox-os/redox/-/issues/1261openssl does not build with perl v5.30.02019-06-29T18:46:22ZRoland Ruckerbaueropenssl does not build with perl v5.30.0<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report....<!-- Thank you for taking the time to submit an issue! By following these comments and filling out the sections below, you can help the developers get the necessary information to fix your issue. Please provide a single issue per report. You can also preview this report before submitting it. Feel free to modify/remove sections to fit the nature of your issue. -->
<!-- Please search to check that your issue has not been created already. By preventing duplicate issues, you can help keep the repository organized. If your current issue has already been created and is still unresolved, you can contribute by commenting there. -->
<!-- Replace the empty checkbox [ ] below with a checked one [x] if you have already searched for your issue. -->
- [X] I agree that I have searched opened and closed issues to prevent duplicates.
--------------------
## Description
<!-- Briefly summarize/describe the issue that you are experiencing below. -->
Redox does not build due to a build failure in openssl recipe.
Perl v5.30.0 removed the module File::Glob::glob, which is installed by default on archlinux.
## Environment info
<!-- To understand where your issue originates, please include some relevant information about your environment. -->
<!-- If you are using a pre-built release of Redox, please specify the release version below. -->
- Redox OS Release:
Current master
<!-- If you have built Redox OS yourself, please provide the following information: -->
- Operating system:
archlinux
- `uname -a`:
`Linux rruckerbauer-xps15-antergos 5.1.15-arch1-1-ARCH #1 SMP PREEMPT Tue Jun 25 04:49:39 UTC 2019 x86_64 GNU/Linux`
- `rustc -V`:
`rustc 1.35.0-nightly (acd8dd6a5 2019-04-05)`
- `git rev-parse HEAD`:
`c35d9e39f7020b0a28131e43c2f68dca82baa64f`
<!-- Depending on your issue, additional information about your environment (network config, package versions, dependencies, etc.) can also help. You can list that below. -->
- Replace me:
Perl version 5.30.0
## Steps to reproduce
<!-- If possible, please list the steps to reproduce ("trigger") your issue below. Being detailed definitely helps speed up bug fixes. -->
Just try to do a full clean build on archlinux.
<!-- **Solution?** Have a solution in mind? Propose your solution below. -->
- **Proposed solution**:
I made a PR with a fix: https://gitlab.redox-os.org/redox-os/openssl/merge_requests/1
<!-- **Screenshots?** Make it easier to get your point across with screenshots. You can drag & drop or paste your images below. -->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/ion/-/issues/882RFC: make command not found an unrecoverable error2019-06-28T14:15:27ZAdminXVIIRFC: make command not found an unrecoverable error# Proposition
Make command not found exit the script.
# Rationale
Scripts should make sure the executable exists on the target system. In case the script wrongly assumed the existence of a command, operations should not be proceeded, or...# Proposition
Make command not found exit the script.
# Rationale
Scripts should make sure the executable exists on the target system. In case the script wrongly assumed the existence of a command, operations should not be proceeded, or "magic" could happen.https://gitlab.redox-os.org/redox-os/handbook/-/issues/1Targeted audience2019-06-18T20:17:04ZJeremy SollerTargeted audience*Created by: k0pernicus*
Nice project :-)
Just a question: is the targeted audience of this book is geek users/common OS developers, or Rust developers?
Just to know if we have to talk about Rust code, give examples, etc...?
*Created by: k0pernicus*
Nice project :-)
Just a question: is the targeted audience of this book is geek users/common OS developers, or Rust developers?
Just to know if we have to talk about Rust code, give examples, etc...?
https://gitlab.redox-os.org/redox-os/drivers/-/issues/27Fix compilation issues2019-06-16T13:48:01ZNequ4tionFix compilation issuesThe following changes since commit 438c979cdf1128d8a00dbf53d2637f62cd6f0abe:
Fix compilation issues (2019-06-16 15:18:28 +0200)
are available in the Git repository at:
ssh://git@github.com/nequ4tion/drivers.git
for you to fetch ...The following changes since commit 438c979cdf1128d8a00dbf53d2637f62cd6f0abe:
Fix compilation issues (2019-06-16 15:18:28 +0200)
are available in the Git repository at:
ssh://git@github.com/nequ4tion/drivers.git
for you to fetch changes up to 438c979cdf1128d8a00dbf53d2637f62cd6f0abe:
Fix compilation issues (2019-06-16 15:18:28 +0200)
----------------------------------------------------------------https://gitlab.redox-os.org/redox-os/ion/-/issues/878Migrating command line argument parsing to "structopt" crate2019-06-15T15:54:36ZAlex TokarevMigrating command line argument parsing to "structopt" crateI have a proposal of changing command line argument parsing from naive implementation to "structopt" crate for the following advantages:
- Clear error messages when unknown option is used or a known one is used incorrectly. Currently an...I have a proposal of changing command line argument parsing from naive implementation to "structopt" crate for the following advantages:
- Clear error messages when unknown option is used or a known one is used incorrectly. Currently an unknown option is interpreted as a path to a script, which tries to get executed and fails because of file not found error.
- Ability to chain command line options after single '-' sign where it makes sense instead of always being separated by whitespace.
- Coherency of binary usage with Rust ecosystem - it is a popular crate for command line argument parsing.
Possible concerns with a new implementation:
- Additional dependency, which maintainers may prefer not to have.
- Possible increase in binary size. Needs to be measured if that is the case and for how much post factum.
If this change is considered desirable, I would like to be responsible for the implementation.