Fix rules_fuzzing presubmit

[fmeum]

Work around bazelbuild/bazel#21592 as discovered in bazel-contrib/rules_fuzzing#242 (comment).

[github-actions]

fmeum has previously contributed to projects/bazel-rules-fuzzing-test-java. The previous PR was #9024
fmeum has previously contributed to projects/bazel-rules-fuzzing-test. The previous PR was #9024

[fmeum]

FYI @stefanbucur

[DavidKorczynski]

Do you know if this should should be propagated into the bazel builder script as well?

oss-fuzz/infra/base-images/base-builder/bazel_build_fuzz_tests

Lines 50 to 62 in 9d03475

	declare -r BAZEL_BUILD_FLAGS=(
	"-c" "opt"
	"--@rules_fuzzing//fuzzing:cc_engine=@rules_fuzzing_oss_fuzz//:oss_fuzz_engine" \
	"--@rules_fuzzing//fuzzing:java_engine=@rules_fuzzing_oss_fuzz//:oss_fuzz_java_engine" \
	"--@rules_fuzzing//fuzzing:cc_engine_instrumentation=oss-fuzz" \
	"--@rules_fuzzing//fuzzing:cc_engine_sanitizer=none" \
	"--cxxopt=-stdlib=libc++" \
	"--linkopt=-lc++" \
	"--verbose_failures" \
	"--spawn_strategy=standalone" \
	"--action_env=CC=${CC}" "--action_env=CXX=${CXX}" \
	${BAZEL_EXTRA_BUILD_FLAGS[*]}
	)

[fmeum]

@DavidKorczynski It shouldn't: Standalone builds are (slightly) faster and thus are better for large, real projects. The incompatibility is only with --features=layering_check, which rules_fuzzing specifies for itself to ensure that it is also compatible with end user projects using that feature - this isn't relevant for those.

[DavidKorczynski]

@DavidKorczynski It shouldn't: Standalone builds are (slightly) faster and thus are better for large, real projects. The incompatibility is only with --features=layering_check, which rules_fuzzing specifies for itself to ensure that it is also compatible with end user projects using that feature - this isn't relevant for those.

Thanks!