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
First of all: Thanks for the great work of enabling an hermetic gcc toolchain in Bazel! It helped us already a lot for our understanding.
Description
At the moment we're trying to integrate your toolchain (with a bumped gcc version) in our build but I am already failing to compile a third party project (which we're bundling/shipping/linking against).
The configure_make step is failing during configure with a lot of errors, where some of them seem to be toolchain related. e.g.:
configure:3724: /home/timotheus/.cache/bazel/_bazel_timotheus/17bdf0994d16870d211e03bc3a9d26dd/sandbox/linux-sandbox/21/execroot/_main/external/gcc_toolchain_x86_64/bin/gcc -c -Dredacted="redacted" conftest.c >&5
conftest.c:10:10: fatal error: stdio.h: No such file or directory
10 | #include <stdio.h>
| ^~~~~~~~~
compilation terminated.
This looks to me as configure is expecting gcc to find the system include paths by its own.
But those paths are explicitly registered (as I assume the pre-compiled/relocated gcc won't be able to do that on his own)
First of all: Thanks for the great work of enabling an hermetic gcc toolchain in Bazel! It helped us already a lot for our understanding.
Description
At the moment we're trying to integrate your toolchain (with a bumped
gcc
version) in our build but I am already failing to compile a third party project (which we're bundling/shipping/linking against).The
configure_make
step is failing duringconfigure
with a lot of errors, where some of them seem to be toolchain related. e.g.:This looks to me as
configure
is expectinggcc
to find the system include paths by its own.But those paths are explicitly registered (as I assume the pre-compiled/relocated
gcc
won't be able to do that on his own)This may all be an issue of the external
rrdtool
project but you guys may have more insights / tips regarding that?Repro
The issue should be fully reproducible with: Checkmk@3be3a14
The text was updated successfully, but these errors were encountered: