Age | Commit message (Collapse) | Author | Files | Lines |
|
which are the full option names used to set rpath directives for the
linker and the compiler, respectively. In places were we are invoking
the linker, use "${LINKER_RPATH_FLAG} <path>", where the space is
inserted in case the flag is a word, e.g. -rpath. The default values
of *_RPATH_FLAG are set by the compiler/*.mk files, depending on the
compiler that you use. They may be overridden on a ${OPSYS}-specific
basis by setting _OPSYS_LINKER_RPATH_FLAG and _OPSYS_COMPILER_RPATH_FLAG,
respectively. Garbage-collect _OPSYS_RPATH_NAME and _COMPILER_LD_FLAG.
|
|
verbose message displayed on patch failure is in fact displayed on
patch failure. It defaults to "no" if PKG_DEVELOPER is defined,
"yes" otherwise. While here, rename PKG_PATCH_FAIL to PKGSRC_PATCH_FAIL.
|
|
real effect at all.
|
|
before any @dirrm's are executed. Rather, put it explicitly at the top of
the final static PLIST generation code.
|
|
all of the .a, .la, .so, and .so.* files in the PLIST. This will
autogenerate the PLIST entries based on the informaion in the .la file.
This include print-PLIST support; if LIBTOOL_LA_FILES contains an
installed .la, its entries will be elided from the output PLIST template.
|
|
defined, note thatthe patch failure may be due to incompatible
build options and/or local patches, and suggest building with fewer.
|
|
and applied to the package sources. The existing options are:
PATCH_DIST_STRIP - option that sets the pathname strip count.
PATCH_DIST_ARGS - the list of arguments to pass to patch(1).
The new options are:
PATCH_DIST_CAT is the command that outputs the patch to stdout.
For each of these variables, there is a patch-specific variant that
may be set, i.e. PATCH_DIST_STRIP.<patch>, PATCH_DIST_ARGS.<patch>,
PATCH_DIST_CAT.<patch>.
|
|
build-defs-message target so that PKG_OPTIONS doesn't show up as a
settable variable in the displayed message.
|
|
|
|
are set, and it'd be nice to know which ones before the default
dependencies are installed.
Create a new target "pre-install-depends" that is executed before
dependencies are installed. Move the display of BUILD_DEFS
(build-defs-message) into pre-install-depends so that they are displayed
before dependencies are installed.
|
|
as well. (Noted by wiz@)
|
|
executes the utility even in such a case. Based on the patch provided
by Hiramatsu Yoshifumi in PR pkg/25777.
|
|
of files installed for SETGIDGAME packages.
This will help address PR pkg/25313 and PR pkg/26236.
|
|
|
|
Robert Elz in PR pkg/26448 (at least for now).
If you want to use it, PKG_RESUME_TRANSFERS must be set to [Yy][Ee][Ss].
While here, no need to use ${AWK} to get the size with ${WC} -c,
${WC} -c < file is enough.
Thanks to Robert Elz for suggestions, still I have to fix the problems
reported in the PR.
|
|
o Use ${WC} -c instead of using ${LS} -l, which works with
symlinks.
o Only assign -R to FETCH_RESUME_ARGS when FETCH_CMD is the
default value (NetBSD's ftp).
o Fix for www/navigator package, which uses DIST_SUBDIR.
o Replace another [ with ${TEST}.
o Print a warning when FETCH_CMD != ftp and FETCH_RESUME_ARGS
is empty (resume will not be possible).
Thanks to cube@ and tron@ for reporting/helping with the problems.
|
|
1. don't hardcode true, echo and [
2. Cope with distfiles which are located in a DIST_SUBDIR
3. Don't always assume there will be a size field in the ${DISTINFO_FILE}
XXX The refetch mods make an assumption that an exit code of 0 from a
${FETCH_CMD} means that the transfer has been completed successfully,
and this used not to be the case. I haven't tested this assumption
recently.
|
|
$http_proxy or $ftp_proxy are defined (for the moment, NetBSD's ftp(1)
doesn't support this).
While I'm here, move FETCH_CMD from bsd.pkg.mk to bsd.pkg.defaults.mk,
and add the new variable FETCH_RESUME_ARGS (-R by default with ftp(1)
from NetBSD/pkgsrc).
If you want to use wget to resume transfers, you should use something
like:
FETCH_CMD=wget
FETCH_RESUME_ARGS=-c
|
|
|
|
buildlink3.
|
|
|
|
ID. from Roland Illig.
|
|
|
|
shell syntax.
this allows the pkgsrc framework to work with IRIX 5.3 and Solaris'
sh(1) built-in test(1).
|
|
Saves trailing \ properly.
Addresses PR pkg/26022 by Akio OBATA.
|
|
SunOS.
|
|
pre-req fails. Fixes an error noticed by Kimmo and others, where a
build would blindly continue even if the pre-requsite package wasn't
built correctly, and is fallout from the "sh -e" and make(1) changes
in NetBSD-current.
|
|
use ABI, but allows IRIX and particularly IRIX64 to find the correct libraries
especially when linking against X11 libs. Tested over several months and
multiple bulk-builds.
|
|
into the new bsd.sites.mk file. Ok'ed by Hubert Feyrer and
Jan Schaumann in tech-pkg@.
|
|
List extracted from http://download.openoffice.org/1.1.1/source.html
|
|
days. Comment it out for now.
|
|
in tech-pkg@.
|
|
and let tools.mk take care of the rest.
|
|
Change that: if it's set to YES, require devel/patch. If building
devel/patch, set _OPSYS_GPATCH_REQD to NO, as otherwise we have a
circular dependency.
|
|
with gavan@NetBSD.org at pkgsrcCon.
Within the pkgsrc infrastructure, LOCALBASE has two different meanings:
(1) where the package being built should be installed, and
(2) where to find previously installed packages.
Most instances of case (2) should be converted to use EVAL_PREFIX,
but there are some cases where this is impossible. To resolve this,
we preserve LOCALBASE to mean (2) and we create a new variable
INSTALLATION_PREFIX to mean (1).
INSTALLATION_PREFIX is meant to be set some time before bsd.pkg.mk is
included, and provides the value for PREFIX if it's defined, e.g.
NO_MTREE= yes
INSTALLATION_PREFIX= /
.include "../../mk/bsd.pkg.mk"
This allows us to remove all cases where PREFIX is explicitly set in
the package Makefile, e.g. Java VM packages, qmail, etc.
|
|
to bl3 and remove f2c's buildlink2.mk file.
|
|
|
|
SETGIDGAME: specifies whether or not certain games are installed setgid
GAMEGRP: the group owning games if SETGIDGAME is set
GAMEOWN: the user owning games if SETFIDGAME is set
GAMEMODE: the mode to install games as
Use these to provide INSTALL_GAME (for example for PR pkg/25313), and
set them to meaningful values under NetBSD.
|
|
"yes"). So any packages that have old GNU configure script that
does not support --infodir option (while using INFO_FILES) can set
CONFIGURE_HAS_INFODIR=NO.
This was suggested by agc@ as a clearer definition.
|
|
I have used this successfully to install over 300 info files
using INFO_DIR=share/info.
Also add new variable called NO_CONFIGURE_INFODIR (as suggested
by Greg Woods) because some autoconf-style configure scripts
don't know --infodir. (The alternative is to use HAS_CONFIGURE
and add the needed CONFIGURE_ARGS.)
Please note that the info tool may not find custom INFO_DIR
unless it is configure to know it. (I will update gtexinfo
for this, but if using native info you are on your own
if you customize this.)
|
|
(mainly intended for shlib use, but for homeful use on all libraries so
that currently static libs can be "provisioned" for future shlib use).
|
|
can include buildlink3.mk files. This change also causes work/.tools/bin
to appear after work/.buildlink/bin in the PATH, but we never relied on
this behaviour, so this side-effect should have no impact.
|
|
|
|
as well.
|
|
in lang/perl58/Makefile. (It had been set previously only in bsd.pkg.mk.)
|
|
what appears to be a routing loop. comment it out for the moment.
|
|
so that Interix can set the default mode to 0775. Then add "install_sh"
to CONFIGURE_ENV so it uses ${INSTALL}, not the package-supplied
install script (as is done for autoconf $INSTALL).
|
|
${_STRIPFLAG_INSTALL}
|
|
can't change at configure time. "mkdir_p" is now used by automake in place
of the traditional autoconf "INSTALL_DIR". Override mkdir_p in MAKE_FLAGS,
if GNU_CONFIGURE is set, with ${INSTALL_DATA_DIR}.
|
|
packages using imake install files into X11BASE instead of PREFIX.
|