Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
Discussed in tech-pkg@:
http://mail-index.netbsd.org/tech-pkg/2016/04/20/msg016755.html
Thanks to Memnon Anon!
|
|
|
|
triplet reporting as x86_64-pc-linux. Go back to the previous triplet of
x86_64-unknown-linux which matches what config.guess outputs.
|
|
|
|
script included in the ocaml-findlib package) and removes the need to call
said script explicitly from PLIST.
Packages that use findlib will now automatically add directories that are
in OCAML_FINDLIB_DIRS (set by default to $(OCAML_SITELIBDIR)/${PKGBASE})
to the file ${PREFIX}/lib/ocaml/ld.conf. This behaviour can be disabled by
undefining OCAML_FINDLIB_REGISTER.
|
|
and MKCATPAGES.
|
|
|
|
|
|
|
|
documentation to reflect the pre-install option.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
libusb-1 - Enable USB access via libusb-1.
nautilus - Enable nautilus sub-menu option.
|
|
|
|
OPSYSVARS to bsd.options.mk as they affect tests against PKG_OPTIONS
before bsd.pkg.mk is parsed.
Approved for commit during the freeze by agc@.
|
|
been broken due to NATIVE_MACHINE_ARCH no longer being set to x86_64. Fix
this by introducing HOST_MACHINE_ARCH which refers to the underlying host
architecture rather than bmake's native architecture, thus differentiating
between cross-compiling and multilib.
This is currently only set on Linux as the only OPSYS which currently
requires such a test, but can be expanded to other OPSYS as necessary.
|
|
rewrite "-isystem dir" as "-isystem,dir"
transform "-isystem,dir" in same ways as "-Idir"
rewrite "-isystem,dir" back to "-isystem dir" in cmd-sink
|
|
This allows fixing an issue with PKGSRC_MKPIE, where "gcc source.c" would
not work. Some packages rely on this test to determine if a working
compiler is available.
|
|
As suggested by wiz@
|
|
- change Linux x86 from sun-jdk6 to oracle-jdk8
- change SunOS x86 from openjdk7 to openjdk8
- change DragonFly from openjdk7 to openjdk8
leave Darwin at sun-jdk6 for now, not sure how the builtin stuff works ...
|
|
- No _GCC_* anything in mk/bsd.prefs.mk;
- No compiler flags in platform files.
Tested again on NetBSD/amd64, with and without cwrappers, with the same
outcome.
With feedback from jperkin@
|
|
- Revisit (and rename) support for FORTIFY as PKGSRC_USE_FORTIFY (instead
of PKGSRC_USE_FORT) for easier support outside NetBSD/gcc;
- PKGSRC_USE_SSP is no longer enabled by default when PKGSRC_USE_FORTIFY
is enabled;
- PKGSRC_MKPIE builds executables as PIE (to leverage userland ASLR)
- PKGSRC_USE_RELRO builds with a read-only GOT to prevent some exploits
from functioning.
Tested on NetBSD/amd64 by myself, in every combination, with and without
pkgtools/cwrappers. MKPIE is not supported at the moment with cwrappers.
Also, MKPIE is known to still break a number of packages when enabled (and
actually supported).
Tested on SunOS by jperkin@, thank you!
As discussed on tech-pkg@, the default behavior is not changed, except
where noted above.
ok bsiegert@
|
|
|
|
|
|
The only current use of this is pbulk's subject line, and Solaris 11.3
makes more sense than Oracle 11.3.
|
|
for OmniOS, stop processing /etc/release after the first line
|
|
variables are unused and in at least one case were completely wrong anyway.
|
|
tests would pass after the first successful check. Exposes library issues
in a number of packages.
|
|
in /usr/bin/awk but mawk. Use /usr/bin/gawk if it exists, otherwise
depend on gawk from pkgsrc when required.
|
|
|
|
It turns out a handful of AIX binutil-like utilities are particular
about type of object files they should examine. Instead of piping
through flags for each utility everywhere, it is easier to just export
'OBJECT_MODE=[32|64]' instead.
From Eric N. Vander Weele.
|
|
|
|
AIX is particular about the type of object files `ar` should examine.
This should be set explicitly to coincide with the user's defined $ABI.
Contributed by Eric N. Vander Weele.
|
|
Fix from Eric N. Vander Weele <ericvw@gmail.com>
|
|
with the Darwin linker. Fixes various packages.
|
|
|
|
|
|
|
|
|
|
already, plus those that are most used in OPSYS-specific sections.
|
|
conflict with pkgsrc versions of those packages, and do not interact well
with the wrappers anyway as cmake will perform simple file-based tests for
headers but the compiler will be unable to find them.
|
|
header provides the uuid_string_t typedef, which is not the case with the
version coming from pkgsrc.
|
|
|