Date: Fri, 22 Apr 2011 19:03:33 +0000 (UTC) From: Florent Thoumie <flz@FreeBSD.org> To: src-committers@freebsd.org, svn-src-projects@freebsd.org Subject: svn commit: r220956 - in projects/portbuild: . conf errorlogs scripts Message-ID: <201104221903.p3MJ3XDF054432@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: flz Date: Fri Apr 22 19:03:33 2011 New Revision: 220956 URL: http://svn.freebsd.org/changeset/base/220956 Log: Import portbuild from pcvs. Discussed with: portmgr (linimon, pav, self) Added: projects/portbuild/ projects/portbuild/conf/ projects/portbuild/conf/README.dotunnel projects/portbuild/conf/client.conf projects/portbuild/conf/common.conf projects/portbuild/conf/make.conf projects/portbuild/conf/server.conf projects/portbuild/errorlogs/ projects/portbuild/errorlogs/index.shtml projects/portbuild/scripts/ projects/portbuild/scripts/allgohans (contents, props changed) projects/portbuild/scripts/allgohans.safe (contents, props changed) projects/portbuild/scripts/bothlogs (contents, props changed) projects/portbuild/scripts/build (contents, props changed) projects/portbuild/scripts/buildenv projects/portbuild/scripts/buildfailure (contents, props changed) projects/portbuild/scripts/buildproxy (contents, props changed) projects/portbuild/scripts/buildproxy-client (contents, props changed) projects/portbuild/scripts/buildscript (contents, props changed) projects/portbuild/scripts/buildsuccess (contents, props changed) projects/portbuild/scripts/checkmachines (contents, props changed) projects/portbuild/scripts/checkmachines.sh (contents, props changed) projects/portbuild/scripts/chopindex (contents, props changed) projects/portbuild/scripts/claim-chroot (contents, props changed) projects/portbuild/scripts/clean-chroot (contents, props changed) projects/portbuild/scripts/cleanup-chroots (contents, props changed) projects/portbuild/scripts/client-metrics (contents, props changed) projects/portbuild/scripts/comparelogs (contents, props changed) projects/portbuild/scripts/cpdistfiles (contents, props changed) projects/portbuild/scripts/cppackages (contents, props changed) projects/portbuild/scripts/do-cleanup-chroots (contents, props changed) projects/portbuild/scripts/docppackages (contents, props changed) projects/portbuild/scripts/dodistfiles (contents, props changed) projects/portbuild/scripts/dologs (contents, props changed) projects/portbuild/scripts/dopackages (contents, props changed) projects/portbuild/scripts/dopackages.wrapper (contents, props changed) projects/portbuild/scripts/dopackages2 (contents, props changed) projects/portbuild/scripts/dopackagestats (contents, props changed) projects/portbuild/scripts/dosetupnode (contents, props changed) projects/portbuild/scripts/flushsquid (contents, props changed) projects/portbuild/scripts/keeprestr (contents, props changed) projects/portbuild/scripts/makeduds (contents, props changed) projects/portbuild/scripts/makeindex (contents, props changed) projects/portbuild/scripts/makerestr (contents, props changed) projects/portbuild/scripts/makeworld (contents, props changed) projects/portbuild/scripts/mkbindist (contents, props changed) projects/portbuild/scripts/nukesquid (contents, props changed) projects/portbuild/scripts/packagebuild (contents, props changed) projects/portbuild/scripts/pdispatch (contents, props changed) projects/portbuild/scripts/pnohang.c projects/portbuild/scripts/pollmachine (contents, props changed) projects/portbuild/scripts/portbuild (contents, props changed) projects/portbuild/scripts/processfail (contents, props changed) projects/portbuild/scripts/processlogs (contents, props changed) projects/portbuild/scripts/processlogs2 (contents, props changed) projects/portbuild/scripts/processonelog (contents, props changed) projects/portbuild/scripts/prunebad projects/portbuild/scripts/prunefailure (contents, props changed) projects/portbuild/scripts/prunepkgs (contents, props changed) projects/portbuild/scripts/ptimeout.c projects/portbuild/scripts/releasemachine (contents, props changed) projects/portbuild/scripts/reportload (contents, props changed) projects/portbuild/scripts/reportload.sh (contents, props changed) projects/portbuild/scripts/retcodes projects/portbuild/scripts/setupnode (contents, props changed) projects/portbuild/scripts/showrunning (contents, props changed) projects/portbuild/scripts/stats (contents, props changed) projects/portbuild/scripts/straslivy.py (contents, props changed) projects/portbuild/scripts/updatesnap (contents, props changed) projects/portbuild/scripts/updatesnap.ports (contents, props changed) projects/portbuild/scripts/zbackup (contents, props changed) projects/portbuild/scripts/zclient (contents, props changed) projects/portbuild/scripts/zexpire Added: projects/portbuild/conf/README.dotunnel ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/portbuild/conf/README.dotunnel Fri Apr 22 19:03:33 2011 (r220956) @@ -0,0 +1,32 @@ +Various package build nodes require us to set up TCP tunnels to talk +to them. (Some systems don't pass certain ports; some systems have +firewalls; some systems have multiple nodes on one IP address.) + +These have always been hardcoded in crontab lines of the form "while true; +do <hardcoded-tunnel-stuff>; done". Other than the magic hardcoding, +there's a problem with this. When the tunnel command exits, such as if +the host suddenly becoming unreachable, it doesn't send mail -- instead +it just accumulates a huge file in /var/spool/clientmqueue which never +gets sent. To add insult to injury, /var is on the root partition on +pointyhat. + +To cure these problems, we now have + + /var/portbuild/conf/<arch>/dotunnel.XXX + +where XXX corresponds to one line in the old crontab. Each script sets +up one tunnel, sends mail to the user(s) in + + /var/portbuild/<arch>/portbuild.conf + +once the command exits, and then sleeps. + +Why not put it in /var/portbuild/<arch> you ask? That directory is +propogated to all nodes for that arch. This would be a security leak. +The intention is that none of the dotunnel files will be checked into +CVS. + +Final note: each script figures out which arch it is for by fiddling +with its $0, so invoke it with its full pathname. + +mcl Added: projects/portbuild/conf/client.conf ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/portbuild/conf/client.conf Fri Apr 22 19:03:33 2011 (r220956) @@ -0,0 +1,41 @@ +# +# client-side definitions (used in /var/portbuild/scripts/portbuild) +# +# $FreeBSD: ports/Tools/portbuild/conf/client.conf,v 1.4 2011/01/23 02:34:58 linimon Exp $ +# + +# +# items to be customized per each package build master +# + +# for nodes where disconnected=0, the NFS host they should mount ports/ +# and src/ from +CLIENT_NFS_MASTER=pointyhat.FreeBSD.org + +# fallback for distfiles (see make.conf in bindist-*.tar) +CLIENT_BACKUP_FTP_SITE=pointyhat.FreeBSD.org + +# where completed packages get uploaded +CLIENT_UPLOAD_HOST=pointyhat.FreeBSD.org + +# +# items that will most likely be common to all package build masters +# + +CLIENT_DISTDIR=/tmp/distfiles +# XXX renaming this from PACKAGES +CLIENT_PACKAGES_LOCATION=/tmp/packages +CLIENT_SRCBASE=/usr/src +CLIENT_WRKDIRPREFIX=/work + +# wait 2 hours before killing build with no output +CLIENT_BUILD_TIMEOUT=7200 +CLIENT_FTP_TIMEOUT=900 +CLIENT_HTTP_TIMEOUT=900 + +# to prevent runaway processes -- 400 meg file size limit, 2 hours CPU limit +CLIENT_ULIMIT_F=819200 +CLIENT_ULIMIT_T=7200 + +# debugging definitions +CLIENT_MALLOC_OPTIONS=AJ Added: projects/portbuild/conf/common.conf ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/portbuild/conf/common.conf Fri Apr 22 19:03:33 2011 (r220956) @@ -0,0 +1,21 @@ +# +# package building configuration file containing things that are common +# both to the server-side (pointyhat instance) and the client side +# (individual build clients). +# +# original author: linimon +# +# $FreeBSD: ports/Tools/portbuild/conf/common.conf,v 1.1 2010/12/01 02:35:20 linimon Exp $ +# + +# +# top-level package building things. These will probably be common +# to all package build masters. +# + +LOCALBASE=/usr/local +PKGSUFFIX=.tbz + +ARCHS_REQUIRING_AOUT_COMPAT="i386" +ARCHS_REQUIRING_LINPROCFS="amd64 i386" +ARCHS_SUPPORTING_COMPAT_IA32="amd64 i386 ia64" Added: projects/portbuild/conf/make.conf ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/portbuild/conf/make.conf Fri Apr 22 19:03:33 2011 (r220956) @@ -0,0 +1,16 @@ +# DON'T SET PORT VARIABLES UNCONDITIONALLY - THEY NEED TO BE +# OVERRIDABLE BY THE SCRIPTS +USA_RESIDENT?=YES + +# +MASTER_SITE_BACKUP= \ + ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/ +MASTER_SITE_OVERRIDE?= ${MASTER_SITE_BACKUP} +MASTER_SITE_LOCAL= \ + ftp://ftp-master.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/%SUBDIR%/ + +NO_PROFILE=true +MAKE_KERBEROS5= yes +SENDMAIL_CF= freefall.cf +BOOT_PXELDR_PROBE_KEYBOARD= true +ENABLE_SUID_K5SU=yes Added: projects/portbuild/conf/server.conf ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/portbuild/conf/server.conf Fri Apr 22 19:03:33 2011 (r220956) @@ -0,0 +1,105 @@ +# +# package building configuration file (server-side). Specific to each +# pointyhat instance. +# +# note: readable by both Python and /bin/sh files. HOWEVER, there is no +# code yet to do the {}-style shell expansions in the Python scripts. +# Beware! +# +# original author: linimon +# +# $FreeBSD: ports/Tools/portbuild/conf/server.conf,v 1.7 2011/04/22 18:32:13 linimon Exp $ +# + +# +# top-level package building things +# + +SUPPORTED_ARCHS="amd64 i386 ia64 powerpc sparc64" + +SRC_BRANCHES="7 8 9" +SRC_BRANCHES_PATTERN="^[0-9]*" +SRC_BRANCH_7_TAG=RELENG_7_3 +SRC_BRANCH_8_TAG=RELENG_8_1 +SRC_BRANCH_9_TAG=. + +DEFAULT_LINUX_OSRELEASE="2.6.16" + +# +# directory management definitions +# + +ZFS_VOLUME=a +ZFS_MOUNTPOINT=/a + +SNAP_DIRECTORY=snap +SNAP_PORTS_DIRECTORY=${SNAP_DIRECTORY}/ports-head +SNAP_SRC_DIRECTORY_PREFIX=${SNAP_DIRECTORY}/src- + +SUPFILE_DIRECTORY=/home/portmgr/sup +PORTS_MASTER_SUPFILE=${SUPFILE_DIRECTORY}/ports-master-supfile +SRC_MASTER_SUPFILE=${SUPFILE_DIRECTORY}/src-master-supfile +PORTS_SUPFILE=${SUPFILE_DIRECTORY}/ports-supfile +SRC_SUPFILE=${SUPFILE_DIRECTORY}/src-supfile + +WORLDDIR=${ZFS_MOUNTPOINT}/chroot/ + +# XXX TODO (note: Python script, so avoid {}) +#zbackup a/nfs a/local a/portbuild/* /dumpster +#zexpire a/nfs a/local a/portbuild/* a/snap/* + +# +# buildproxy definitions (note: Python script, so avoid {}) +# + +BUILDPROXY_SOCKET_FILE=/tmp/.build + +# +# pdispatch definitions +# + +# reflect hardwiring in 'buildscript' phase 1 and also 'processonelog' and +# 'processlogs2'. You probably do not want to change this! +PDISPATCH_HDRLENGTH=6 + +# number of lines of log to email +PDISPATCH_LOGLENGTH=1000 + +# wait 100 hours maximum +PDISPATCH_TIMEOUT=360000 + +# +# qmanager definitions (note: Python script, so avoid {}) +# + +QMANAGER_PATH=/var/portbuild/evil/qmanager +QMANAGER_DATABASE_FILE=qdb.sl3 +QMANAGER_SOCKET_FILE=/tmp/.qmgr + +QMANAGER_PRIORITY_PACKAGES="openoffice kde-3" + +# maximum number of times to build an individual job +QMANAGER_MAX_JOB_ATTEMPTS=5 + +# attempt to limit the amount time (and email) on botched runs +QMANAGER_RUNAWAY_PERCENTAGE=0.75 +QMANAGER_RUNAWAY_THRESHOLD=100 + +# +# upload definitions (see 'cpdistfiles') +# + +UPLOAD_DIRECTORY="w/ports/distfiles/" +UPLOAD_TARGET="ftp-master.FreeBSD.org" +UPLOAD_USER="portmgr" + +# +# user-visible things +# + +MASTER_URL="pointyhat.FreeBSD.org" + +# +# www definitions (see processfail) +# +WWW_DIRECTORY=/usr/local/www/data/ Added: projects/portbuild/errorlogs/index.shtml ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/portbuild/errorlogs/index.shtml Fri Apr 22 19:03:33 2011 (r220956) @@ -0,0 +1,984 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<html> +<head> +<meta name="generator" content="HTML Tidy, see www.w3.org"> +<title>FreeBSD Package building logs and errors</title> +</head> +<body> +<h1><font color="#990000">FreeBSD Package building logs and errors</font></h1> + +<p>FreeBSD maintains a build farm (the "pointyhat cluster") that is used +to build all packages across all supported architectures and major releases. +This page contains the build logs and errors for all the ports built by +the cluster. See the <a href="#notes">notes</a> for additional information, +or the <a href="#errorlist">types of package errors detected</a>.</p> + +<h4><font color="#990000"> +Port cross-reference summaries +</font></h4> +<p>These live on +<a href="http://portsmon.FreeBSD.org/index.html">portsmon.FreeBSD.org</a>.</p>; +<dl> + +<dd><img alt="*" src="/errorlogs/images/blue-ball.gif"> Build errors +<a href="http://portsmon.FreeBSD.org/portserrs.py">by portname</a>; +<a href="http://portsmon.FreeBSD.org/portscrossref.py">by portname vs. build environment</a>; +<a href="http://portsmon.FreeBSD.org/portserrcounts.py">by error type vs. build environment</a></dd> +<dd><img alt="*" src="/errorlogs/images/blue-ball.gif"> Problem Reports +for <a href="http://portsmon.FreeBSD.org/portsprsbyexplanation.py?explanation=existing">existing ports</a>; +for <a href="http://portsmon.FreeBSD.org/portsprsbyexplanation.py?explanation=new">new ports</a>; +for <a href="http://portsmon.FreeBSD.org/portsprsbyexplanation.py?explanation=framework">the ports framework</a>; +for <a href="http://portsmon.FreeBSD.org/portsprsbyexplanation.py?explanation=repocopy">repocopies requested</a>; +for <a href="http://portsmon.FreeBSD.org/portsprsbyexplanation.py?explanation=unknown">unknown</a></dd>; +<dd><img alt="*" src="/errorlogs/images/blue-ball.gif"> Build Errors and +Problem Reports +<a href="http://portsmon.FreeBSD.org/portsconcordance.py">by portname</a>; +<a href="http://portsmon.FreeBSD.org/portsconcordanceformaintainer.py">for one maintainer</a>; +<a href="http://portsmon.FreeBSD.org/portsconcordanceforbroken.py">for broken ports</a>; +<a href="http://portsmon.FreeBSD.org/portsconcordancefordeprecated.py">for deprecated ports</a>; +<a href="http://portsmon.FreeBSD.org/portsconcordanceforforbidden.py">for forbidden ports</a></dd> +<dd><img alt="*" src="/errorlogs/images/blue-ball.gif"> Everything about +<a href="http://portsmon.FreeBSD.org/portoverview.py">one port</a></dd> +<dd><img alt="*" src="/errorlogs/images/blue-ball.gif"> The +<a href="http://portsmon.FreeBSD.org/index.html">complete list of all reports</a></dd> +</dl> + +<h4><font color="#990000"> +New build failures +</font></h4> +<p>Check here to find the most recent error log from your port.</p> + +<!--#config timefmt="%F %R" --> + +<dl> +<dd> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build +failures on 7.x-stable: +<a href="amd64-7-failure.html">amd64</a> +<a href="i386-7-failure.html">i386</a> +<a href="ia64-7-failure.html">ia64</a> +<a href="sparc64-7-failure.html">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build +failures on 8.x-stable: +<a href="amd64-8-failure.html">amd64</a> +<a href="i386-8-failure.html">i386</a> +<a href="ia64-8-failure.html">ia64</a> +<a href="powerpc-8-failure.html">powerpc</a> +<a href="sparc64-8-failure.html">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build +failures on 9.x-current: +<a href="amd64-9-failure.html">amd64</a> +<a href="i386-9-failure.html">i386</a> +<a href="ia64-9-failure.html">ia64</a> +<a href="powerpc-9-failure.html">powerpc</a> +<a href="sparc64-9-failure.html">sparc64</a> +<br> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build failures on 7.x-stable with experimental port patches: +<a href="amd64-7-exp-failure.html">amd64</a> +<a href="i386-7-exp-failure.html">i386</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build failures on 8.x-stable with experimental port patches: +<a href="amd64-8-exp-failure.html">amd64</a> +<a href="i386-8-exp-failure.html">i386</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> New build failures on 9.x-current with experimental port patches: +<a href="amd64-9-exp-failure.html">amd64</a> +<a href="i386-9-exp-failure.html">i386</a> +<br> +</dd> +</dl> + +<h4><font color="#990000"> +Error logs +</font></h4> + +<dl> +<dd> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run +on 7.x-stable: +<a href="amd64-7-full/">amd64</a> +<a href="i386-7-full/">i386</a> +<a href="ia64-7-full/">ia64</a> +<a href="sparc64-7-full/">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run +on 7.x-stable: +<a href="amd64-7-latest/">amd64</a> +<a href="i386-7-latest/">i386</a> +<a href="ia64-7-latest/">ia64</a> +<a href="sparc64-7-latest/">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run +on 8.x-stable: +<a href="amd64-8-full/">amd64</a> +<a href="i386-8-full/">i386</a> +<a href="ia64-8-full/">ia64</a> +<a href="powerpc-8-full/">powerpc</a> +<a href="sparc64-8-full/">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run +on 8.x-stable: +<a href="amd64-8-latest/">amd64</a> +<a href="i386-8-latest/">i386</a> +<a href="ia64-8-latest/">ia64</a> +<a href="powerpc-8-latest/">powerpc</a> +<a href="sparc64-8-latest/">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run +on 9.x-current: +<a href="amd64-9-full/">amd64</a> +<a href="i386-9-full/">i386</a> +<a href="ia64-9-full/">ia64</a> +<a href="powerpc-9-full/">powerpc</a> +<a href="sparc64-9-full/">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run +on 9.x-current: +<a href="amd64-9-latest/">amd64</a> +<a href="i386-9-latest/">i386</a> +<a href="ia64-9-latest/">ia64</a> +<a href="powerpc-9-latest/">powerpc</a> +<a href="sparc64-9-latest/">sparc64</a> +<br> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run +on 7.x-stable with experimental port patches: +<a href="amd64-7-exp-full/">amd64</a> +<a href="i386-7-exp-full/">i386</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run +on 7.x-stable with experimental port patches: +<a href="amd64-7-exp-latest/">amd64</a> +<a href="i386-7-exp-latest/">i386</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run +on 8.x-stable with experimental port patches: +<a href="amd64-8-exp-full/">amd64</a> +<a href="i386-8-exp-full/">i386</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run +on 8.x-stable with experimental port patches: +<a href="amd64-8-exp-latest/">amd64</a> +<a href="i386-8-exp-latest/">i386</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Previous run +on 9.x-current with experimental port patches: +<a href="amd64-9-exp-full/">amd64</a> +<a href="i386-9-exp-full/">i386</a> +<br> +<img alt="*" src="/errorlogs/images/yellow-ball.gif"> Current run +on 9.x-current with experimental port patches: +<a href="amd64-9-exp-latest/">amd64</a> +<a href="i386-9-exp-latest/">i386</a> +</dd> +</dl> + +<h4><font color="#990000"> +Build logs (errors and otherwise) +</font></h4> + +<dl> +<dd> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run +on 7.x-stable: +<a href="amd64-7-full-logs">amd64</a> +<a href="i386-7-full-logs">i386</a> +<a href="ia64-7-full-logs">ia64</a> +<a href="sparc64-7-full-logs">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on +7.x-stable: +<a href="amd64-7-latest-logs">amd64</a> +<a href="i386-7-latest-logs">i386</a> +<a href="ia64-7-latest-logs">ia64</a> +<a href="sparc64-7-latest-logs">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run +on 8.x-stable: +<a href="amd64-8-full-logs">amd64</a> +<a href="i386-8-full-logs">i386</a> +<a href="ia64-8-full-logs">ia64</a> +<a href="powerpc-8-full-logs">powerpc</a> +<a href="sparc64-8-full-logs">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on +8.x-stable: +<a href="amd64-8-latest-logs">amd64</a> +<a href="i386-8-latest-logs">i386</a> +<a href="ia64-8-latest-logs">ia64</a> +<a href="powerpc-8-latest-logs">powerpc</a> +<a href="sparc64-8-latest-logs">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run +on 9.x-current: +<a href="amd64-9-full-logs">amd64</a> +<a href="i386-9-full-logs">i386</a> +<a href="ia64-9-full-logs">ia64</a> +<a href="powerpc-9-full-logs">powerpc</a> +<a href="sparc64-9-full-logs">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on +9.x-current: +<a href="amd64-9-latest-logs">amd64</a> +<a href="i386-9-latest-logs">i386</a> +<a href="ia64-9-latest-logs">ia64</a> +<a href="powerpc-9-latest-logs">powerpc</a> +<a href="sparc64-9-latest-logs">sparc64</a> +<br> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run +on 7.x-stable with experimental port patches: +<a href="amd64-7-exp-full-logs">amd64</a> +<a href="i386-7-exp-full-logs">i386</a> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on +7.x-stable with experimental port patches: +<a href="amd64-7-exp-latest-logs">amd64</a> +<a href="i386-7-exp-latest-logs">i386</a> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run +on 8.x-stable with experimental port patches: +<a href="amd64-8-exp-full-logs">amd64</a> +<a href="i386-8-exp-full-logs">i386</a> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on +8.x-stable with experimental port patches: +<a href="amd64-8-exp-latest-logs">amd64</a> +<a href="i386-8-exp-latest-logs">i386</a> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Previous run +on 9.x-current with experimental port patches: +<a href="amd64-9-exp-full-logs">amd64</a> +<a href="i386-9-exp-full-logs">i386</a> +<br> +<img alt="*" src="/errorlogs/images/orange-ball.gif">Current run on +9.x-current with experimental port patches: +<a href="amd64-9-exp-latest-logs">amd64</a> +<a href="i386-9-exp-latest-logs">i386</a> +<br> +</dd> +</dl> + +<h4><font color="#990000"> +Packages +</font></h4> + +<dl> +<dd> +<img alt="*" src="/errorlogs/images/purple-ball.gif"> Packages from +latest run on 6-stable: +<a href="amd64-6-packages-latest/">amd64</a> +<a href="i386-6-packages-latest/">i386</a> +<a href="sparc64-6-packages-latest/">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/purple-ball.gif"> Packages from +latest run on 7-stable: +<a href="amd64-7-packages-latest/">amd64</a> +<a href="i386-7-packages-latest/">i386</a> +<a href="ia64-7-packages-latest/">ia64</a> +<a href="sparc64-7-packages-latest/">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/purple-ball.gif"> Packages from +latest run on 8-stable: +<a href="amd64-8-packages-latest/">amd64</a> +<a href="i386-8-packages-latest/">i386</a> +<a href="ia64-8-packages-latest/">ia64</a> +<a href="powerpc-8-packages-latest/">powerpc</a> +<a href="sparc64-8-packages-latest/">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/purple-ball.gif"> Packages from +latest run on 9-current: +<a href="amd64-9-packages-latest/">amd64</a> +<a href="i386-9-packages-latest/">i386</a> +<a href="ia64-9-packages-latest/">ia64</a> +<a href="powerpc-9-packages-latest/">powerpc</a> +<a href="sparc64-9-packages-latest/">sparc64</a> +<br> +<br> +<img alt="*" src="/errorlogs/images/purple-ball.gif"> Package +<a href="packagestats.html">building statistics</a> (current state of all package builds) +</dd> +</dl> + +<h4><font color="#990000"> +Archive +</font></h4> + +<dl> +<dd><img alt="*" src="/errorlogs/images/red-ball.gif"> All error +logs: +<a href="amd64-errorlogs/">amd64</a> +<a href="i386-errorlogs/">i386</a> +<a href="ia64-errorlogs/">ia64</a> +<a href="powerpc-errorlogs/">powerpc</a> +<a href="sparc64-errorlogs/">sparc64</a> +<br> +<img alt="*" src="/errorlogs/images/red-ball.gif"> All portbuild +logs: +<a href="amd64-buildlogs/">amd64</a> +<a href="i386-buildlogs/">i386</a> +<a href="ia64-buildlogs/">ia64</a> +<a href="powerpc-buildlogs/">powerpc</a> +<a href="sparc64-buildlogs/">sparc64</a> +</dd> +</dl> + +<a name="notes"> +<h3><font color="#990000">Additional information</font></h3> +</a> + +<p>All of the "Current run" links are possibly in progress and may be +partial, so keep that in mind if there appear to be some missing.</p> + +<p>None of the ports marked <tt>IS_INTERACTIVE</tt> or +<tt>NO_PACKAGE</tt> are built any more -- if you have ports that +fall into those categories, assume their packages or distfiles will +never show up in ftp sites or CDROMs. <tt>RESTRICTED</tt> packages +are built and deleted (using "<tt>make +clean-restricted-list</tt>"). <tt>NO_CDROM</tt> packages are built +but deleted (using "<tt>make clean-cdrom-list</tt>") before being +put on a CDROM.</p> + +<p>See also the <a href="errors.html">types of errors detected</a>.</p> + +<p>Notes on the building process:</p> + +<ul> +<li><em>Every</em> port is built in its own chroot environment +<!-- MCL 20090823 broken links +( +<a href="i386-7-bindist.tar">tarball for 7.x-stable</a> +|<a href="i386-8-bindist.tar">tarball for 8.x-stable</a> +|<a href="i386-9-bindist.tar">tarball for 9.x-current</a> +) +--> +, starting with an +empty <tt>/usr/local</tt> and <tt>/usr/X11R6</tt>. <a name= +"pkgadd">The dependencies are installed as packages</a> just before +the build. You can see the list of dependencies on the third line +of the log -- the "foo.tgz bar.tgz" stuff are the dependencies. To +make sure that these actually work, <tt>DEPENDS_TARGET</tt> is set +to "/usr/bin/true"; if you see "/usr/bin/true is up to date" or +some such, that means there is something wrong with the dependency +lines or the packages this port is depending on.</li> + +<li>The build is done on a shared (read-only) <tt>/usr/ports</tt> +with <a href= +"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-wrkdir.html">; +<tt>WRKDIRPREFIX</tt></a> set to <tt>/work</tt>. If your +<tt>WRKSRC</tt> looks funny, that's probably why.</li> + +<li><tt>MASTER_SITE_OVERRIDE</tt> is pointing to pointyhat's distfile +dir, and <tt>MASTER_SITE_BACKUP</tt> is pointing to +ftp-master.freebsd.org or a local mirror. <!--Wrong! +The one on pointyhat is empty when the build starts, +and every successful build will copy distfiles to there. This means +that if there are a few ports that share the same distfile, only +the first one will have to go to the original master site (provided +the second build starts after the first one ends). After the entire +build process, the distfiles are copied over to ftp.freebsd.org. +This means if your port built successfully once, you will never see +a "can't fetch distfile" error again.--> +Please pay attention to +<a href="http://people.freebsd.org/~ehaupt/distilator/">; +Emanuel Haupt's distfile checker</a> +for that.</li> + +<li>The ports are built on machines that are mostly running + 9-CURRENT, with some 8.x-STABLE machines. If your port depends on + the result of uname(3) or sysctl to determine the running version of + FreeBSD, change it to use uname(1) instead (the builds use a dummy + uname(1) that reports the target version of FreeBSD), or change it to + use the value of the OSVERSION variable that can be passed in from + the port makefile. </li> </ul> + +<a name="errorlist"></a> +<h2><font color="990000">Types of package errors detected</font></h2> + +<p>Here is the <b>alphabetical list of current errors</b> +detected by the AI script. Note that this is all just a rough guess -- +it is merely for your aid.</p> + +<p>Key: +<dl> + <dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif">The most common + errors.</dt> + <dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif">Some less common + errors.</dt> + <dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif">Transient + errors. These may not be your fault.</dt> +</dl> +</p> + +<p> +<dl> +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"arch">arch</a></dt> + +<dd>The port does not build on a particular architecture, due to +assembler or linker errors. In some easy cases this is due to +not picking up the various <tt>ARCH</tt> configuration variables +in the Makefile; you'll see this via, e.g., a Sparc <tt>make</tt> +failing while looking for an i386 subdirectory. For the 64-bit +architectures, a common problem is the assumption many programmers +make that pointers may be cast to and from 32-bit ints. In other cases +the problems run much deeper, in which case <tt>ONLY_FOR_ARCHS</tt> +may be needed.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"autoconf">autoconf</a></dt> + +<dd>Your port depends on <tt>autoconf</tt>, but the <tt>Makefile</tt> +either doesn't have <tt>USE_AUTOCONF</tt>, or does not use +<tt>USE_AUTOCONF_VER</tt> correctly.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"autoheader">autoheader</a></dt> + +<dd>Your port depends on <tt>autoheader</tt>, but the <tt>Makefile</tt> +cannot find it; set <tt>USE_AUTOHEADER</tt>.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"automake">automake</a></dt> + +<dd>Your port depends on <tt>automake</tt>, but the <tt>Makefile</tt> +either doesn't have <tt>USE_AUTOMAKE</tt>, or does not use +<tt>USE_AUTOMAKE_VER</tt> correctly.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"badc++">bad C++ code</a></dt> + +<dd>There is a compiler error which is caused by something specific +to C++.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"cc">compiler error</a></dt> + +<dd>There is a C compiler error which is caused by something other +than e.g. "new compiler error".</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"categories">CATEGORIES</a></dt> + +<dd>The <tt>CATEGORIES</tt> line in <tt>Makefile</tt> includes an +invalid category.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"checksum">checksum</a></dt> + +<dd>The checksum of one or more of the files is incorrect.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"clang">clang</a></dt> + +<dd>Your code does not run with the the experimental <tt>clang</tt> compiler. See +(TBA) +for further information.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"clang-bug">clang bug</a></dt> + +<dd>You have tickled a bug in <tt>clang</tt> itself. See +(TBA) +for further information.</dd> + +<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a name= +"cluster">cluster</a></dt> + +<dd>There was some kind of transient error on the build cluster. It is not your +fault.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"compat6x">compat6x</a></dt> + +<dd>This port needs to depend on a port <tt>misc/compat6x</tt>.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"configure">configure error</a></dt> + +<dd>The port's <tt>configure</tt> script produced some kind of +error. +(Note: using <tt>clang</tt> as the ports compiler can also trigger this message.)</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"coredump">coredump</a></dt> + +<dd>Some process in the build chain dropped core. While your port may indeed +be faulty, the process that dropped core should also be fixed.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"cpusetsize">cpusetsize</a></dt> + +<dd>This port needs to catch up with the <tt>cpusetsize</tt> sysctl change in 9-CURRENT.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"dependobj">depend object</a></dt> + +<dd>The port is trying to reinstall a dependency that already +exists. This is usually caused by the first field of a +<tt>*_DEPENDS</tt> line (the <tt>obj</tt> of +<tt>obj:dir[:target]</tt>) indicating a file that is not installed +by the dependency, causing it to be rebuilt even though it has +already been <a href="#pkgadd">added from a package</a>.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"dependpkg">depend package</a></dt> + +<dd>There was an error during <a href="#pkgadd">adding dependencies +from packages</a>. It is the fault of the package being added, not +this port.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"dirent">dirent</a></dt> + +<dd>The port has not caught up with the change to <code>scandir(3)</code> +as committed in FreeBSD version 800501.</dd> + +<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a name= +"df">disk full</a></dt> + +<dd>The disk filled up on the build system. It is not your +fault.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"display">DISPLAY</a></dt> + +<dd>This port requires an X display to build. There is nothing you +can do about it unless you can somehow make it not require an X +connection.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"distinfo">distinfo update</a></dt> + +<dd>The contents of <tt>distinfo</tt> does not match the list of +distfiles or patchfiles.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"fetch">fetch</a></dt> + +<dd>One or more of the files could not be fetched.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"fetch-timeout">fetch timeout</a></dt> + +<dd>Your fetch process was killed because it took too long. (More +accurately, it did not produce any output for a long time.) Please +put sites with better connectivity near the beginning of +<tt>MASTER_SITES</tt>.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"forbidden">forbidden</a></dt> + +<dd>Someone has marked this port as "forbidden", almost always due +to security concerns. See the logfile for more information.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"gcc-bug">gcc bug</a></dt> + +<dd>You have tickled a bug in gcc itself. See the +<a href="http://www.gnu.org/software/gcc/bugs.html">GNU bug report documentation</a> +for further information.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"gcc4">gcc4</a></dt> + +<dd>Your code does not run with the latest gcc version +See <a href="http://wiki.freebsd.org/gcc4">the wiki page</a> +for further information.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"gmake">gmake</a></dt> + +<dd>Your code does not run with the latest, incompatible, gmake version +(3.82.)</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"install">install error</a></dt> + +<dd>There was an error during installation.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"libdepends">LIB_DEPENDS</a></dt> + +<dd>The <tt>LIB_DEPENDS</tt> line specifies a library name +incorrectly. This often happens when a port is upgraded and the +shared library version number changes.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"ld">linker error</a></dt> + +<dd>There is a linker error which is caused by something other than +those flagged elsewhere. +(Note: using <tt>clang</tt> as the ports compiler can also trigger this message.)</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"makefile">makefile</a></dt> + +<dd>There is an error in the <tt>Makefile</tt>, possibly in the default +targets.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"manpage">manpage</a></dt> + +<dd>There is a manpage listed in a <tt>MAN?</tt> macro that does not +exist or is not installed in the right place.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"header">missing header</a></dt> + +<dd>There is a missing header file. This is usually caused by +either (1) a missing dependency, or (2) specifying an incorrect +location with <tt>-I</tt> in the compiler command line.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"mtree">mtree</a></dt> + +<dd>The port leaves <tt>${PREFIX}</tt> in a state that is not +consistent with the mtree definition after <tt>pkg_delete</tt>. This +usually means some files are missing from <tt>PLIST</tt>. It could +also mean that your installation scripts create files or +directories not properly deleted by the deinstallation scripts. +Another possibility is that your port is deleting some directories +it is not supposed to, or incorrectly modifying some directory's +permission.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"nested_declaration">nested_declaration</a></dt> + +<dd>There is a nested declaration in the source code.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"newgcc">new compiler error</a></dt> + +<dd>The newest version of gcc in the base does not like the source code. This is +usually due to stricter C++ type checking or changes in register +allocation policy.</dd> + +<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a name= +"nfs">NFS</a></dt> + +<dd>There was either a temporary NFS error on the build system +(which is not your fault), or the <tt>WRKSRC</tt> is invalid +(which is your fault).</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"patch">patch</a></dt> + +<dd>One or more of the patches failed.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"perl">perl</a></dt> + +<dd><tt>perl</tt> is no longer included by default in the base +system, but your port's configuration process depends on it. While +this change helps avoid having a stale version of <tt>perl</tt> +in the base system, it also means that many ports now need to include +<tt>USE_PERL5</tt>.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"plist">PLIST</a></dt> + +<dd>There is a missing item in the <tt>PLIST</tt>. Note that this is +often caused by an earlier error that went undetected. In this case, +you should fix the error and also the build process so it will fail +upon an error instead of continuing, since that makes debugging +that much harder.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"process">process failed</a></dt> + +<dd>The <tt>make</tt> process terminated unexpectedly, due to +something like a signal 11 or bus error.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"runaway">runaway process</a></dt> + +<dd>Your <tt>make package</tt> process was killed because it took +too long. (More accurately, it did not produce any output for a long +time.) It is probably because there is a process spinning in an infinite +loop. Please check the log to determine the exact cause of the +problem.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"segfault">segfault</a></dt> + +<dd>Some process in the build chain got a segmentation fault.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"sem_wait">sem_wait</a></dt> + +<dd>This port needs to catch up with semaphore changes in 9-CURRENT.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"termios">termios</a></dt> + +<dd>This port needs to catch up with the <tt>termios.h</tt> changes in src.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"threads">threads</a></dt> + +<dd>There is a linker error which is caused by failing to find one of +the thread libraries.</dd> + +<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a name= +"truncated_distfile">truncated_distfile</a></dt> + +<dd>A package node encountered an error during pkg_add. It is not your +fault. Linimon is trying to figure out this problem.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"utmp_x">utmp_x</a></dt> + +<dd>This port needs to catch up with the <tt>utmp_x.h</tt> changes in src.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"wrkdir">WRKDIR</a><a name="WRKDIR"></a></dt> + +<dd>The port is attempting to change something outside +<tt>${WRKDIR}</tt>. See <a href= +"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-wrkdir.html">handbook</a>; +for details.</dd> + +<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a name= +"unknown">??? (unknown)</a></dt> + +<dd>The automated script cannot even guess what is wrong with your +port. <tt>portmgr</tt> tries to keep the <tt>processonelog</tt> script +reasonably efficient while covering as many errors as possible, but many +errors are not common enough to try to catch.</dd> +</dl> + +<p>Here is an <b>alphabetical list of obsolete errors</b></a> +that used to be detected by the AI script, but are now uncommon enough to +be skipped:</p> + +<dl> +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"alignment">alignment</a></dt> + +<dd>You've managed to confuse the assembler with a misaligned +structure.</dd> + +<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a name= +"apxs">apxs</a></dt> + *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201104221903.p3MJ3XDF054432>