correct way to access gcc's own static libs?

[howarth at bromo dot msbb dot uc dot edu (Jack Howarth)]

    Is there a best approach to forcing gcc to check its own
arch specific gcc-lib directory for its static own static libs
during link time? In particular, if one has multiple versions
of gcc installed and want to link in static libs such as libstdc++.a
or libgcc.a without explicitly adding the path to their directory
with an -L. Specifically I am trying to avoid modifying Makefiles
to contain a specific gcc-lib location on a -L but make the process
more general such that a given version of gcc can find its own
static libs during linkage. Thanks in advance for any suggestions.
                Jack