USE_GCC and unnesessary RUN_DENEDS on gcc port (Was: Print +REQUIRED_BY as tree?)

[b. f.]

> >  For example, x264 DEPENDS on gcc, (has USE_GCC=4.4+ in Makefile),
> >  but no x264 files are linked with libgcc_s.so or other libraries from
> >  gcc44. It seems, that we need separate USE_GCC_BUILD and USE_GCC_RUN,
> >  as with PERL or PYTHON.
>   Or, maybe automate this, as now port system warns user about
> "possible network servers" -- check all installed binaries and
> libraries for linkage with non-system-gcc libraries and add "run"
> dependency. But I'm not sure it is easy to do, as it should be done
> after installation, when, I afraid, adding RUN_DEPEND at this stage
> doesn't help, so this automatic should make all depends-related work
> (+REQUIRED_BY / +CONTENT) "by hands".

The type of dependency should be established by the maintainer of the
port that relies upon gcc, or by the user who sets USE_GCC in a custom
build.  It does not seem convenient or efficient to conduct a test of
the sort you describe, and there are cases -- such as  a script
calling a gcc binary, or a binary using dlopen to load a gcc library
-- that would complicate matters. There is already a proposal to add
some more flexibility to the USE_GCC construct:

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/155408

, an effort to create lighter runtime-only gcc ports, and some other
simplifications:

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=ports/160507

that will make changes like you describe less of a problem.

b.