summaryrefslogtreecommitdiff
path: root/mk
AgeCommit message (Collapse)AuthorFilesLines
2004-02-06I missed changing a defined(_NEED_GCC3) into a yes/no check.jlam1-2/+2
2004-02-06Whitespace nit.jlam1-2/+2
2004-02-06If we're passing through MAKEFLAGS variables whose values may containjlam2-9/+9
spaces, use the :Q modifier instead of double-quoting the value. This avoids breakage when executing the just-in-time su targets.
2004-02-06If we're passing through MAKEFLAGS variables whose values may containjlam4-13/+13
spaces, use the :Q modifier instead of double-quoting the value. This fixes breakage when executing the just-in-time su targetes.
2004-02-06Remove a debugging statement.jlam1-2/+1
2004-02-06Hiding the PATH from certain phases of the build only accidentally workedjlam9-28/+36
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.
2004-02-06Allow an empty USE_LANGUAGES setting to not break in show-shlib-type.jlam1-7/+7
If we're not compiling anything, we're likely not installing any shared libraries.
2004-02-06We only prepend a directory to the PATH if we haven't already done sojlam9-31/+81
(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.
2004-02-05extract OPSYS and OS_VERSION from pkgsrc and use them in the reportgrant1-3/+8
email subject.
2004-02-05show build start time in localtime, not seconds-since-epoch :)grant1-2/+6
2004-02-05Get the version string out of the MIPSpro compiler in the right way.jlam1-3/+4
2004-02-05Note that the variables (USE_LANGUAGES, GCC_REQD, PKGSRC_COMPILER) shouldjlam1-2/+3
be defined in or before the first inclusion of bsd.prefs.mk.
2004-02-05Back out bikeshed material added in rev. 1.1371hubertf1-2/+2
2004-02-05Remove a local change which crept in with the last update.sketch1-3/+1
2004-02-05Allow this to work with ccache by passing the full PATH through libtool.jlam2-2/+4
2004-02-05Touch up the grammar a bit in the last commit.jlam1-6/+9
2004-02-05Use the new work log format used by buildlink3. Lines beginning withjlam2-4/+10
"[*]" are the untransformed command lines, and the ones beginning with "<.>" are the ones that are actually executed.
2004-02-05Mention that some buildlink3 variables are not defined at all times.seb1-2/+8
Approved by jlam@.
2004-02-05Pass the PATH when executing ${CC} so that the compiler may be found whenjlam1-1/+2
CC is something like ccache or distcc that relies on finding the true compiler in the PATH.
2004-02-05Document PREFER_PKGSRC and default to "no".jlam1-1/+10
2004-02-05Make PREFER_PKGSRC just yes/no or a list of packages. This makes itjlam1-5/+3
simpler to understand.
2004-02-05Rename BUILDLINK_PREFER_PKGSRC to PREFER_PKGSRC so that we can use itsjlam1-5/+4
value outside of buildlink-related files.
2004-02-05Support a new global variable:jlam1-1/+11
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.
2004-02-05When a pkg is already found install, tell the user to 'make deinstall'hubertf1-2/+2
instead of running pkg_delete to be consistent with the other commands (which all use 'make ...').
2004-02-05GCC_REQD should be appended to, not set.jlam2-5/+5
2004-02-05Simpilfy the test for whether we're inside bsd.prefs.mk.jlam5-11/+11
2004-02-05Include bsd.compiler.mk inside both bsd.pkg.mk and bsd.prefs.mk and definejlam2-3/+15
a stack-like mechanism in bsd.prefs.mk to detect when a we're inside bsd.prefs.mk.
2004-02-05Allow bsd.compiler.mk to be included by both bsd.prefs.mk and bsd.pkg.mk.jlam6-226/+281
Any additions to DEPENDS/BUILD_DEPENDS or inclusions of buildlink[23].mk files are deferred till bsd.compiler.mk is included by bsd.pkg.mk. We allow bsd.compiler.mk to be included by bsd.prefs.mk solely for the purpose of setting CC_VERSION properly for use by package Makefiles. There is the surprising behaviour that CC_VERSION won't necessarily have the correct value at all times until after "make extract" has been completed (dependencies are installed before "make extract"), so package Makefile writers should keep that in mind. Just to note that this is _existing_ behaviour that's preserved by these changes.
2004-02-05Don't compute the CC_VERSION unless ${CC} exists.jlam3-3/+15
2004-02-05_CC is really meant to be evaluated from the value of CC _as found_ injlam1-4/+5
that particular location, so set it using :=
2004-02-05_GCC_PREFIX and _GCC_SUBPREFIX are expected to end in "/" if we're usingjlam1-3/+3
the pkgsrc gcc.
2004-02-05Reset the values of _GCC_PREFIX and _GCC_SUBPREFIX from the value ofjlam1-1/+5
_GCC_ARCHDIR, since _GCC_ARCHDIR is something that GCC actually tells us and can be relied upon to accurately give the installed location of GCC.
2004-02-05Fix an error that crept in between revisions 1.25 and 1.26 where some /'sjlam1-3/+3
were inadvertantly added when replacing the awk script with a sed script.
2004-02-04Missing a "jlam1-2/+2
2004-02-04case branches are separated by ;;jlam1-3/+3
2004-02-04Try to avoid "/" as the _GCC_SUBPREFIX.jlam1-2/+6
2004-02-04Make it more apparent where certain "not_found" values are being set forjlam1-3/+3
debugging purposes.
2004-02-04Make it more apparent where certain "not_found" values are set forjlam1-9/+9
debugging purposes.
2004-02-04Fix harmless for-loop-break bug.jlam1-2/+2
2004-02-04Instead of tedious validating every platform for full caching compliance,jlam2-26/+24
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.
2004-02-04Avoid a non-zero exit value in a != variable definition.jlam1-2/+2
2004-02-04Define _GCC_PKG unconditionally since its value is determined by anotherjlam1-2/+2
global variable, and so that we can reuse it in other places in gcc.mk.
2004-02-04Try to be smarter about detecting whether a cc in the PATH is actuallyjlam1-37/+40
GCC. If it's found under ${LOCALBASE}, then assume that it came from a package and proactively require at least that version of GCC so that the correct package dependencies are added.
2004-02-03Reorder checks when setting _GCC_SUBPREFIX so that we always search forjlam1-6/+9
the installed package first if _USE_PKGSRC_GCC is "yes".
2004-02-03Remove not_found checks now that we pre-filter them out when settingjlam1-3/+1
LDFLAGS.
2004-02-03Do previous in a different way to avoid make errors.jlam1-2/+3
2004-02-03Don't add to LDFLAGS if the directories are "not_found".jlam1-1/+3
2004-02-03":H", not ":T", is the correct make variable modifier to get everythingjlam1-2/+2
except the final component of a path.
2004-02-03Reorder sections a bit so that related sections are together.jlam1-49/+47
2004-02-03Whitespace nit.jlam1-2/+2
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-28 17:56:13 +0000