-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DevContainer: build failing on main #31856
Comments
Probably has to do with the recent cel upgrades #31456 (I am also encountering the same issues) |
Same here: envoy on main [$] via 🐹 v1.18.1 took 5s
➜ bazel build //contrib/exe:envoy-static
WARNING: The following configs were expanded more than once: [clang]. For repeatable flags, repeats are counted twice and may lead to unexpected behavior.
WARNING: The following configs were expanded more than once: [clang]. For repeatable flags, repeats are counted twice and may lead to unexpected behavior.
INFO: Analyzed target //contrib/exe:envoy-static (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /data/fabrizio/ongres/github.com/envoy/source/extensions/access_loggers/filters/cel/BUILD:11:19: Compiling source/extensions/access_loggers/filters/cel/cel.cc failed: (Exit 1): clang failed: error executing command (from target //source/extensions/access_loggers/filters/cel:cel_lib) /usr/lib/llvm-14/bin/clang -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -Wunused-but-set-parameter -Wno-free-nonheap-object -fcolor-diagnostics -fno-omit-frame-pointer ... (remaining 245 arguments skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
In file included from source/extensions/access_loggers/filters/cel/cel.cc:1:
In file included from ./source/extensions/access_loggers/filters/cel/cel.h:12:
In file included from ./source/extensions/filters/common/expr/evaluator.h:7:
In file included from ./source/extensions/filters/common/expr/context.h:11:
In file included from external/com_google_cel_cpp/eval/public/cel_value.h:37:
external/com_google_cel_cpp/base/memory.h:92:7: error: no matching function for call to 'operator delete'
::operator delete(static_cast<void*>(p), n * sizeof(T),
^~~~~~~~~~~~~~~~~
/usr/lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/new:155:6: note: candidate function not viable: no known conversion from 'unsigned long' to 'std::align_val_t' for 2nd argument
void operator delete(void*, std::align_val_t, const std::nothrow_t&)
^
/usr/lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/new:153:6: note: candidate function not viable: requires 2 arguments, but 3 were provided
void operator delete(void*, std::align_val_t)
^
/usr/lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/new:144:6: note: candidate function not viable: requires 2 arguments, but 3 were provided
void operator delete(void*, const std::nothrow_t&) _GLIBCXX_USE_NOEXCEPT
^
/usr/lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/new:180:13: note: candidate function not viable: requires 2 arguments, but 3 were provided
inline void operator delete (void*, void*) _GLIBCXX_USE_NOEXCEPT { }
^
/usr/lib/gcc/x86_64-linux-gnu/12/../../../../include/c++/12/new:130:6: note: candidate function not viable: requires 1 argument, but 3 were provided
void operator delete(void*) _GLIBCXX_USE_NOEXCEPT
^
1 error generated.
Target //contrib/exe:envoy-static failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 17.305s, Critical Path: 16.61s
INFO: 25 processes: 17 internal, 8 linux-sandbox.
FAILED: Build did NOT complete successfully |
i dont use devcontainer so cant speak to that directly - but given this passes our CI im wondering what can be different iirc you need to rebuild the container after updates - could this be the issue ? |
k - i think this is a different (if related) issue can you either use the official build container or ensure that your host has exactly the same versions of compilers and related utilities |
in both cases im assuming that you have something in user.bazelrc that points to gcc as i think the default would build on llvm @fabriziomello one thing i can spot that is different is the c++ version which i believe is tied to the gcc version when testing a recent gcc update we were only able to build with gcc/g++11 so my guess is that this is related to the issues you are seeing cc @kyessenov it would be good if these issues could be resolved upstream |
I think this is related to using clang with libstdc++ headers. Can you try adding |
Fixes envoyproxy#31856 Signed-off-by: Fredy Wijaya <[email protected]>
@Pawan-Bishnoi could you test if #31872 resolves the issue with the dev container ? |
either wait for google/cel-cpp#558 or enable |
Fixes #31856 Signed-off-by: Fredy Wijaya <[email protected]>
yes, it does. |
Fixes envoyproxy#31856 Signed-off-by: Fredy Wijaya <[email protected]> Signed-off-by: Ryan Northey <[email protected]>
Fixes #31856 Signed-off-by: Fredy Wijaya <[email protected]> Signed-off-by: Ryan Northey <[email protected]>
Title: Envoy build fails when using devcontainer mode on main branch
Description:
The text was updated successfully, but these errors were encountered: