Age | Commit message (Collapse) | Author | Files | Lines |
|
${LOCALBASE}. Some packages' configure scripts resolve all paths to
physical paths, and since buildlink3 suppresses references outside of
${LOCALBASE}, it can break the build of those packages.
This should fix the problem noted by Nathan Williams in the thread
titled "x11/tk build failure" at:
http://mail-index.netbsd.org/tech-pkg/2004/02/17/0004.html
|
|
uses {} to list several "or" dependencies.
|
|
cd: cd BUILDLINK_PREFIX.foo_not_found
We now say that the package wasn't installed at the time that we were
trying to buildlink its files.
|
|
|
|
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.
|
|
ucode compilers only support building the "o32" ABI.
|
|
|
|
|
|
|
|
|
|
foo>=0.3 foo>=0.4" are collapsed into a single "foo>=0.4" dependency.
|
|
|
|
|
|
pkg-config to only look in ${BUILDLINK_DIR}/lib/pkgconfig for *.pc files.
This will correctly hide the presence of software from configure scripts
that query pkg-config for that information.
Idea suggested by Julio M. Merino Vidal.
|
|
|
|
|
|
actually has some effect.
|
|
|
|
symlinking into ${BUILDLINK_DIR} for a more complete set of headers.
|
|
compiler set. This will cause the libtool configuration found in several
packages to use the correct C++ compiler even though the package doesn't
use C++. This was causing bugs when CXXFLAGS contained flags not
understood by the system gcc-2.95.3.
|
|
script will understand these commands.
|
|
efficiency reasons.
|
|
variable with an exponentially increasing size. Fixes infinite loop when
building security/cyrus-saslauthd.
|
|
|
|
the "r" command to allow paths ending in "/". This should fix PR 24352.
|
|
similar ways to -install_name, and all need the subsequent argument to be
protected from /path/shlib -> -L/path -lshlib transformations.
|
|
|
|
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.
|
|
spaces, use the :Q modifier instead of double-quoting the value. This
fixes breakage when executing the just-in-time su targetes.
|
|
due to a type on gcc.mk that causes the ${_GCC_PREFIX}/bin to always be
prepended to the PATH. The problem that was hiding was "make" resolving
to ${TOOLS_DIR}/bin/make if the package used GNU make, which broke
building since the package Makefile is a BSD Makefile and we passed
PATH to some phases of the build. Fix this by expanding MAKE to the
full path to ${MAKE} in bsd.prefs.mk. We also garbage collect the now
useless checks for PHASES_AFTER_BUILDLINK that cluttered the PREPEND_PATH
code.
|
|
(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.
|
|
|
|
Approved by jlam@.
|
|
simpler to understand.
|
|
value outside of buildlink-related files.
|
|
BUILDLINK_PREFER_PKGSRC
This variable determines whether or not to prefer the pkgsrc
versions of software that is also present in the base system.
This variable is multi-state:
defined, or "yes" always prefer the pkgsrc versions
not defined, or "no" only use the pkgsrc versions if
needed by dependency requirements
This can also take a list of packages for which to prefer the
pkgsrc-installed software. The package names may be found by
consulting the value added to BUILDLINK_PACKAGES in the
buildlink[23].mk files for that package.
|
|
were inadvertantly added when replacing the awk script with a sed script.
|
|
debugging purposes.
|
|
|
|
just assume they do unless they're known _not_ to work. So far, only
Darwin-5.* suffers from this problem, apparently because they use some
bizarre version of zsh for /bin/sh.
|
|
noted in USE_LANGUAGES.
|
|
packages which pass these gcc-specific flags.
also ignore -Werror; if a package passes -Werror, it's expecting that
the compiler is gcc, which in this case it is not. SunPro often emits
warnings on code which gcc doesn't, so transforming this flag to
-errwarn is counterproductive.
|
|
Also remove unneeded section on OS-specific wrappers that's handled
automatically nowadays by pkgsrc/bl3.
|
|
|
|
header.
|
|
several arguments together) from the command line and push it onto the
stack. Pop the top off the stack, process, and push replacement
arguments onto the stack. Repeat the last step until no more processing
is done, and we have our final argument to be passed on through to the
rest of the wrapper script.
|
|
|
|
specify library orderings with:
BUILDLINK_TRANSFORM+= reorder:l:crypt:crypto
The wrapper scripts then reorder the libraries so that -lcrypt will
always come before -lcrypto. If there are lots of reorder:l:...
commands, then the algorithm looks a bit like a topological sort.
|
|
We just let the rest of the wrapper scripts do it now that we can't
overflow a fixed-sized circular buffer.
|