Lines Matching full:build

47 is used to build ports on a cluster of machines, or on a single machine
75 to build as parameters.
81 to build, or a filename that contains pkgpaths (one per line).
103 In order to build on a cluster, the ports tree itself should be identical
126 .Pa ${DISTDIR}/build-stats .
182 Build packages for given architecture, selecting relevant hosts from the
197 Explicitly prime the heuristics module with a previous build log,
198 so that packages that take a long time to build will happen earlier.
200 .Pa %f/build-stats/%a
203 Don't clean port working directories after build.
209 Clean port working directory and log before each build.
258 to build a small subset of packages which would pull in the kitchen sink
292 Don't fetch distfiles/don't build packages that are not allowed for ftp.
294 Don't fetch or build anything.
329 will never clean any work directory after build.
331 Disable reading/saving of default build stats under
332 .Pa ${DISTDIR}/build-stats/${ARCH} .
368 Clamp number of stats (per individual pkgpath) used for computing build
397 Do not build any package but fetch everything, disregarding
409 Those are separate from the build jobs, since they don't consume cpu, and they
483 Build everything below that wrkdir threshold with
489 is the sum, in KBytes, of ports that will be allowed to build in memory.
533 Requires previous build information to be effective.
537 ports known to build under that duration are deemed to be small, so
540 It will go straight to build and package instead.
563 This will also add them to the list of things to build.
568 Delete unneeded installed packages during the build.
609 Those ports' build may be broken by a
629 can be made that will allow the port build to finish.
646 Build ports below the memory threshold under a memory
654 is the sum, in KBytes, of ports allowed to build there.
694 Concretely, use to run a partial bulk build after some library change.
702 Random build order.
704 Useful to try to find missing build dependencies.
712 This will also maintain a rolling log of build sizes under
713 .Pa %f/build-stats/%a-size .
723 Can be used to run a bulk-build on a machine with installed packages,
724 but might break a bit, since some packages only build on a clean machine
737 and coming back up, build errors, or builds not progressing.
741 figures out in which order to build things on the fly, and constantly
748 www/mozilla-firefox(build) [9452] 41% unchanged for 92 seconds
778 build statistics are available).
824 number of packages to build, where dependencies are not yet resolved.
854 There are also provisions for a feedback-directed build, where information from
855 previous builds can be used to try to build long-running jobs first.
880 as decided randomly at the start of each build.
913 and several build slots.
917 and lots of build slots.
937 is used as the build and log user, and
960 is used to build stuff locally or distantly (can be per-host), using:
976 ${DISTDIR}/build-stats.
1001 .Ar show-prepare-results , patch , build
1012 This lockfile is filled with such info as the build start time or the host,
1020 At the end of a successful build, these lockfiles are removed.
1027 and the name of the next task in the build pipeline (with todo=<nothing>
1030 .Ar depends prepare fetch patch configure build fake package clean .
1037 another build.
1039 This eases manual repairs: if a package does not build, the user can look
1068 .Ss BUILD CYCLES
1080 That information is only wiped out when a given build finishes successfully.
1084 will try to restart that build on the same host, which can be handy if you
1164 Add new pkgpath to list of paths that should not be cleaned after build
1177 ready to build, to build later, along with current dependencies if
1244 the fetch engine knows precisely which files are needed by the build
1289 also records rolling build statistics under
1290 .Pa ${DISTDIR}/build-stats/${ARCH} ,
1307 .Pa ${DISTDIR}/build-stats/${ARCH}-size
1319 .Pa ${DISTDIR}/build-stats/${ARCH}-dependencies ,
1322 This list will be automatically reused when restarting a build:
1356 .It Pa build.log
1357 Actual build log.
1358 Each line summarizes build of a single pkgpath, as:
1360 where time is the actual build time in seconds, host is the machine name
1362 and a ! is appended in case the build didn't succeed.
1364 The detailed timing info gives a run-down of the build, with clean, fetch,
1365 prepare, patch (actually extract+patch), configure, build, fake, package, clean
1367 Note that the actual build time starts at
1392 A long log file generated at the end of build that yields any information
1394 .Sq to build
1402 Build engine log.
1415 affinity mismatch: path considered for build, but not the right host,
1422 error in build or fetch.
1430 job to build pkgpath started.
1431 Also records the host used for the build.
1433 kde mismatch, no build until host has been cleaned up.
1444 pkgpath to build / distfile to download.
1467 The engine is no longer run after each package build event
1475 Lists of equivalent pkgpaths for the build, when default flavors and default subpackages have been …
1524 doesn't run its engine at each new package build,
1553 Size of work directory at the end of each build, built only with
1566 A summary file generated at end of build that lists packages not built
1574 in case of build cycles, stopping at the first loop.
1686 this is an actual bug: the engine said it can build, there are cores available,
1689 can't start a new build job.
1711 performs best with lots of paths to build.
1712 When just used to build a few ports, there's a high risk of starvation
1747 On heterogeneous networks, calibration of build info and choice of speed
1749 Using distinct speed factors on a build log that comes from a single
1750 machine works fine, but using the build info coming from several machines
1775 make sure all the hosts build ports the same way.