Self-defined C/C++ toolchain with "no_legacy_features" does not accept unknown features #22992
Unanswered
andreas-0815-qwertz
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am creating a toolchain for Gcc 3.4.5; this Gcc version does not support parameter files for the linker (
linker_param_file
feature). Therefore, I have defined the feature "no_legacy_features" in my toolchain. Compiler and archiver features are supported by issuing the related flags in the command lines, but the linker features are unfortunately not. I am sure I am missing something but could you please tell me what?I have attached a minimal working example using my toolchain with
/usr/bin/gcc
. On a linux system you should be able to unpack the tarball and runbazel build --noenable_bzlmod --platforms=//bazel_utils/platforms:onepc_platform -s //:toolchain_test
to see, what I mean. The surprising thing for me is that the featuredefault_compile_flags
does not seem to work.My bazel configuration is:
$ bazel version
Bazelisk version: v1.17.0
Build label: 7.2.1
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Tue Jun 25 15:53:05 2024 (1719330785)
Build timestamp: 1719330785
Build timestamp as int: 1719330785
toolchain_test.tar.gz
Beta Was this translation helpful? Give feedback.
All reactions