Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
This notably allows emulators/qemu to properly detect support for PIE, and
disable it where appropriate. This does not work with cwrappers yet.
|
|
|
|
Revert this fix until we can determine a possibly better fix.
|
|
Allow the dylib install_name to be just the library basename
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Skip any lines of otool output that do not start with a tab, ensuring we
only check valid files and ignore e.g. shell scripts. Older versions of
otool would simply print no output on such files, whereas newer releases
print "is not an object file".
|
|
It completely broke the checks, resulting in broken binary packages
being shipped, e.g. https://github.com/joyent/pkgsrc/issues/104
|
|
At the previous location it was overridden if a gcc from pkgsrc was used.
Problem found by bacon@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The "split" program is not managed by the tools framework. It just has a
wrapper that is placed into the same directory. This is confusing since
intuitively, "split" is a tool like many others.
The "duplicate script for target" warning from Make is therefore correct,
albeit obscure.
Currently, neither the pkgsrc infrastructure nor pkglint check for
allowed tool names.
|
|
The TOOLS_CREATE variable is only ever appended to, without checking for
duplicates. In some rare cases, this produces warnings about
doubly-defined make targets. An example is adding USE_TOOLS+=strip to
pkgtools/pkglint:
".../mk/tools/create.mk" line 149: warning:
duplicate script for target ".../work/.tools/bin/strip" ignored
The above line number 149 is zero-based, which in reality means the
duplicate definition is in line 150.
|
|
|
|
|
|
SUBST_)
|
|
|
|
CMAKE_PKGSRC_BUILD_FLAGS
If set to yes, disable compiler optimization flags associated
with the CMAKE_BUILD_TYPE setting (for pkgsrc these come in from
the user via variables like CFLAGS). The default is yes, but you can
set it to no for pkgsrc packages that do not use a compiler to avoid
cmake "Manually-specified variables were not used by the project"
warnings associated with this variable.
|
|
|
|
|
|
Linux version of readelf (at least on Arch) translates output
(e.g. "Shared library") and makes the script broken.
|
|
The voodoo that checks this now keeps track of which packages caused
what, and in addition to the list FORCED_PKGSRC of packages that have
been forced to non-builtin, it also produces a list FORCED_PKGSRC_REASONS
of the form pkg:causing-pkg{,causing-pkg...}.
(which means that USE_BUILTIN.pkg has been set to no because
USE_BUILTIN.causing-pkg is set to no.)
This could probably just be one list but I'm not sure if anything is
relying on the format of the current FORCED_PKGSRC.
|
|
|
|
|
|
Because print-PLIST uses mixed case (unlike most of the other make
targets), it is not found by the keyword search of "make help".
|
|
|
|
|
|
Remove now obsolete packages.
|
|
|
|
The variable names are typically mentioned in one of these styles:
# Package-settable variables:
#
# VARNAME
# Description
# Package-settable variables:
#
# VARNAME
# Description
Lines that are indented with two tabs contain text. And if one of these
lines starts with a variable name, it is just a coincidence. A practical
example of this happening is in mk/misc/developer.mk 1.24, where PKGNAME
starts a line of description.
|
|
|
|
|
|
|
|
No objection on tech-pkg@
Tested on NetBSD/amd64.
|
|
|
|
|
|
|
|
|
|
- Put the main mirror at the lowest priority. it seems to be struggling.
- Add two mirrors that seem decent at the highest priority.
|
|
This switch is meant to be used by packages requiring an implementation of the
former libusb (as in devel/libusb). The original implementation can be
chosen by setting LIBUSB_TYPE to "native".
The alternative implementation libusb-compat (as in devel/libusb-compat) wraps
libusb1 (in devel/libusb1). This implementation can be chosen by setting
LIBUSB_TYPE to "compat". On NetBSD, it has the advantage of not requiring root
privileges to locate and use USB devices without a kernel driver.
This first part only imports the switch framework itself.
|