| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
Relying on native variables like MKBSDTAR only works when using the native
make, and should be avoided as they are not set when using a bootstrap.
Should fix build of lang/go117 with bootstrapped NetBSD, as bsdtar from
pkgsrc is unable to handle the distfile due to locale errors.
|
|
Explain that we should probably use cmake's RPATH support instead of
turning it off and passing it via LDFLAGS, but that this change seems
somewhat risky.
(This is a comment-only change.)
|
|
|
|
|
|
Improves language and mirrors LD_TOXIC_PATH nomenclature available on at
least the SunOS dynamic linker. The previous name is retained for now
for compatibility, even though I get the feeling I'm the only person who
is actually using this feature.
|
|
|
|
PostgreSQL 14 contains many new features and enhancements, including:
Stored procedures can now return data via OUT parameters.
The SQL-standard SEARCH and CYCLE options for common table expressions have been implemented.
Subscripting can now be applied to any data type for which it is a useful notation, not only arrays. In this release, the jsonb and hstore types have gained subscripting operators.
Range types have been extended by adding multiranges, allowing representation of noncontiguous data ranges.
Numerous performance improvements have been made for parallel queries, heavily-concurrent workloads, partitioned tables, logical replication, and vacuuming.
B-tree index updates are managed more efficiently, reducing index bloat.
VACUUM automatically becomes more aggressive, and skips inessential cleanup, if the database starts to approach a transaction ID wraparound condition.
Extended statistics can now be collected on expressions, allowing better planning results for complex queries.
libpq now has the ability to pipeline multiple queries, which can boost throughput over high-latency connections.
|
|
|
|
prevents mangling by wrappers in mysterious circumstances
|
|
|
|
|
|
/usr/share/mk
|
|
|
|
|
|
|
|
Presumably there's a way to make this work, but it probably requires
changes to the bootstrap kits.
|
|
|
|
|
|
|
|
- Needed for proper aarch64-apple-darwin* detection
- Upstream accepted NetBSD aarch64eb patch
- Manually merged config.guess revision 1.22 on top of the upstream version
for NetBSD/evbarm fixes (currently the only local change we have)
Tested on:
NetBSD x86_64, earmv7hf and aarch64
macOS aarch64
|
|
|
|
|
|
This allows RELRO to be used when building imake packages.
XXX: I'm not certain if this is the right place, but this already seems
to be cargo-culted in individual package Makefiles...
|
|
The documentation did not mention that conditional entries in PLIST
files are skipped. Pkglint doesn't know this either and issues wrong
notes that some directories are redundant in INSTALLATION_DIRS when in
reality they need to be listed there.
While here, filter out some duplicate directories. This invokes the
command for creating a single directory less often. Since PLIST files
are usually sorted, files in the same directory tend to be listed near
each other.
The fallback to the plain 'uniq' is needed for SCO_SV, which does not
define TOOLS_PLATFORM.uniq.
|
|
|
|
|
|
PR pkg/56337
|
|
PR/56315.
|
|
|
|
|
|
|
|
Add a test to check that an xbase set is installed when a tool depends on
X11 and X11_TYPE=native.
Thanks to Greg and Edgar for their comments and suggestions!
|
|
Fixes builds inside an x86_64 chroot where packages add x86-specific flags
based on the output of uname even though we're building for aarch64. CMake
provides the CMAKE_APPLE_SILICON_PROCESSOR variable for this situation.
|
|
|
|
|
|
dash considers \1 to be octal escape.
for PR pkg/56248, from Michael Forney's suggestion.
$echo seems to be used for performance here (was previously cat) and not
for compatibility with some esoteric system.
I misunderstood things, and failed to test the last bootstrap diff, breaking
bootstrap on Ubuntu for a while.
|
|
|
|
that to BUILDLINK_PASSTHRU_DIRS.
|
|
|
|
|
|
|
|
|
|
|
|
This delivers 64 bit index BLAS libraries alongside 32 bit ones. This is often
called ILP64 in the BLAS world, as opposed to LP64 where integers are 32 bit
due to the Fortran default integer type, not to be confused with the basic
system ABI used by C. For really large vectors on modern machines, you want
an 'ILP64' BLAS and layers on top of it.
In preparation of better support for vendor BLAS libraries, I had to realize
that you better use the C interfaces supplied by them, not the netlib one
strapped on. A simple reason of practicability: The vendor blas libraries,
just like openblas, like to ship all symbols in one library, so you get them
whether you want it or not. Also implementations may skip Fortran and implement
the underlying functionality directly in C anyway, so one might skip a
layer of indirection. Future will tell if other layers will follow. We still
have the framework of individual layers from Netlib to combine with certain
implementations that miss them (Accelerate framework comes to mind, which
needs further work).
The framework of netlib reference packages for the separate libraries
is instructive and helps keeping things small when you not need all of them.
The installation location of the headers is now in a subdirectory to be able
to have 32 and 64 bit variants independently. The 32 bit ones are linked to
${PREFIX}/include to keep the old picture. We could be brave and remove
those, but there is some value in a build just trying -lcblas and
inclusion of <cblas.h> to be happy.
There is one blas.buildlink3.mk that is supposed to be used only once and
so avoids a combination of conflicting libraries (as the 64 bit index symbols
have the same names as the 32 bit ones).
Basic usage for getting LAPACK+BLAS is still the same as before. You get
CBLAS and LAPACKE by setting BLAS_C_INTERFACE=yes in the package. The 64 bit
indices are selected via BLAS_INDEX64=yes.
Due to the special nature of the Accelerate framework, a package has to
explicitly indicate support for it and it will also not appear on the
list of implementations by default. The reason is that it does provide
mainly CBLAS and CLAPACK (another version of C interface to LAPACK, f2c-based)
and BLAS/LAPACK with f2c/g77 calling conventions. A default build with
gfortran would not like that
This commit also fixes up math/py-numpy and math/py-numpy16 to follow the
new scheme, as that are the only packages directly affected by the change
in CBLAS providership.
|
|
|
|
|
|
|
|
BUILDLINK_CONTENTS_FILTER, as discussed on tech-pkg on may 26 and 27.
Fix an issue with www/libwebsockets/buildink3.mk where some cmake files
are missing from the .buildlink dir, causing config failure in consumer
packages.
|
|
|
