for it from compiler.mk.
Move the variable of the same name used by compiler/gcc.mk and
the gcc* buildlink3 files into private namespace (_USE_GCC_SHLIB).
Update gcc3-c++ to 3.3.3nb1
Update gcc3-c to 3.3.3nb2
Update gcc3-f77 to 3.3.3nb1
Update gcc3-java to 3.3.3nb1
Update gcc3-objc to 3.3.3nb1
Update gcc3 to 3.3.3nb1
gcc arm: fix GCC _P_R_ target/14302
Apply gcc fix for gcc PR target/14302 to fix ARM compiler
issues triggered by at least glib, glib2, and pkgconfig.
2004-02-26 Richard Earnshaw <rearnsha@arm.com>
Daniel Jacobowitz <drow@mvista.com>
PR target/14302
* arm.h (ARM_GO_IF_LEGITIMATE_ADDRESS): Don't check the mode
size for minipool references.
there exists a 'cc', leading to buildlink creating a 'cc' wrapper pointing
to the original 'cc', which then won't work with the gcc flags, while the
'gcc' wrapper does work (since packages simply call 'cc' (or 'gcc') and
rely on buildlink having prepended the path to the right wrapper).
support. This makes it easier to "bootstrap" the installation of a
pkgsrc compiler without a lot of additional indirect build dependencies on
gettext, libiconv, libtool, etc.
by moving the inclusion of buildlink3.mk files outside of the protected
region. This bug would be seen by users that have set PREFER_PKGSRC
or PREFER_NATIVE to non-default values.
BUILDLINK_PACKAGES should be ordered so that for any package in the
list, that package doesn't depend on any packages to the left of it
in the list. This ordering property is used to check for builtin
packages in the correct order. The problem was that including a
buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed
from BUILDLINK_PACKAGES and appended to the end. However, since the
inclusion of any other buildlink3.mk files within that buildlink3.mk
was in a region that was protected against multiple inclusion, those
dependencies weren't also moved to the end of BUILDLINK_PACKAGES.
"linux"-style one. This matches our pkgsrc libtool behaviour so that we
can get a consistent numbering across different platforms so that we don't
have to fiddle with the PLIST. This fixes PR 22556 and PR 23684.
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.)
