Added GCC toolchain patch to fix the linker scripts for libc.so and libm.so.

[kekxv]

➜ /workspaces/rules_cc/examples/rule_based_toolchain (main) $ bazel build --config=gcc :quick_test
INFO: Analyzed target //:quick_test (2 packages loaded, 5541 targets configured).
INFO: From Linking quick_test:
/home/codespace/.cache/bazel/_bazel_codespace/3580036953c5d36d0e83906c15f52e80/external/+_repo_rules+gcc-linux-x86_64/bin/../lib/gcc/x86_64-buildroot-linux-gnu/13.3.0/../../../../x86_64-buildroot-linux-gnu/bin/ld: warning: asm_answer.o: missing .note.GNU-stack section implies executable stack
/home/codespace/.cache/bazel/_bazel_codespace/3580036953c5d36d0e83906c15f52e80/external/+_repo_rules+gcc-linux-x86_64/bin/../lib/gcc/x86_64-buildroot-linux-gnu/13.3.0/../../../../x86_64-buildroot-linux-gnu/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
INFO: Found 1 target...
Target //:quick_test up-to-date:
  bazel-bin/quick_test
INFO: Elapsed time: 38.822s, Critical Path: 6.98s
INFO: 25 processes: 8 action cache hit, 3 internal, 22 linux-sandbox.
INFO: Build completed successfully, 25 total actions

[trybka]

Is there an issue associated with this? Given that this is the example rules-based toolchain--is there something we can fix to not require a set of patches?

cc: @armandomontanez

[kekxv]

Is there an issue associated with this? Given that this is the example rules-based toolchain--is there something we can fix to not require a set of patches?

This is a long-standing issue. My goal here is to offer a feasible solution for users looking for a current implementation.