Age | Commit message (Collapse) | Author | Files | Lines |
|
automatically by pthread.buildlink3.mk. Also, factor out the pthread
library out of PTHREAD_LDFLAGS into a standalone variable PTHREAD_LIBS
and use it in packages where necessary (usually the ones that don't
have a GNU configure script).
|
|
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.
|
|
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".
|
|
|
|
|
|
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.
|
|
(Also should depend on gindent, but not fixed here.)
|
|
|
|
buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk.
|
|
|
|
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.
|
|
automatically substitute for any config.{guess,sub} files found up to a
directory depth of 2.
|
|
|
|
|
|
the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives
a value only once due to the multiple inclusion protection in the
bulldlink3.mk files. In the case where a package includes several
buildlink3.mk files that each want a slightly different version of another
dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the
strictest <pkg> dependency to be matched.
|
|
|
|
fake-la bug has been fixed.
|
|
|
|
|
|
|
|
|
|
This makes this package compile on Solaris and Linux (plus - hey! - static
linking is really from the past millennium!)
Fixes PR 23032.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
include pthread.buildlink2.mk.
|
|
|
|
|
|
dependency bumps.
|
|
Fixes endless loop problems. Report and suggestion by Greg Troxel
gdt at ir bbn com in private mail; some comments by Alistair Crooks;
patch reviewed and okayed by Jaromir Dolecek.
Bump PKGREVISION to 3.
|
|
properly.
|
|
not try to remove it, even if empty.
|
|
|
|
dependency.
|
|
so don't depend on devel/gindent on these two platforms.
* USE_BUILDLINK2 implies AUTOMAKE_OVERRIDE=NO.
* Don't use the hackish test for libwrap supplied in the configure script.
Instead, just specify the necessary variables to link against libwrap
in the package Makefile.
This closes PR 18712 by Greg A. Woods.
|
|
|
|
Patch provided in PR pkg/18701 by Julio Merino <jmmv@menta.net>
|
|
|
|
the Makefile.am file.
|
|
compiled using orbit-idl, which uses the C preprocessor to do its work, and
the C preprocessor has it's arguments transformed (correctly) by
buildlink2.
|
|
headers in ${BUILDLINK_DIR}, simply create BUILDLINK_CPPFLAGS.<pkg>
variables whose values are appended to CPPFLAGS, which are automatically
passed to the configure and build processes.
BUILDLINK_TRANSFORM.<pkg> has little use in buildlink2 since packages are
now told that the software may be found where it really is installed, not
in ${BUILDLINK_DIR} as was the case with buildlink1. Eventually, these
variables will be declared unsupported by buildlink2.
|
|
|
|
buildlink2.mk files back into the main trunk. This provides sufficient
buildlink2 infrastructure to start merging other packages from the
buildlink2 branch that have already been converted to use the buildlink2
framework.
|
|
Bump PKGREVISION
|
|
|
|
includes are actually copied to the buildlink directory.
|