With GCC 4.0 and 4.2 fading further into the distance, and GCC 14 now available in Tigerbrew itself, we'll want to be able to use the Tigerbrew-provided GCCs when building binary packages. Since C and C++ software will be dynamically linked against that compiler's C/C++ stdlibs, we'll want to ensure that the appropriate compiler is installed when pouring the bottle. Right now, we don't have any support for this.
One solution here would be for Tigerbrew to run the linkage checker after pouring a bottle. If it finds a broken dynamic link against a library coming from a GCC formula, it can go ahead and fetch the compiler's bottle too. This would save us having to make GCC itself a runtime dependency, and make the compiler we use OS-dependent - which feels right.
refs #1188.