2004-10-04 13:19:41 by grant beattie | Files touched by this commit (2) |
Log message:
distinguish between glib1 and glib2 in COMMENT.
|
2004-10-03 02:13:34 by Todd Vierling | Files touched by this commit (908) |
Log message:
Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
|
2004-09-22 10:10:08 by Johnny C. Lam | Files touched by this commit (703) |
Log message:
Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
|
2004-07-01 15:45:08 by Thomas Klausner | Files touched by this commit (4) |
Log message:
Unused.
|
2004-06-01 10:03:10 by John R. Shannon | Files touched by this commit (2) |
Log message:
Re: PR 25706 Syntax error prevents compilation with gcc 3.4.0
Applied patch provided by Christian Biere <christianbiere@gmx.de>
The patch ensures that G_GNUC_FUNCTION and G_GNUC_PRETTY_FUNCTION always
expand to string literals - necessary since they will be concatenated
(the source of the compilation error). This closes the PR.
|
2004-04-15 02:07:26 by Juan Romero Pardines | Files touched by this commit (1) |
Log message:
Make this build under FreeBSD.
|
2004-04-12 22:18:07 by Jan Schaumann | Files touched by this commit (2) |
Log message:
Make this build under IRIX by only applying this patch on non-irix.
(Is this patch really needed on all other platforms?)
|
2004-03-18 10:12:18 by Johnny C. Lam | Files touched by this commit (232) |
Log message:
Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly
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-05 20:25:43 by Johnny C. Lam | Files touched by this commit (256) |
Log message:
Reorder location and setting of BUILDLINK_PACKAGES to match template
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
|
2004-02-28 00:57:03 by Krister Walfridsson | Files touched by this commit (1) |
Log message:
Fix PR pkg/24464 again. We need to patch config.status instead of
config.status.overridden since the change in rev. 1.1413 of bsd.pkg.mk.
|