| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
TOOLS_REAL_CMD.<tool> => TOOLS_PATH.<tool>
TOOLS_REAL_ARGS.<tool> => TOOLS_ARGS.<tool>
TOOLS_REAL_CMDLINE.<tool> => TOOLS_CMDLINE.<tool>
|
|
to another. This appears to fix whatever hidden bug a bit more
completely. "make show-var VARNAME=RM" in pkgsrc/x11/kdepim3 no longer
returns an empty value.
XXX I still have no idea why this "fixes" the problem. I can't seem to
XXX create a test case that exposes this problem.
|
|
tools listed in USE_TOOLS -- some of them are required by the pkgsrc
infrastructure in variable assignment statements that look like:
VARIABLE!= ${AWK} ...
These tools are actually *required* by pkgsrc to be installed on the
system before it can even work (bootstrap situation). For these tools,
only override the "TOOL" name representing the tool if we're really
using the pkgsrc version of the tool.
We accomplish this by adding a new :pkgsrc modifier that is appended
to these tools listed in USE_TOOLS. We also list these tools in
bsd.prefs.mk so that all packages pick them up fairly early on.
|
|
was empty.
XXX I have no idea why this fixes the problem.
|
|
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
|
|
run-time dependency (DEPENDS) on a tool is to append a ":run" modifier
to the tool name, e.g.,
USE_TOOLS+= perl:run
Tools without modifiers or with an explicit ":build" modifier will
cause build dependencies (BUILD_DEPENDS) on those tools to be added.
This makes the notation a bit more compact.
|
|
PKGSRC_USE_TOOLS go away. There is now only a single USE_TOOLS variable
that specifies all of the tools we need to build/run the package.
|
|
any IMAKE_TOOLS in that case as well.
|
|
|
|
|
|
|
|
|
|
command that can be embedded into packages. Calling a bare "ldconfig"
will still call the one in the tools directory, which always does the
right thing.
|
|
|
|
|
|
(e.g. graphics/netpbm) use native bash if available.
|
|
lang/perl5 to perl-5.8.6nb4. Modify packages that referred to
lang/perl58 to point to lang/perl5 instead.
|
|
|
|
|
|
|
|
OpenBSD release, so check for the right location.
|
|
in tools/defaults.mk where they can be more widely used.
|
|
the perl interpreter.
|
|
dependencies on archivers/bzip2 and textproc/groff when they are
available in the base system.
|
|
used by pkgtools/xpkgwedge.
|
|
are automatically undefined after the loop exits.
|
|
shell builtins, e.g. echo, false, test, true, since those tools don't
have a full path.
|
|
"env" tool.
|
|
Also, some configure scripts use "ENV" to represent the path to the
"env" tool, which is probably bad since ENV has a special meaning to
/bin/sh. To workaround this, set ac_cv_path_ENV.
|
|
mktemp with USE_TOOLS+=mktemp in the samba packages.
|
|
x11-clients.buildlink3.mk. Packages that need bdftopcf should say:
USE_TOOLS+= bdftopcf
|
|
to see if _USE_TOOLS contains "perl", not USE_TOOLS.
|
|
This makes "make fetch-list" in "pkgsrc/meta-pkgs/kde3" work again.
|
|
USE_TOOLS and any of "autoconf", "autoconf213", "automake" or
"automake14". Also, we don't need to call the auto* tools via
${ACLOCAL}, ${AUTOCONF}, etc., since the tools framework takes care
to symlink the correct tool to the correct name, so we can just use
aclocal, autoconf, etc.
|
|
|
|
|
|
-- the checks for grep and egrep are broken because when passed GREP
and EGREP in the environment, the script causes GREP and EGREP to be
set to empty strings, which causes GNU configure scripts to hang or
break. Pass the real paths to grep and egrep through using ac_cv_path_GREP
and ac_cv_path_EGREP as well to avoid the brokenness. This fixes the
build of textproc/gsed.
|
|
that they require flex instead of any old lex.
|
|
|
|
for INSTALL by itself during the configure stage. This fixes problems
with GNU configure scripts using the wrong value of INSTALL.
|
|
USE_GNU_TOOLS -> USE_TOOLS
awk -> gawk
m4 -> gm4
make -> gmake
sed -> gsed
yacc -> bison
|
|
would always be built with gmake on Linux.
|
|
don't want to depend on perl, e.g. devel/cvs. Provide values for
TOOLS_PERL5 and PERL5 even if the package doesn't ask for the perl
tool.
|
|
mk/tools/replace.mk.
|
|
one name.
|
|
|
|
paths for the tools that the package uses through the shell environment.
We do this since these paths may be hardcoded into package scripts,
and if they're not pre-specified, then they'll be searched for in the
PATH, which would find the ones in ${TOOLS_DIR}.
The variable names that GNU configure scripts expect are named in
_TOOLS_VARNAME_GNU.* for the various tools.
|
|
|
|
|
|
avoids making autoconf required by every package in pkgsrc.
|
