Open jainvikas8 opened 3 months ago
Could you provide more details: how do you build parsec, what version, do you use Yocto, what poky version, what meta-security version, do you have any your own bbapend for parsec recipes, etc.
This was done on a Debian (Ubuntu 22 LTS) on a docker container.
FROM ubuntu:22.04
RUN apt update && apt-get -y upgrade
RUN apt install -y autoconf-archive libcmocka0 libcmocka-dev procps
RUN apt install -y iproute2 build-essential git pkg-config gcc libtool automake libssl-dev uthash-dev doxygen libjson-c-dev
RUN apt install -y --fix-missing wget python3 cmake clang
RUN apt install -y libini-config-dev curl libgcc1
RUN apt install -y python3-distutils libclang-11-dev protobuf-compiler python3-pip
RUN apt install -y libgcrypt20-dev uuid-dev
RUN apt install -y git gcc nano openssl
ENV RUSTUP_HOME="/opt/rust"
ENV CARGO_HOME="/opt/rust"
RUN curl https://sh.rustup.rs -sSf | sh -s -- --default-toolchain=1.78.0 -y --no-modify-path
ENV PATH="/root/.cargo/bin:/opt/rust/bin:${PATH}"
RUN git clone https://github.com/parallaxsecond/parsec.git --branch main \
&& cd parsec \
&& cargo build --features "mbed-crypto-provider,direct-authenticator"
This issue is also seen on a host machine.
Upgraded to latest 1.8.0 and it gives different issue
https://git.yoctoproject.org/poky/commit/?id=30bf8dcc25602ccc7e119ef2b9e766b33fcc35cb meta-poky, upgrades to use 1.80.0 version and we see the similar issue on Yocto builds when we use 1.4.1 release
See this issue when building parsec, it requires rustc 1.78 version, the newest release 1.8 also gives issues.