Convert binary wrapper to a symlink wrapper.v2.0

Before the change:
   /usr/bin/gcc and friends were a copy of /usr/$(libexecdir)/misc/gcc-config
After the change:
   /usr/bin/gcc is a symlink to a real compiler binary. Examples:
       /usr/${CTARGET}/gcc-bin/${GCC_VER}/gcc (native)
       /usr/${CHOST}/${CTARGET}/gcc-bin/${GCC_VER}/gcc (cross)

gcc-config is a binary wrapper that does (or did) a few things:

- [removed in 2011] injects additional CFLAGS_${ABI}

  Removed in commit 7ac40f3eb8434961f70485247d883f5b3009dcf2
  "Stop auto appending CFLAGS_<abi> from the env."

- traverses PATH for real compiler binary and reexecutes it.

- reads /etc/env.d/05gcc-${CTARGET} as a fallback if PATH is empty.

Today binary wrapper does only PATH resolution and re-execution.

This change has a few minor benefits:

- PATH will not contain explicit /usr/${CHOST}/${CTARGET}/gcc-bin/${GCC_VER}
  entry. This will make PATH shorter for those who have mavy cross-compilers
  installed.

- compiler switch will not require sourcing '. /etc/profile' as changes are
  applied as soon an symlink is switched.

- ccache will see gcc binary changes directly and react accordingly.
  Previously in default configuration ccache cache depended on state of
  /usr/$(libexecdir)/misc/gcc-config

  See bug #640958 where ccache did not notice USE=-pie -> USE=pie switch.

- Reasoning about PATH ordering is straightforward: all available binaries
  (as symlinks) are in /usr/bin.

  See bug #255695 where PATH ordering changed and bug #626606 where
  people get confused on what is in /usr/bin/gcc binary.

Bug: https://bugs.gentoo.org/626606
Bug: https://bugs.gentoo.org/255695
Bug: https://bugs.gentoo.org/640958
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>

1 files changed, 0 insertions, 3 deletions

diff --git a/.gitignore b/.gitignore
index 23938ed..b79124b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,6 +1,4 @@
-a.out
 *~
-*.o
 
 *.diff
 *.patch
@@ -10,4 +8,3 @@ a.out
 /gcc-config-*.tar.*
 
 /.gcc-config
-/wrapper