Age | Commit message (Collapse) | Author | Files | Lines |
|
dependencies unless USE_GNU_GETTEXT is defined or IMCOMPAT_GETTEXT is set
appropriately. This should allow packages to use the glibc gettext
routines on Linux.
|
|
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.
|
|
BUILDLINK_PACKAGES, then set BUILDLINK_PKGBASE.<pkg> explicitly so that
we can map from <pkg> to BUILDLINK_PKGBASE.<pkg>.
|
|
to BUILDLINK_DEPENDS unless their respective buildlink3.mk files are
included by the top-level Makefile.
|
|
built-in or not into a separate builtin.mk file. The code to deal
checking for built-in software is much simpler to deal with in pkgsrc.
The buildlink3.mk file for a package will be of the usual format
regardless of the package, which makes it simpler for packagers to
update a package.
The builtin.mk file for a package must define a single yes/no variable
USE_BUILTIN.<pkg> that is used by bsd.buildlink3.mk to decide whether
to use the built-in software or to use the pkgsrc software.
|
|
(The DESCRiption was same as the other gettext package,
and the COMMENT mentioned "Tools".)
|
|
environment overrides all other settings.
|
|
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.
|
|
|
|
automatically now.
|
|
as PREFER_PKGSRC. Preferences are determined by the most specific
instance of the package in either PREFER_PKGSRC or PREFER_NATIVE. If
a package is specified in neither or in both variables, then PREFER_PKGSRC
has precedence over PREFER_NATIVE.
|
|
whether the software is built-in or not. This facilitates implementing
the forthcoming PKGSRC_NATIVE variable.
|
|
block that decides whether package FOO is built-in or not. If the
platform is listed in IMCOMPAT_FOO, then treat FOO as being not
built-in.
|
|
spaces, use the :Q modifier instead of double-quoting the value. This
avoids breakage when executing the just-in-time su targets.
|
|
simpler to understand.
|
|
value outside of buildlink-related files.
|
|
BUILDLINK_PREFER_PKGSRC
This variable determines whether or not to prefer the pkgsrc
versions of software that is also present in the base system.
This variable is multi-state:
defined, or "yes" always prefer the pkgsrc versions
not defined, or "no" only use the pkgsrc versions if
needed by dependency requirements
This can also take a list of packages for which to prefer the
pkgsrc-installed software. The package names may be found by
consulting the value added to BUILDLINK_PACKAGES in the
buildlink[23].mk files for that package.
|
|
|
|
fixes build problems under Darwin.
|
|
don't keep re-evaluating it.
|
|
|
|
|
|
|
|
recommended by seb :)
|
|
does it correctly for us.
|
|
|
|
|
|
buildlink3 framework.
|
|
doesn't completely gratuitously export a symbol that conflicts with
libiconv
|
|
packages.
|
|
0.11.5nb1 or higher, 0.11.5 is good enough.
fixes build with slightly older installation of gettext-lib.
|
|
|
|
|
|
Noted by Matthias Scheler.
|
|
|
|
Should anybody feel like they could be the maintainer for any of thewe packages,
please adjust.
|
|
|
|
the right version for most other packages (AFAICT), but this package seems
to be different.
|
|
|
|
Makefiles simply need to use this value often, for better or for
worse.
(2) Create a new variable FIX_RPATH that lists variables that should
be cleansed of -R or -rpath values if ${_USE_RPATH} is "no". By
default, FIX_RPATH contains LIBS, X11_LDFLAGS, and LDFLAGS, and
additional variables may be appended from package Makefiles.
|
|
fix the problem where gettext-lib on certain OSes that already have iconv
functions in libc don't need to link against libiconv.
|
|
gettext-lib/buildlink2.mk to be included anywhere in a Makefile instead
of only after where GNU_CONFIGURE may be defined.
|
|
not build a shared library on platforms that libtool thinks can't handle
inter-library dependencies, e.g. OpenBSD and Solaris.
|
|
building of these packages by using buildlink2.
|
|
gettext.
|
|
<URL:http://mail.gnu.org/pipermail/bug-gnu-utils/2002-September/002920.html>.
|
|
if we don't actually require gettext-lib>=0.11.5. For other installations
where keeping an older gettext around isn't wanted, convert the gettext
dependency to >=0.11.5 and include the necessary buildlink2 magic for
libiconv support.
|
|
Do it better now - ugly but the logic here is a bit twisted.
|
|
confusion.
|
|
uses a compile/link test to determine the presence or absence of libintl.
Instead it uses a file existence test for libintl.{a,so,la} in specific
directories. buildlink2 can't work around this, but gettext.m4 does
provide a new configure option "--with-libintl-prefix" to specify in which
directory to look for libintl, so use it. It's harmless on older GNU
configure scripts as they will ignore unknown options, but it will fix
gettext detection with newer GNU configure scripts that use the new
gettext.m4. Also protect a forced cache value from being passed to the
configure script unless libintl really does exist.
|