You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
Trying to build this on Arch, which is using the relatively newer Linux 5.12 kernel and ran into the issue. Basically when I do the cargo build step, with or without --release it fails near the end with the following error message:
error: failed to run custom build command for `ingraind v1.0.0 (/foniod)`
Caused by:
process didn't exit successfully: `/foniod/target/release/build/ingraind-63413aae32fcee9d/build-script-build` (signal: 11, SIGSEGV: invalid memory reference)
As it is probably a difficult to reproduce environment, I went ahead and used docker to create the following Dockerfile that reproduces the error using a more vanilla Ubuntu image:
FROM ubuntu:latest
RUN apt update
RUN apt dist-upgrade -y
RUN echo "12\n5" | apt install -y tzdata
RUN apt install -y capnproto llvm-11 clang-11 curl linux-headers-generic git gcc g++ binutils pkg-config openssl libssl-dev libz-dev
RUN curl https://sh.rustup.rs -sSf > rustup.sh
RUN chmod 0755 rustup.sh
RUN ./rustup.sh -y
RUN git clone https://github.com/foniod/foniod.git
WORKDIR foniod
RUN . ~/.cargo/env && KERNEL_VERSION=5.4.0-74-generic cargo build --release
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Trying to build this on Arch, which is using the relatively newer Linux 5.12 kernel and ran into the issue. Basically when I do the
cargo build
step, with or without--release
it fails near the end with the following error message:As it is probably a difficult to reproduce environment, I went ahead and used
docker
to create the followingDockerfile
that reproduces the error using a more vanilla Ubuntu image:The text was updated successfully, but these errors were encountered: