summaryrefslogtreecommitdiff
path: root/mk
AgeCommit message (Collapse)AuthorFilesLines
2004-02-10Turn PERL5_REQD into a list of values, the highest of which will be usedjlam1-17/+38
to choose the correct Perl dependency.
2004-02-10Give a better pseudo CC_VERSION for the SunPro C compiler.jlam1-2/+2
2004-02-09Apparently, GCC isn't the only compiler that tries to be clever by checkingjlam2-6/+12
with what path it was invoked. Copy the driver script trick from gcc.mk into mipspro.mk and sunpro.mk.
2004-02-09Update comment to reflect reality.jlam1-2/+2
2004-02-09Limit xargs to 256 args when passing args to ls for the package sizejlam1-2/+2
computation. The motivation for this is that kdelibs3 was overflowing ls through xargs.
2004-02-09Reorder some lines so that a default definition for some variables isjlam1-13/+14
present in global context.
2004-02-09Darwin's special GCC also uses -dylib_file and -dylib_install_name injlam1-5/+10
similar ways to -install_name, and all need the subsequent argument to be protected from /path/shlib -> -L/path -lshlib transformations.
2004-02-09Don't generate wrapper scripts if we can't find the wrappee.jlam2-49/+55
2004-02-09Also turn shlibtool into a shell script instead of a symlink. Thisjlam1-3/+8
duplicates the change made in rev. 1.1368 for libtool.
2004-02-09We need the full path to the libtool that needs to be invoked when wejlam3-6/+23
use LIBTOOL_OVERRIDE. In the buildlink[23] case, that is supposed to be the one in ${BUILDLINK_DIR}. Create new private variables _LIBTOOL and _SHLIBTOOL to hold these paths.
2004-02-09Don't have recursive variable definitions.jlam2-6/+6
2004-02-09Use TOOLS_SHELL since we're creating the shell script at override-toolsjlam1-2/+2
time.
2004-02-08print date and time in UTC.grant1-3/+5
2004-02-08It's not PKGSHLIBTOOL anymore but PKG_SHLIBTOOL.seb1-2/+2
2004-02-08include the total number of binary pkgs created in the report. fixgrant1-6/+17
some HTML nits.
2004-02-08Use ${PKG_LIBTOOL} to refer to the full path to the real libtool.jlam1-3/+3
2004-02-08Make those scripts executable.jlam1-1/+2
2004-02-08Use a two-line "exec" shell script instead of a symlink to the real GCC.jlam1-2/+4
This should fix problems with not finding "cc1" or other GCC subprograms.
2004-02-08* Let CC/CXX/CPP/FC always point to the compiler used in the actualjlam8-111/+70
building of software. For packages that use either buildlink2 or buildlink3, this would be the wrapper script in ${BUILDLINK_DIR}. * Garbage-collect _BLNK_WRAP_SETENV.* as those are not needed after the above changes. Configure and make processes will automatically find the right compilers in the PATH. * PKGLIBTOOL and PKGSHLIBTOOL are no longer needed since LIBTOOL and SHLIBTOOL point to the correct libtools regardless of any USE_BUILDLINK[23] definitions.
2004-02-07Introduce EMACS_TYPE to determine which emacs version should be installed,uebayasi1-1/+7
and emacs lisp packages should be built for. Users need to set the version you like in /etc/mk.conf explicitly. The default is emacs21 (editors/emacs, GNU Emacs 21.x). This will deprecate EMACS_VERSION_DEFAULT defined in emacs.mk and USE_XEMACS used in places.
2004-02-07Symlink the compiler into ${WRKDIR} so that there's a consistent path tojlam5-61/+121
the compiler and that it's behind .tools/bin and .buildlink/bin, regardless of whether or not we're using gcc3-c or not, or whether it's been installed yet in the process of satisfying dependencies, etc.
2004-02-07Don't pass PREPEND_PATH via MAKEFLAGS as that overrides whatever valuejlam1-9/+10
that we're trying to compute for PREPEND_PATH. Instead, pass it through the environment.
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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-07 12:47:08 +0000