Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
These are supported options from the soon-to-be-committed wrapper
framework and are meant to more precisely state the intended
transformation. Also just skip over unknown commands instead of
generating an error.
|
|
|
|
|
|
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.
|
|
down we get the correct value for _PATCH_BACKUP_ARG and friends.
|
|
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.
|
|
Perl in Interix ships, so it's an appropriate default for the OS. (Still
overrideable in mk.conf explicitly.)
|
|
|
|
target takes care of this case already.
|
|
|
|
For me this fixed the build of devel/kdevelop-base version 3.1.0 with latest
automake package version 1.9.1 installed.
|
|
it to ${CAT} as a fall-through.
|
|
PKG_DEFAULT_OPTIONS.
|
|
into the bsd.options.mk framework. Instead of appending to
${PKG_OPTIONS_VAR}, it appends to PKG_DEFAULT_OPTIONS. This causes
the default options to be the union of PKG_DEFAULT_OPTIONS and any
old USE_* and FOO_USE_* settings.
This fixes PR pkg/26590.
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
that the whole pipeline returns 0. This avoids subtle breakage when the
we use built-in software and there is actually no list of files passed as
input to the pipeline, and the final egrep returns non-zero.
|
|
has a space in the filename. Without the quoting the buildlink
stage fails completely with errors. ok'ed by Johnny Lam.
|
|
|
|
remove rpath options come first. This fixes problems we may encounter
if ${_OPSYS_RPATH_NAME} is something surprising, like "-L". On Darwin,
this was causing -L/usr/lib to be stripped out of "-Wl,-L/usr/lib",
which left a bare "-Wl," on the command line.
|
|
case ${_OPSYS_RPATH_NAME} is something surprising, like "-L".
|
|
pass "-Wl,${RPATH_FLAG}..." to the linker, which can break the build
of these packages. Using -L essentially makes these arguments a no-op,
and fixes packages which were solely broken by this.
|
|
|
|
|
|
|
|
|
|
|
|
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>.
|
|
PR pkg/26576: Kouichirou Hiratsuka.
|
|
|
|
download page (cesnet, easynews, keihanna, mesh, switch).
|
|
when changing directory, breaking the resulting tsort from the printindex
script output.
|
|
Makefiles and will be removed and some point in the future.
|
|
their respective package Makefiles after they were converted to use
bsd.options.mk. These variables will be removed at some point in the
future (to be determined).
|
|
build-defs-message target so that PKG_OPTIONS doesn't show up as a
settable variable in the displayed message.
|
|
|
|
of the display. We now batch them up and print a few per line. Also,
display the supported options at pre-install-depends time.
|
|
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@)
|