summaryrefslogtreecommitdiff
path: root/mk
AgeCommit message (Collapse)AuthorFilesLines
2004-02-24Add en_CA locale, used by development version of atk (currently 1.5.x).jmmv9-9/+45
2004-02-24Add 'mi' locale, used by development version of nautilus (what will be 2.6.x).jmmv9-9/+45
2004-02-23sjg recommends escaping the bare left curly brace in the make variablejlam1-2/+2
modifer expression.
2004-02-23Back out previous because that brace is not supposed to be there.jlam1-2/+2
2004-02-23add a missing } to the end of the line; fixes PR/24525.dogcow1-2/+2
2004-02-22Allow setting CCACHE_DIR in the environment or in /etc/mk.conf.jlam1-1/+5
2004-02-21Use BUILD_ENV instead of just {CONFIGURE,MAKE}_ENV to pass CCACHE_HASHCCjlam1-3/+2
to ccache. This now correctly passes CCACHE_HASHCC to ccache if the package has a custom do-build target that invokes ${CC} directly.
2004-02-21Rename PATH_ENV to BUILD_ENV, which better expresses what it's for.jlam1-9/+12
BUILD_ENV is used to set the environment for the sub-make processes that are invoked for each phase after and including buildlink.
2004-02-21Pass LDFLAGS (minus any libraries) to the compiler when creating thejlam2-4/+5
trivial libtool archive.
2004-02-20Symlink the libtool-1.4.m4 file into any directory in which there's ajlam2-2/+886
configure script under ${WRKSRC}. The symlink is called "libtool.m4", which is the name expected by the autoconf tools. The symlinking is only done if ${AUTOCONF_REQD} == 2.13 and USE_LIBTOOL is defined. This allows autoconf-2.13, autoreconf-2.13 and aclocal-2.13 to use the older libtool.m4 file when regenerating files. This is okay, because we later override the generated libtool file anyway. This fixes problems when libtool-1.5.x is installed and a package tries to invoke autoconf-2.13 programs at pre-configure time, e.g., gnome-games, xpuyopuyo, faad2, libwww, etc. These packages no longer need to be worked around by bumping AUTOCONF_REQD to 2.50.
2004-02-20Provide a much more complete list of version number patterns <= 2.95.3.jlam1-2/+2
2004-02-20If for some reason, _GCC_REQD doesn't match any of the version patternjlam1-1/+4
lists, then just assume that we need gcc3. The rest of the code in the file assumes that we either need gcc2 or gcc3, so this provides a fall-through, default value.
2004-02-19According to the documentation on version numbering of shared libraries at:jlam1-7/+1
http://fink.sourceforge.net/doc/porting/shared.php It's okay to link against a name like "libqt.2.3.0.dylib" using "-lqt.2.3.0", which means we never need to do anything more than just strip the trailing ".dylib" from shared library names when converting from a full path to "-L... -l...". This should fix PR 24402.
2004-02-19Use the mipspro-ucode bits if we're using the mipspro-ucode compiler.jlam1-1/+30
2004-02-19Resolve ${LOCALBASE} to its phyiscal path and mangle it back intojlam1-15/+25
${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
2004-02-19Don't spew files in the package directory if the BUILDLINK_DEPENDS.<pkg>jlam1-4/+9
uses {} to list several "or" dependencies.
2004-02-18Output a more informative/desriptive error than:jlam1-1/+8
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.
2004-02-18Remove some checks for PREPEND_PATH as we don't need them.jlam3-10/+3
2004-02-18* Move pkgsrc/mk/compiler/bsd.compiler.mk to pkgsrc/mk/compiler.mk.jlam12-336/+266
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.
2004-02-18Initial support for the MIPSpro ucode compilers found on IRIX 5.3. Thejlam4-2/+74
ucode compilers only support building the "o32" ABI.
2004-02-18Allow overriding CC_VERSION_STRING and CC_VERSION.jlam2-6/+6
2004-02-18Typo in comment.jlam1-2/+2
2004-02-18Typo in comment.jlam1-2/+2
2004-02-17Require x11-links-0.23 for the correct set of links with XFree86-4.3.x.jlam2-4/+4
2004-02-17Fix the glob pattern to match >= dependencies correctly.jlam1-11/+8
2004-02-17Do "dependency reduction" where dependency lists of the form "foo>=0.2jlam1-2/+53
foo>=0.3 foo>=0.4" are collapsed into a single "foo>=0.4" dependency.
2004-02-17G/C the unused GNU_MISSING_OVERRIDE logic, as we don't need it anymorejlam1-14/+1
after the changes in revision 1.27 of tools.mk to hide the auto* tools between pre-configure and do-configure.
2004-02-17Move up the creation of the auto* stubs to just before the do-configurejlam1-3/+3
target. This still allows any autoconf/automake we execute at pre-configure time to find its own scripts, but forces the configure script find our stubs instead. This should prevent the need to constantly override the missing script using GNU_MISSING_OVERRIDE.
2004-02-17+less obfuscated errorsjlam1-1/+3
2004-02-16also ignore -pedantic, SunPro doesn't need to be told ;-)grant2-3/+8
2004-02-16Symlink any *.pc files into ${BUILDLINK_DIR} for dependencies and forcejlam1-2/+2
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.
2004-02-16Add some TODO items for me.jlam1-1/+7
2004-02-16Add RCS IDhubertf1-0/+2
2004-02-16Be less aggressive about overriding all of the functionality ofjlam1-4/+15
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.
2004-02-16Handle compressed info files in PLIST handling.seb1-4/+5
2004-02-16ignore -ansi, SunPro doesn't need to be told to support ANSI C.grant2-3/+8
2004-02-16Quote '+' in awk regexp related to PLIST and INFO_FILES.seb1-3/+3
As seen in devel/libg++ with its libg++.info file...
2004-02-16Move section that checks for PREFER_PKGSRC a little higher so that itjlam1-8/+8
actually has some effect.
2004-02-15ml locale goes after mk.jmmv9-27/+27
2004-02-15Whitespace nits.jlam1-3/+3
2004-02-15Aside from everything under ${PREFIX}/include, grab all *.h files forjlam1-2/+2
symlinking into ${BUILDLINK_DIR} for a more complete set of headers.
2004-02-15Create wrappers for the compilers for every language supported by thejlam5-25/+13
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.
2004-02-15avoid another long command line calling tar(1).grant1-2/+2
2004-02-15Set CONF_FILES_MODE from @CONF_FILES_MODE@.lukem1-1/+2
2004-02-14Use relative to ${WRKSRC} pathnames in do-gnu-missing-override targetseb1-6/+5
by cd'ing into it. Also symlink the missing script instead of copying it.
2004-02-14Make LIBTOOL_OVERRIDE more powerful by taking a list of shell globsjlam1-21/+22
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}.
2004-02-14Make CONFIG_{GUESS,SUB}_OVERRIDE slighly more powerful by allowing them tojlam1-11/+23
be lists of shell globs relative to ${WRKSRC}.
2004-02-14Change into ${WRKSRC} first so that shell globs expand properly.jlam1-6/+6
2004-02-14Some shells barf if the for loop list is empty, so avoid that.jlam1-3/+3
2004-02-14Default to overriding config.status after GNU configure has been run. Wejlam1-7/+20
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.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-24 03:01:53 +0000