Age | Commit message (Collapse) | Author | Files | Lines |
|
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).
|
|
the resulting shared library names don't necessarily match the NetBSD
names. Instead of hardcoding the shared library names in the PLISTs,
only list the libtool archives in the PLISTs and dynamically determine
the shared library names at post-install time and insert them into
the PLIST. This fixes PLIST errors on non-NetBSD platforms.
All of the magic is done in pkgsrc/lang/gcc3/language.mk. This should
probably be generalized into something that could be used by all
packages that use libtool.
|
|
|
|
bugfixes only afaict, no new features, no new files
|
|
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.
|
|
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
|
|
a single patch directory from gcc3/patches/.
Also Move gcc3-c/{Makefile.common,language.mk} into gcc3/.
|
|
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.
|
|
functional change.
|
|
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that
we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
|
|
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
|
|
|
|
references to the buildlink work directories.
|
|
|
|
behaviour in gcc3-c/Makefile.common.
|
|
if it's being included by bsd.prefs.mk, so we can safely move the
BUILDLINK_DEPENDS line to its usual location.
|
|
be added automatically to library and run-time library search paths.
|
|
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.
|
|
|
|
gcc3 pkg. Until we have a sane solution, delete it for now.
Addresses PR pkg/22773 by John R. Shannon.
|
|
|
|
COMMENT tweaks.
|
|
|
|
gcc3 to 3.3nb5
gcc3-c to 3.3nb1
gcc3-c++ to 3.3nb1
In gcc3.mk set CPP to '.../cpp -gcc' rather than '.../cpp'
Ensure __GNUC__ and similar are defined.
|
|
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...
|
|
language backends.
|
|
-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)
|
|
about GCC_PREFIX.
XXX why is GCC_PREFIX ${PREFIX}/gcc3 ?
|
|
Needs some cleanup and integration; eventually lang/gcc3 can turn into
a meta-pkg.
|