summaryrefslogtreecommitdiff
path: root/mk/tools/tools.NetBSD.mk
AgeCommit message (Collapse)AuthorFilesLines
2010-11-10use -current's builtin xzcatdrochner1-1/+4
2009-09-04Use unzip from base if it exists.joerg1-1/+4
2008-05-22Add ftp as tool. On NetBSD and DragonFly, this will use the systemjoerg1-1/+2
version of tnftp, otherwise it will use net/tnftp. Require ftp as bootstrap dependency when the package has files to fetch. The dependency is currently unconditional and FETCH_CMD is set to TOOLS_PATH.ftp by default.
2007-09-30Fixed indentation.rillig1-3/+3
2007-08-20Add readelf as tool, for only only the BSDs get it.joerg1-2/+7
2007-08-16A number of packages implicitly assume that ar runs the right ranlib,joerg1-1/+3
so override it as well for DESTDIR.
2007-08-15Create ranlib override for cross-compilation as libtool doesn'tjoerg1-1/+4
use the target version. If we ever want to create archives for the native platform, NATIVE_RANLIB similiar to NATIVE_CC should be introduced.
2007-08-02Add core of the infrastructure support for cross-compilation.joerg1-1/+22
- USE_CROSS_COMPILATION activates it, CROSS_DESTDIR specifies root of the target filesystem - derive _CROSS_DESTDIR from CROSS_DESTDIR or MAKEOBJDIR - buildlink3.mk prefixes the files to symlink with _CROSS_DESTDIR - compiler/gcc.mk knows about the target prefix (e.g. i386--netbsdelf) - PKG_DBDIR is prefixed with _CROSS_DESTDIR - package-install and bin-install are not called with su - install and strip are redirected to the tool version - links for the target specific ar, as, ld, nm, objdump, ranlib and strip are added - compiler wrapper detect if linking is requested or not - special command sinks for CPP and CC/CXX add the cross-compile magic: - modify include dirs to get the target /usr/include - modify linker dirs and runpath to use target /usr/lib at link time, but keep correct rpath entries Supported-by: Google SoC 2007 Basic tests by he@ on Sparc. Review from jlam@.
2007-06-19Add bzip2 as tool. All platforms that had code to deal with bzcatjoerg1-1/+2
also get bzip2, the rest falls back to archivers/bzip2. OK jlam.
2007-06-19Add ident as tool and use /usr/bin/ident on those platforms I know tojoerg1-1/+2
have it. Fallback to devel/rcs otherwise. Commited during freeze as it is a dependency of pbulk.
2006-07-05Teach the tools framework about the following new tools:jlam1-1/+3
itools, intltool, diff3, sdiff, msgmerge * Adding USE_TOOLS+=itools to a package Makefile will cause the tool-directory versions of imake, makedepend, mkdirhier and xmkmf to point to the ones from the devel/nbitools package. This change will remove the need for nbitools/buildlink3.mk, which currently does a bit of hackery to force the "right" imake tools to be used by packages that need it. * Adding USE_TOOLS+=intltool to a package Makefile will cause the local versions of intltool-* inside ${WRKSRC} to be replaced by copies from the textproc/intltool package. If "intltool" is not specified as a tool, then we create "broken" intltool-* tools in the tools directory to help highlight hidden dependencies on the intltool package. In addition, modify the tools framework so that if "perl" is not specified as a tool, then we create a "broken" perl tool in the tools directory for the same reason as for "intltool". These two changes together will remove the need for intltools/buildlink3.mk and should also catch all cases where the sources' intltools may have been silently used because perl was found on the system. * Adding USE_TOOLS+=diff3, USE_TOOLS+=sdiff, or USE_TOOLS+=msgmerge to a package Makefile will cause the corresponding tool to be pulled into the tools directory. These are convenience tools to help simplify dependencies for some packages.
2006-06-14Teach the tools framework about "openssl".jlam1-1/+2
2006-05-21Add back "gsoelim" as a NetBSD tool since it supports "-I directory".jlam1-2/+3
Mark this as merely "GNUish" in the comment so that we know it's not really GNU soelim.
2006-05-21NetBSD actually doesn't have GNU soelim, but rather BSD soelim.jlam1-2/+1
2006-05-21Teach the tools framework about "groff" as a tool.jlam1-1/+2
2006-04-13Rename msgfmt.mk to gettext.mk. The rest of the gettext tool handlingjlam1-1/+4
will be moved here from replace.mk shortly.
2006-04-13Overhaul the way packages can ask for "msgfmt". If a package needsjlam1-1/+4
msgfmt, then it should set the following in the package Makefile: USE_TOOLS+= msgfmt To deal with message files that use the "msgid_plural" statement, which isn't supported in NetBSD<=3.x and also in gettext<=0.10.35, we determine if the built-in "msgfmt" is sufficiently new enough to understand "msgid_plural". If it isn't, then we use the msgfmt.sh script to transform the msgid_plural statements to an equivalent construct that's understood by older msgfmt tools. The msgfmt.sh script is a straightforward translation of the original perl script msgfmt.pl script by Julio M. Merino Vidal into shell and awk, which are more lightweight dependencies than perl. We remove the USE_MSGFMT_PLURALS bits in gettext-lib/builtin.mk as they are made obsolete by the new code in mk/tools/msgfmt.mk. BUILD_USE_MSGFMT is still supported but will be removed in a separate commit.
2006-03-06Teach the tools framework how to supply a pkgsrc version of install-infojlam1-1/+4
if a native one isn't available. We ensure that the "install-info" tool in the tools directory is a no-op since the real info file registration is handled by the INSTALL/DEINSTALL script in pkgsrc/mk/pkginstall/install-info.
2006-03-05* Teach the tools framework how to supply the pkgsrc version ofjlam1-1/+4
makeinfo if no native makeinfo executable exists. Honor TEXINFO_REQD when determining whether the native makeinfo can be used. * Remove USE_MAKEINFO and replace it with USE_TOOLS+=makeinfo. * Get rid of all the "split" argument deduction for makeinfo since the PLIST module already handles varying numbers of split info files correctly. NOTE: Platforms that have "makeinfo" in the base system should check that the makeinfo entries of pkgsrc/mk/tools.${OPSYS}.mk are correct.
2006-01-09Teach the tools framework about the ``ksh'' tool, provided by thejlam1-1/+2
shells/pdksh package if it doesn't exist on the base system.
2006-01-08Teach the tools framework about "gsoelim", which is the soelim tool fromjlam1-1/+2
a groff distribution.
2005-11-08Add "soelim", also part of groff if replacement is needed.tv1-1/+2
2005-11-04Teach the tools framework about "sleep" which can be provided by thejlam1-1/+2
sysutils/coreutils package.
2005-10-12Teach the tools framework about ``printf'', which can be replaced by thejlam1-1/+2
printf in sysutils/coreutils.
2005-09-20Teach the tools framework about "byacc", which is a Berkeley-compatiblejlam1-1/+2
YACC. This should be used by packages that require NOT using bison (maybe because bison can't handle the .y file) but still need a yacc.
2005-06-24Teach the tools framework about csh, and replace with tcsh if necessary.jlam1-1/+2
2005-06-23Note locations for native diff tools.jlam1-1/+2
2005-06-03Teach the tools framework about mktemp. Replace explicit tests forjlam1-1/+2
mktemp with USE_TOOLS+=mktemp in the samba packages.
2005-05-26Teach the tools framework about nroff.jlam1-1/+2
2005-05-23Teach the tools framework about "flex" so that packages can specifyjlam1-1/+2
that they require flex instead of any old lex.
2005-05-16Change the EXTRACT_USING_PAX defined/undefined option into a EXTRACT_USINGjlam1-2/+1
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.
2005-05-14Consider ${TAR} differently from ${GTAR}. Currently, mark pkgsrc downjlam1-6/+7
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.
2005-05-10Split out ldconfig handling from the USE_TOOLS processing in replace.mk.jlam1-3/+1
This makes more sense since there is never going to be a pkgsrc replacement for ldconfig. We now always create an ldconfig tool in ${TOOLS_DIR} that either calls the system-supplied one if it exists, or is a no-op.
2005-05-10Remove conditional expression from tools.*.mk files. Strip handling hasjlam1-3/+2
moved to its own file, and we only need to define TOOLS_PLATFORM.strip if it actually exists on the system.
2005-05-04Teach the new tools framework about ${STRIP}, which is used in somejlam1-1/+3
packages to strip installed executables. If INSTALL_UNSTRIPPED == "yes", then we create a "strip" wrapper in ${TOOLS_DIR} that just calls ${TRUE} by considering ${TRUE} the system-supplied strip command.
2005-05-03Teach the new tools framework about INSTALL and set the appropriatejlam1-1/+2
default value for each platform. Currently, the replacement tools comes from sysutils/coreutils, but where there is no native BSD install program, bootstrap-pkgsrc should probably be made to provide an install shell script as an alternative, and mk/tools/bootstrap.mk should be amended accordingly. Also remove one use of ${TYPE} in pkgsrc (bsd.pkg.mk) under the new tools framework.
2005-05-03Teach the new tools framework about MAIL_CMD. We use mail/nail as ajlam1-1/+2
"mail" replacement in case TOOLS_PLATFORM.mail is empty.
2005-05-02Teach the new tools framework about ldconfig. This must be provided byjlam1-1/+6
tools.${OPSYS}.mk, so at the very worst, it must be set to "true".
2005-05-02Teach the new tools framework about USE_TOOLS+=bzcat.jlam1-1/+4
2005-04-28Note the "[" is natively available everywhere (usually as a shell builtin).jlam1-1/+2
2005-04-27Rename PLATFORM_TOOLS.* to TOOLS_PLATFORM.* to bring the variable namesjlam1-59/+59
under the same namespace as the other parts of the new tools framework.
2005-04-27The BSDs all have lex, tbl, and yacc in the base system.jlam1-1/+8
2005-04-27Initial stab at creating lists of system-supplied tools for each platform.jlam1-0/+60
These were culled from pkgsrc/mk/${OPSYS}.mk. These files should only be listing utilities that aren't installed by pkgsrc.