summaryrefslogtreecommitdiff
path: root/lang/gcc3-objc
AgeCommit message (Collapse)AuthorFilesLines
2006-04-12Aligned the last line of the buildlink3.mk files with the first line, sorillig1-2/+2
that they look nicer.
2006-04-06Over 1200 files touched but no revisions bumped :)reed1-3/+3
RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-02-05Recursive revision bump / recommended bump for gettext ABI change.joerg2-2/+4
2005-06-16Create directories before installing files into them.jlam1-1/+2
2004-11-22Now that no package uses USE_GCC_SHLIB any longer, remove supportwiz1-2/+2
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).
2004-09-08GCC generates and uses its own libtool to build shared libraries, andjlam1-5/+1
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.
2004-07-06Unused.wiz1-35/+0
2004-07-02update to 3.3.4drochner1-2/+1
bugfixes only afaict, no new features, no new files
2004-05-22Update gcc3-ada to 3.3.3nb1abs1-1/+2
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.
2004-05-17Garbage collect BUILDLINK_PKGBASE.<pkg> from buildlink3: it is not anymoreseb1-2/+1
used since revision 1.139 of mk/buildlink3/bsd.buildlink3.mk.
2004-04-10Make all gcc3-* packages use a single distinfo file from gcc3/distinfo andseb3-24/+2
a single patch directory from gcc3/patches/. Also Move gcc3-c/{Makefile.common,language.mk} into gcc3/.
2004-03-18Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properlyjlam1-5/+4
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.
2004-03-18Rename the internal package variable referred to by buildlink[23]. Nojlam2-28/+28
functional change.
2004-03-16If the ${PKGBASE} of a package doesn't match the token passed tojlam1-1/+2
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
2004-03-05Reorder location and setting of BUILDLINK_PACKAGES to match templatejlam1-7/+9
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
2004-03-02update to gcc-3.3.3drochner2-5/+4
2004-02-13Bump the PKGREVISION after fixing up the installed *.la files to removejlam1-1/+4
references to the buildlink work directories.
2004-02-13Check if a variable is defined before checking its value.jlam1-2/+4
2004-02-13Fix the check for the GCC3_INSTALLTO_SUBPREFIX so that it matches thejlam1-2/+2
behaviour in gcc3-c/Makefile.common.
2004-02-05bsd.compiler.mk no longer adds dependencies or includes buildlink*.mk filesjlam1-1/+5
if it's being included by bsd.prefs.mk, so we can safely move the BUILDLINK_DEPENDS line to its usual location.
2004-02-05List the correct directories for finding GCC libraries so that they willjlam1-1/+3
be added automatically to library and run-time library search paths.
2004-02-01bl3ify the gcc3-* packages. Also provide buildlink[23].mk files for usejlam4-22/+70
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.
2003-12-03update to gcc-3.3.2 (bugfix release)drochner1-3/+3
2003-08-11update to 3.3.1drochner3-22/+5
2003-08-08include major version number in COMMENT for distinction, some minorgrant1-2/+2
COMMENT tweaks.
2003-07-16elaborate the INSTALLTO_SUBPREFIX thing a bit more: modify thedrochner1-2/+2
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...
2003-07-09The file affected by the bugfix (unroll.c) is potentially used by alldrochner2-1/+18
language backends.
2003-07-08some cleanup:drochner5-133/+25
-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)
2003-07-06set GCC_VERSION for use in GCC_ARCHDIR. remove a superfluous commentgrant1-2/+3
about GCC_PREFIX. XXX why is GCC_PREFIX ${PREFIX}/gcc3 ?
2003-07-06Split the gcc3 pkg into per-language pieces.drochner6-0/+182
Needs some cleanup and integration; eventually lang/gcc3 can turn into a meta-pkg.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-30 10:34:34 +0000