| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Changes since 2.4.2 are too numerous to mention, with over 4,700 lines
in the ChangeLog file. However, this release does at least fix a large
number of build failures on SmartOS, and doesn't appear to cause any
obvious regressions in bulk builds performed by Joerg and myself.
Some pkgsrc cleanups while here, including merging the MirBSD patches
correctly. It couldn't be made much clearer how to properly integrate
patches here to ensure they are not lost. Next time you might not be so
fortunate!
|
|
By default CMAKE_INSTALL_PREFIX points to PREFIX, but some software requres
custom subprefix. At least blender and brlcad are in this category.
To set new prefix it's sufficient to set CMAKE_INSTALL_PREFIX in a package,
for example (in brlcad):
CMAKE_INSTALL_PREFIX=${PREFIX}/brlcad
Reviewed by <joerg> and <jperkin>.
|
|
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.
|
|
overrides for libtool. This allows us to easily get the fixed version
from our libtool in place without having to hunt down for the specific
bugs in random places. Disable the override explicitly in clisp, which
installs a copy without explicitly depending on libtool at run time.
|
|
wrapped version by full path. This fixes some cases where the wrappers
have been bypassed. lang/lua52 triggered the investigation as it failed
to link against libreadline, which should have been translated to
libedit. Tested by jperkin and myself with full bulk builds.
|
|
If set to yes, set GNU standard installation directories with pkgsrc
configured settings for cmake GNUInstallDirs module.
The default is yes.
|
|
their files in non-standard locations (e.g., qt5).
From Niclas Rosenvik.
|
|
It may be triger of unwanted rebuild.
|
|
with packager-chosen prefixes (as with portaudio-devel recently).
|
|
--libdir handling, same as for --mandir and --infodir.
Currently, HAS_CONFIGURE_LIBDIR=no by default unless libdir related variables
are set, but it will be switched to "yes" after all packages have been checked
(and SET_LIBDIR will be deprecated).
|
|
This file is from libtool-1.x, which is not in pkgsrc any longer
(using libtool-2.x since 2009). Also, it was only used for packages
using autoconf-2.13 AND libtool; I found three packages in pkgsrc with
that combination, and all of them still build on NetBSD-6.99.24/amd64
after this change.
|
|
|
|
|
|
Rationale: undocumented, easily replaced with "CONFIGURE_ARGS+=--libdir="
and only used by 10 packages.
|
|
|
|
|
|
Make sure cmake does this.
|
|
|
|
|
|
the default libdir (and there for be passed to ./configure), this is the
best way to deal with the 'lib64' problem on x86_64-linux systems (with
most some packages).
Also add SET_LIBDIR, GNU_CONFIGURE_LIBDIR, and GNU_CONFIGURE_LIBSUBDIR to
_PKG_VARS.gnu-configure
|
|
|
|
configure scripts as the value of --libdir.
On Linux x86_64 set GNU_CONFIGURE_LIBDIR to ${GNU_CONFIGURE_PREFIX}/lib,
this will stop package trying to install into ${PREFIX}/lib64.
|
|
to santise environment
|
|
(look in lang/python/application.mk). Noticed by Rhialto in PR 44868.
|
|
Thorsten Glaser.
|
|
|
|
|
|
a cross-compile like environment otherwise.
|
|
|
|
pkgsrc.
|
|
|
|
that they are private to the current file.
|
|
|
|
including file is always the first in the search path.
|
|
|
|
to tools. Also cmake wants cpack to exist in the same directory so
toolise it and make cmake and cpack imply each other.
|
|
the configure stage of a build (by setting USE_CMAKE=yes).
|
|
it. It had only been used to change the "nerrors" variable in bulk
builds, but this variable is not used further anyway.
|
|
|
|
REPLACE_INTERPRETER takes place before the portability check. Shell
scripts that will use bash anyway do not need to be checked for
portability problems.
|
|
cross-compile support.
- NATIVE_MACHINE_GNU_ARCH, NATIVE_LOWER_ARCH, NATIVE_MACHINE_ARCH,
NATIVE_MACHINE_PLATFORM and NATIVE_MACHINE_GNU_PLATFORM work
like the counterpars without NATIVE_ prefix. Expansion of
NATIVE_LOWER_ARCH and NATIVE_MACHINE_ARCH is enforced early,
so that MACHINE_ARCH can be overriden in mk.conf to specify the
target architecture.
- Provide a default of NO for USE_CROSS_COMPILE. This will be the
main switch to activate cross-compiling and adding it now makes
it possible to merge more of the patches for specific packages.
- Set --build and --host when cross-compiling, the former using the
just added variable NATIVE_MACHINE_GNU_PLATFORM.
Supported-by: Google SoC 2007
Looks good: jlam@
|
|
CHECK_INTERPRETER bulk build has shown a surprising number of
packages using it.
|
|
|
|
We fix GNU configure script stupidity by directly replacing the stock
install-sh script provided by the software with the BSD install-compatible
sysutils/install-sh script.
A new package-settable variable comes to life:
INSTALL_SH_OVERRIDE is a list of files relative to WRKSRC which
should be overridden by the install-sh script from
sysutils/install-sh. If not defined or set to "no", then
no files are overridden.
Possible values: no, defined, undefined.
Default value: defined when GNU_CONFIGURE is defined, undefined
otherwise.
Get rid of the install_sh tool, which is no longer needed.
|
|
must point to a shell script (as the name implies), not to a binary.
|
|
is a new target "show-all" that fits to the existing "debug",
"show-tools", "show-vars" targets. It prints a list of the variables
that make up the public interface to pkgsrc. Running this target is
especially useful if you want to do some things, you know that they must
have been implemented but you don't know what it is called. It also
shows the "class" of a variable (user-defined, package-defined,
system-defined).
|
|
Improved the documentation.
|
|
|
|
|
|
|
