by bsd.compiler.mk. Note that in the buildlink3.mk files, the dependency
is always added regardless of the BUILDLINK_DEPTH. This is because these
buildlink3.mk files may be included by bsd.prefs.mk, which is often
included other buildlink3.mk files, and we need to ensure that regardless
of the depth, we are using the correct compiler.
PKGNAME if we are installing to an alternative location so that the
pkg system doesn't complain about conflicts.
Now it is possible to install a gcc3 tree to some location where
it can be used to bootstrap another instance of itself...
Apply http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10955
* unroll.c (unroll_loop): Fix off-by-one bug.
Fixes build issue with xdm and -O3
Suggested by fredb
-${prefix} is the same like ${GCC_PREFIX}, but the former is already there
are not for the host compiler, but for the stage-1 "xgcc", which is
not subject to buildlink's redirection.
(The gcc libs are needed because ld is redirected.)
-USE_NEW_TEXINFO, saves some patches
-symlink libiberty.a into build tree instead of buildlink/lib,
saves some patches
-put common make rules into Makefile.common (for all) and
buildaddon.mk (for all but the base "c" pkg)
