[libgpiod] Show build issues with container #68
Conversation
|
Earlier it used to fail while trying to build libgpiod, now it is not even able to fetch it. Not sure why. Are we restricting the dependencies to be from known paths only? |
vireshk
force-pushed
the
gpio/container-issues
branch
4 times, most recently
from
b092b68
to
ea9f43e
Compare
vireshk
force-pushed
the
gpio/container-issues
branch
from
18862f2
to
957525e
Compare
We are not restricting dependencies in any way. Not sure why this is happening. |
It was failing ealier because of edition 2021 in libgpiod, after making that 2018, it is working fine. Only the build issues are left. |
|
FYI @vireshk the container is not automatically published. Once it gets published, we need to also update rust-vmm-ci to use the new container version. |
|
@vireshk I published rust-vmm/dev:v14, can you update the container version in rust-vmm-ci? |
vireshk
force-pushed
the
gpio/container-issues
branch
from
d5f1835
to
c765e9f
Compare
Sure. |
The containers used for builds currently don't have necessary tools to compile buildgen stuff, which compiles few C files and create bindings. This pull request is about highlighting those issues here. We need these tools in the containers: libclang-dev clang musl-tools. Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
vireshk
force-pushed
the
gpio/container-issues
branch
from
c765e9f
to
a2672bc
Compare
Hi @andreeaflorescu
The containers used for builds currently don't have necessary tools to
compile buildgen stuff, which compiles few C files and create bindings.
This pull request is about highlighting those issues here.
We need these tools in the containers: libclang-dev clang musl-tools.
We also need to configure the container to pass the include path for the Linux libraries,
else we get more errors.
THIS PULL REQUEST SHOULDN'T BE MERGED.