| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
-- 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.
|
|
perl5/module.mk into tools/perl.mk so that the substitution occurs for
all packages that use perl.
|
|
tree.
|
|
to use. This fixes packages that want automake-1.4, but autoconf-2.50.
|
|
${WRKSRC}. Just directly create the msgfmt wrapper in the proper
target. Also, note that the msgfmt handling should eventually migrate
to the tools framework so that build dependencies and binary paths are
correct.
|
|
the extra bits required by packages that use imake/xmkmf. This
consolidates most of the replacement tools handling into replace.mk.
|
|
the extra bits required by packages that use perl. This causes
PKGSRC_USE_TOOLS+=perl to work properly.
|
|
iterating over each dependency in the list.
|
|
Plan:
(1) Change USE_PERL5=build into USE_TOOLS+=perl.
(2) Change all other USE_PERL5 into including perl5/buildlink3.mk.
Possibly, for packages that don't actually build anything with perl,
but merely require it for the perl interpreter, we can instead do:
USE_TOOLS+= perl
TOOLS_DEPMETHOD.perl= DEPENDS
but this is more verbose than simply including the perl5/buildlink3.mk
file.
Move the PERL5_REQD computation into a lang/perl5/version.mk file,
and only do the USE_PERL5 logic in bsd.pkg.use.mk if we're not using
the new tools framework. This consolidates all of the perl-handling
into two places -- lang/perl5 and mk/tools/perl.mk.
|
|
and is still strong enough for pkgsrc use.
|
|
Since replace.mk has its own loop to add dependencies, we can remove
the one from perl.mk.
|
|
to note that we need the perl binary and the associated PERL5 and
TOOLS_PERL5 variable definitions.
|
|
TOOLS_CMD.* variables for the -2.13 variants. Otherwise, they're
empty, which causes errors for packages that use ${AUTOCONF}.
|
|
meaning.
|
|
specify that imake is used by the package, while the latter triggers
the special do-configure process.
|
|
the implication that the system yacc(1) is not good enough anyway.
|
|
which can take multiple values -- "pax" or "gtar". The default value
of EXTRACT_USING is "pax", which more closely matches reality since
before, we were using bootstrap "tar" for ${GTAR} and it was actually
pax-as-tar. Also, stop pretending pax-as-tar from the bootstrap kit
or on NetBSD is GNU tar. Lastly, in bsd.pkg.extract.mk, note whether
we need "pax" or "gtar" depending on what we need to extract the
distfiles.
|
|
|
|
"bison" and "bison-yacc". bison is just a symlink to the real bison,
but "bison-yacc" provides a "yacc" in ${TOOLS_DIR} that does "bison
-y". This allows the tools framework to provide everything that a
package might look for when asking for "bison" and avoids relying on
the bison being available in the PATH.
|
|
creating it in case ${MKDIR} can't handle that situation.
|
|
is already properly constructed to call the one in ${TOOLS_DIR}, which
symlinks to the correct make tools. From rillig@ in private mail.
|
|
From schwarz@ in private mail.
|
|
|
|
gzip.
|
|
Ditto for mailx. Lastly, /usr/bsd/zcat isn't gzcat (doesn't understand
gzipped files), so don't use it as a gzcat replacement. Changes from
Georg Schwarz in private email.
|
|
pick up the xpkgwedge imake config files.
|
|
"gtar". Force the gtar in the tools directory to be a wrapper script
so that we invoke the (possibly) pax-as-tar as "tar".
|
|
|
|
when a symlink is created.
|
|
a proper BUILD_DEPENDS or DEPENDS list.
|
|
as needing both (no impact since they're both satisfied by the tar
binary installed by the bootstrap kit). There's some funniness in
the extraction code where we check for pax or GNU tar that needs to
be resolved. Remove the TAR=${GTAR} hack since it's no longer needed
after these changes.
XXX Later, a sweep needs to be made to see where we actually need GTAR
XXX and where we only need TAR, probably triggered by whether we call it
XXX with the "z" option or not. Packages that need GTAR should explicitly
XXX add USE_TOOLS+=gtar to the package Makefile.
|
|
with TAR vs. GTAR. This fixes pkg_install not being created with a
tar command.
|
|
other files without making assumptions about the location of the top of
the pkgsrc tree. This fixes problems with running "make bulk-cache"
in /usr/pkgsrc (PR pkg/30288).
|
|
|
|
|
|
|
