Age | Commit message (Collapse) | Author | Files | Lines |
|
pkgsrc); simply # makes older bmake hork up in combination with some shells.
|
|
libtool-base includes "Fix version_type settings for the non-NetBSD
platforms in the CXX and F77 cases." And "Pull in the fix for the
symlink vulnerability.")
Several packages have been changed to reflect the better libtool-base,
but old LIBTOOL_REQD allowed old 1.4.2 version. So new packages had
wrong library versioning like: libasprintf.so.0.0, libsvn_delta-1.so.0.0,
and libXrender.so.0.0.
Okayed by wiz@.
|
|
apparently not updated any more.
|
|
|
|
some pickier awks (e.g nawk) refuse the regex otherwise
|
|
--recheck from re-executing the configure script by inserting "exit 0"
judiciously. This works with configure scripts generated by autoconf>=2.13
and fixes problems with running config.status on Solaris systems where
/bin/sh isn't POSIX enough.
|
|
|
|
BUILD_ENV is used to set the environment for the sub-make processes that
are invoked for each phase after and including buildlink.
|
|
Package Makefiles may now directly include compiler.mk.
* Don't include compiler.mk within bsd.prefs.mk any longer. It was only
included for the purposes of defining CC_VERSION. Packages that want
to test the value of CC_VERSION should now first include
"../../mk/compiler.mk". Any GCC_REQD statements in package Makefiles
should be set before compiler.mk is included.
* Simpllfy pkgsrc/mk/compiler/*.mk files as a result of not needing to
be included indirectly by bsd.prefs.mk. We remove the special handling
associated with detecting whether the file was included from within
bsd.prefs.mk. These files are now much more straightforward to write
and understand.
* G/C the BSD_PREFS_MK stack mechanism as the only users (compiler/*)
no longer need it.
* Ensure that directories are prepended to the PATH only from within
bsd.pkg.mk.
|
|
after the changes in revision 1.27 of tools.mk to hide the auto* tools
between pre-configure and do-configure.
|
|
config.status. Instead, only block "config.status --recheck", which
re-executes the GNU configure script. This still allows config.status to
overwrite post-configure changes to Makefiles and config.h files, so those
changes should (properly) be applied to Makefile.in and config.h.in
instead.
|
|
|
|
As seen in devel/libg++ with its libg++.info file...
|
|
by cd'ing into it. Also symlink the missing script instead of copying it.
|
|
relative to ${WRKSRC}. Also automaticslly set LIBTOOL_OVERRIDE if
USE_LIBTOOL is defined, as the vast majority of packages need both if they
need USE_LIBTOOL. The default LIBTOOL_OVERRIDE overrides libtool scripts
up to a directory depth of 2 within ${WRKSRC}.
Note that SHLIBTOOL_OVERRIDE must still be set manually in package
Makefiles that need it; however, it's also been changed to be a list of
shell globs relative to ${WRKSRC}.
|
|
be lists of shell globs relative to ${WRKSRC}.
|
|
|
|
|
|
don't want it to execute during the build phase as it might overwrite
post-configure changes we might have made to the generated files. Packages
that don't want this behaviour can simply set:
CONFIG_STATUS_OVERRIDE= # empty
in the package Makefile.
|
|
${LOCALBASE}/bsd/share/mk/zoularis.mk exists.
|
|
save the value of LDFLAGS, CPPFLAGS, etc. in the config.cache file.
However, they don't store the value correctly if it contains leading
spaces. This leads to sub-configure scripts that examine to cache to
error out saying that the build environment changed. Use a make
variable trick to strip off all of the leading spaces on these variables
when passing them via CONFIGURE_ENV.
|
|
default to overriding ${WRKSRC}/config.{guess,sub} so packages can
recognise platforms such as NetBSD/shark.
|
|
|
|
transformations.
|
|
|
|
|
|
to CONFIGURE_ARGS if USE_X11 is defined i.e no need to special case
xpkgwedge usage.
Please note that previously these were added to CONFIGURE_ARGS
as soon as xpkgwedge was used even if the package did not actually
defined USE_X11 or something implying it.
|
|
before replacing them.
|
|
replaced by pkgsrc/mk/gnu-config/missing. This avoids requiring
autoconf and automake as hidden build dependencies when they're not ever
invoked by the build process.
|
|
|
|
"${MAKE}" contains forward slashes. Just pass the bare name of ${MAKE} to
the configure phase as we ensure that "make" is always calling the correct
one symlinked into the .tools directory.
|
|
|
|
package.
|
|
record it only if the package actually used the compiler.
|
|
to choose the correct Perl dependency.
|
|
computation. The motivation for this is that kdelibs3 was overflowing ls
through xargs.
|
|
duplicates the change made in rev. 1.1368 for libtool.
|
|
use LIBTOOL_OVERRIDE. In the buildlink[23] case, that is supposed to be
the one in ${BUILDLINK_DIR}. Create new private variables _LIBTOOL and
_SHLIBTOOL to hold these paths.
|
|
|
|
|
|
building of software. For packages that use either buildlink2 or
buildlink3, this would be the wrapper script in ${BUILDLINK_DIR}.
* Garbage-collect _BLNK_WRAP_SETENV.* as those are not needed after
the above changes. Configure and make processes will automatically
find the right compilers in the PATH.
* PKGLIBTOOL and PKGSHLIBTOOL are no longer needed since LIBTOOL and
SHLIBTOOL point to the correct libtools regardless of any
USE_BUILDLINK[23] definitions.
|
|
that we're trying to compute for PREPEND_PATH. Instead, pass it through
the environment.
|
|
spaces, use the :Q modifier instead of double-quoting the value. This
fixes breakage when executing the just-in-time su targetes.
|
|
If we're not compiling anything, we're likely not installing any shared
libraries.
|
|
(by checking PREPEND_PATH) and only for those phases of the build that
care about the PATH (buildlink or later). We also pass the PATH to
those same phases of the build so that executing ${CC} will work correctly
from custom {pre,do,post}-* targets that occur at buildlink time or
later.
|
|
|
|
CC is something like ccache or distcc that relies on finding the true
compiler in the PATH.
|
|
instead of running pkg_delete to be consistent with the other commands
(which all use 'make ...').
|
|
a stack-like mechanism in bsd.prefs.mk to detect when a we're inside
bsd.prefs.mk.
|
|
PMC.
|