From owner-svn-src-projects@FreeBSD.ORG Tue Jun 21 14:31:37 2011 Return-Path: Delivered-To: svn-src-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A5F8106566B; Tue, 21 Jun 2011 14:31:37 +0000 (UTC) (envelope-from flz@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:4f8:fff6::2c]) by mx1.freebsd.org (Postfix) with ESMTP id 47C328FC14; Tue, 21 Jun 2011 14:31:37 +0000 (UTC) Received: from svn.freebsd.org (localhost [127.0.0.1]) by svn.freebsd.org (8.14.4/8.14.4) with ESMTP id p5LEVbhb004723; Tue, 21 Jun 2011 14:31:37 GMT (envelope-from flz@svn.freebsd.org) Received: (from flz@localhost) by svn.freebsd.org (8.14.4/8.14.4/Submit) id p5LEVbje004718; Tue, 21 Jun 2011 14:31:37 GMT (envelope-from flz@svn.freebsd.org) Message-Id: <201106211431.p5LEVbje004718@svn.freebsd.org> From: Florent Thoumie Date: Tue, 21 Jun 2011 14:31:37 +0000 (UTC) To: src-committers@freebsd.org, svn-src-projects@freebsd.org X-SVN-Group: projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Subject: svn commit: r223366 - in projects/portbuild: conf errorlogs scripts www www/js X-BeenThere: svn-src-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the src " projects" tree" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jun 2011 14:31:37 -0000 Author: flz Date: Tue Jun 21 14:31:36 2011 New Revision: 223366 URL: http://svn.freebsd.org/changeset/base/223366 Log: Cleanup www configuration and static files. - Add apache configuration. - Add static files. - Add js/sorttable.js to generate sortable tables and adjust processlogs. Added: projects/portbuild/conf/apache.conf projects/portbuild/errorlogs/index.html (contents, props changed) projects/portbuild/www/ projects/portbuild/www/favicon.ico (contents, props changed) projects/portbuild/www/index.html - copied unchanged from r222445, projects/portbuild/errorlogs/index.shtml projects/portbuild/www/js/ projects/portbuild/www/js/sorttable.js projects/portbuild/www/robots.txt Deleted: projects/portbuild/errorlogs/index.shtml Modified: projects/portbuild/scripts/processlogs Added: projects/portbuild/conf/apache.conf ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/portbuild/conf/apache.conf Tue Jun 21 14:31:36 2011 (r223366) @@ -0,0 +1,43 @@ +DocumentRoot "/var/portbuild/www" + +# filter magic to decompress bzip2 logs - pav@ +LoadModule ext_filter_module libexec/apache22/mod_ext_filter.so +LoadModule php5_module libexec/apache22/libphp5.so +ExtFilterDefine BUNZIP2 mode=output intype=application/x-bzip2 outtype=text/plain cmd=/usr/bin/bunzip2 + + + Order allow,deny + Allow from all + Options FollowSymLinks + AllowOverride None + #Redirect permanent /index.html http://pointyhat-west.isc.freebsd.org/errorlogs/ + + +Alias /errorlogs/ /var/portbuild/errorlogs/ + + + Order allow,deny + Allow from all + Options FollowSymLinks +# Added kk 030222 + Options +IncludesNoExec + AddHandler server-parsed .shtml + DirectoryIndex index.shtml index.html +# filter magic to decompress bzip2 logs - pav@ + Options +MultiViews + AddOutputFilterByType BUNZIP2 application/x-bzip2 + + +Alias /ganglia/ "/usr/local/www/ganglia/" + + + Order allow,deny + Allow from all + Options Indexes FollowSymlinks MultiViews + AllowOverride None + AddType text/html php + #AddType application/x-httpd-php .php + #AddType application/x-httpd-php-source .phps + addhandler php5-script .php + DirectoryIndex index.php + Added: projects/portbuild/errorlogs/index.html ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/portbuild/errorlogs/index.html Tue Jun 21 14:31:36 2011 (r223366) @@ -0,0 +1 @@ +link ../www/index.html \ No newline at end of file Modified: projects/portbuild/scripts/processlogs ============================================================================== --- projects/portbuild/scripts/processlogs Tue Jun 21 12:38:40 2011 (r223365) +++ projects/portbuild/scripts/processlogs Tue Jun 21 14:31:36 2011 (r223366) @@ -121,6 +121,7 @@ fi header() { echo "Package building errors" >$of + echo "" >>$of echo "

Package building errors

" >>$of echo "

View by " >>$of echo "[ port " >>$of @@ -141,7 +142,7 @@ header() { echo "\"Aff.\" is number of ports that depend on this one
" >> $of echo "\"[B]\" indicates port is marked BROKEN (Note: BROKEN ports are not frequently rebuilt so they may not be listed here)

" >> $of echo "

${n_logs} errors

" >> $of - echo "" >>$of + echo "

" >>$of echo "$1" >>$of fi } Added: projects/portbuild/www/favicon.ico ============================================================================== Binary file. No diff available. Copied: projects/portbuild/www/index.html (from r222445, projects/portbuild/errorlogs/index.shtml) ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/portbuild/www/index.html Tue Jun 21 14:31:36 2011 (r223366, copy of r222445, projects/portbuild/errorlogs/index.shtml) @@ -0,0 +1,984 @@ + + + + +FreeBSD Package building logs and errors + + +

FreeBSD Package building logs and errors

+ +

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 notes for additional information, +or the types of package errors detected.

+ +

+Port cross-reference summaries +

These live on +portsmon.FreeBSD.org.

+ +

Build errors +by portname; +by portname vs. build environment; +by error type vs. build environment

Problem Reports +for existing ports; +for new ports; +for the ports framework; +for repocopies requested; +for unknown

Build Errors and +Problem Reports +by portname; +for one maintainer; +for broken ports; +for deprecated ports; +for forbidden ports

Everything about +one port

The +complete list of all reports

+ + +

+New build failures +

Check here to find the most recent error log from your port.

+ + + +

New build +failures on 7.x-stable: +amd64 +i386 +ia64 +sparc64 +
+

New build +failures on 8.x-stable: +amd64 +i386 +ia64 +powerpc +sparc64 +
+

New build +failures on 9.x-current: +amd64 +i386 +ia64 +powerpc +sparc64 +
+
+

New build failures on 7.x-stable with experimental port patches: +amd64 +i386 +
+

New build failures on 8.x-stable with experimental port patches: +amd64 +i386 +
+

New build failures on 9.x-current with experimental port patches: +amd64 +i386 +
+

+ + +

+Error logs +

+ +

Previous run +on 7.x-stable: +amd64 +i386 +ia64 +sparc64 +
+

Current run +on 7.x-stable: +amd64 +i386 +ia64 +sparc64 +
+

Previous run +on 8.x-stable: +amd64 +i386 +ia64 +powerpc +sparc64 +
+

Current run +on 8.x-stable: +amd64 +i386 +ia64 +powerpc +sparc64 +
+

Previous run +on 9.x-current: +amd64 +i386 +ia64 +powerpc +sparc64 +
+

Current run +on 9.x-current: +amd64 +i386 +ia64 +powerpc +sparc64 +
+
+

Previous run +on 7.x-stable with experimental port patches: +amd64 +i386 +
+

Current run +on 7.x-stable with experimental port patches: +amd64 +i386 +
+

Previous run +on 8.x-stable with experimental port patches: +amd64 +i386 +
+

Current run +on 8.x-stable with experimental port patches: +amd64 +i386 +
+

Previous run +on 9.x-current with experimental port patches: +amd64 +i386 +
+

Current run +on 9.x-current with experimental port patches: +amd64 +i386 +

+ + +

+Build logs (errors and otherwise) +

+ +

Previous run +on 7.x-stable: +amd64 +i386 +ia64 +sparc64 +
+

Current run on +7.x-stable: +amd64 +i386 +ia64 +sparc64 +
+

Previous run +on 8.x-stable: +amd64 +i386 +ia64 +powerpc +sparc64 +
+

Current run on +8.x-stable: +amd64 +i386 +ia64 +powerpc +sparc64 +
+

Previous run +on 9.x-current: +amd64 +i386 +ia64 +powerpc +sparc64 +
+

Current run on +9.x-current: +amd64 +i386 +ia64 +powerpc +sparc64 +
+
+

Previous run +on 7.x-stable with experimental port patches: +amd64 +i386 +
+

Current run on +7.x-stable with experimental port patches: +amd64 +i386 +
+

Previous run +on 8.x-stable with experimental port patches: +amd64 +i386 +
+

Current run on +8.x-stable with experimental port patches: +amd64 +i386 +
+

Previous run +on 9.x-current with experimental port patches: +amd64 +i386 +
+

Current run on +9.x-current with experimental port patches: +amd64 +i386 +
+

+ + +

+Packages +

+ +

Packages from +latest run on 6-stable: +amd64 +i386 +sparc64 +
+

Packages from +latest run on 7-stable: +amd64 +i386 +ia64 +sparc64 +
+

Packages from +latest run on 8-stable: +amd64 +i386 +ia64 +powerpc +sparc64 +
+

Packages from +latest run on 9-current: +amd64 +i386 +ia64 +powerpc +sparc64 +
+
+

Package +building statistics (current state of all package builds) +

+ + +

+Archive +

+ +

All error +logs: +amd64 +i386 +ia64 +powerpc +sparc64 +
+

All portbuild +logs: +amd64 +i386 +ia64 +powerpc +sparc64 +

+ + + +

Additional information

+ + +

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.

+ +

None of the ports marked IS_INTERACTIVE or +NO_PACKAGE 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. RESTRICTED packages +are built and deleted (using "make +clean-restricted-list"). NO_CDROM packages are built +but deleted (using "make clean-cdrom-list") before being +put on a CDROM.

+ +

Types of package errors detected

+ +

Here is the alphabetical list of current errors +detected by the AI script. Note that this is all just a rough guess -- +it is merely for your aid.

+ +

Key: +

The most common + errors.
Some less common + errors.
Transient + errors. These may not be your fault.

+ +

arch: 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 ARCH configuration variables +in the Makefile; you'll see this via, e.g., a Sparc make +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 ONLY_FOR_ARCHS +may be needed.
autoconf: Your port depends on autoconf, but the Makefile +either doesn't have USE_AUTOCONF, or does not use +USE_AUTOCONF_VER correctly.
autoheader: Your port depends on autoheader, but the Makefile +cannot find it; set USE_AUTOHEADER.
automake: Your port depends on automake, but the Makefile +either doesn't have USE_AUTOMAKE, or does not use +USE_AUTOMAKE_VER correctly.
bad C++ code: There is a compiler error which is caused by something specific +to C++.
compiler error: There is a C compiler error which is caused by something other +than e.g. "new compiler error".
CATEGORIES: The CATEGORIES line in Makefile includes an +invalid category.
checksum: The checksum of one or more of the files is incorrect.
clang: Your code does not run with the the experimental clang compiler. See +(TBA) +for further information.
clang bug: You have tickled a bug in clang itself. See +(TBA) +for further information.
cluster: There was some kind of transient error on the build cluster. It is not your +fault.
compat6x: This port needs to depend on a port misc/compat6x.
configure error: The port's configure script produced some kind of +error. +(Note: using clang as the ports compiler can also trigger this message.)
coredump: Some process in the build chain dropped core. While your port may indeed +be faulty, the process that dropped core should also be fixed.
cpusetsize: This port needs to catch up with the cpusetsize sysctl change in 9-CURRENT.
depend object: The port is trying to reinstall a dependency that already +exists. This is usually caused by the first field of a +*_DEPENDS line (the obj of +obj:dir[:target]) indicating a file that is not installed +by the dependency, causing it to be rebuilt even though it has +already been added from a package.
depend package: There was an error during adding dependencies +from packages. It is the fault of the package being added, not +this port.
dirent: The port has not caught up with the change to scandir(3) +as committed in FreeBSD version 800501.
disk full: The disk filled up on the build system. It is not your +fault.
DISPLAY: 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.
distinfo update: The contents of distinfo does not match the list of +distfiles or patchfiles.
fetch: One or more of the files could not be fetched.
fetch timeout: 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 +MASTER_SITES.
forbidden: Someone has marked this port as "forbidden", almost always due +to security concerns. See the logfile for more information.
gcc bug: You have tickled a bug in gcc itself. See the +GNU bug report documentation +for further information.
gcc4: Your code does not run with the latest gcc version +See the wiki page +for further information.
gmake: Your code does not run with the latest, incompatible, gmake version +(3.82.)
install error: There was an error during installation.
LIB_DEPENDS: The LIB_DEPENDS line specifies a library name +incorrectly. This often happens when a port is upgraded and the +shared library version number changes.
linker error: There is a linker error which is caused by something other than +those flagged elsewhere. +(Note: using clang as the ports compiler can also trigger this message.)
makefile: There is an error in the Makefile, possibly in the default +targets.
manpage: There is a manpage listed in a MAN? macro that does not +exist or is not installed in the right place.
missing header: There is a missing header file. This is usually caused by +either (1) a missing dependency, or (2) specifying an incorrect +location with -I in the compiler command line.
mtree: The port leaves ${PREFIX} in a state that is not +consistent with the mtree definition after pkg_delete. This +usually means some files are missing from PLIST. 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.
nested_declaration: There is a nested declaration in the source code.
new compiler error: 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.
NFS: There was either a temporary NFS error on the build system +(which is not your fault), or the WRKSRC is invalid +(which is your fault).
patch: One or more of the patches failed.
perl: perl 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 perl +in the base system, it also means that many ports now need to include +USE_PERL5.
PLIST: There is a missing item in the PLIST. 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.
process failed: The make process terminated unexpectedly, due to +something like a signal 11 or bus error.
runaway process: Your make package 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.
segfault: Some process in the build chain got a segmentation fault.
sem_wait: This port needs to catch up with semaphore changes in 9-CURRENT.
termios: This port needs to catch up with the termios.h changes in src.
threads: There is a linker error which is caused by failing to find one of +the thread libraries.
truncated_distfile: A package node encountered an error during pkg_add. It is not your +fault. Linimon is trying to figure out this problem.
utmp_x: This port needs to catch up with the utmp_x.h changes in src.
WRKDIR: The port is attempting to change something outside +${WRKDIR}. See handbook +for details.
??? (unknown): The automated script cannot even guess what is wrong with your +port. portmgr tries to keep the processonelog script +reasonably efficient while covering as many errors as possible, but many +errors are not common enough to try to catch.

+ +

Here is an alphabetical list of obsolete errors +that used to be detected by the AI script, but are now uncommon enough to +be skipped:

+ +

alignment: You've managed to confuse the assembler with a misaligned +structure.
apxs: Your port depends on Apache (in particular, the apxs +binary) but the Makefile doesn't have Apache in +BUILD_DEPENDS and/or LIB_DEPENDS.
assert: Compilation failed due to an assert. This is often a variation +on arch or missing header.
awk: awk is complaining about some kind of bogus string +expression.
bison: Your port requires bison, which does not exist in +4.x-stable or newer anymore. Either patch it to use byacc +instead, or define USE_BISON.
cgi-bin: Your port assumes that a directory (usually +/usr/local/www/cgi-bin) already exists, +but by default it doesn't.
chown: POSIX has deprecated the usage +"chown user.group filename" in favor of +"chown user:group filename". This happened quite some time +ago, actually, but it is only now being enforced. (The change was +made to allow '.' in usernames).
ELF: The port does not properly work in the new ELF world. It is +probably looking for an a.out object (e.g., +crt0.o).
f77: gcc in base no longer includes the Fortran compiler +by default.
ffs conflict: Both /usr/include/machine/cpufunc.h and +/usr/include/strings.h are attempting to define int ffs().
getopt.h: <getopt.h> is conflicting with unistd.h.
+getopt: Your port may need to set the new port variable +USE_GETOPT_LONG.
libc_r not found: This library has not yet been ported to e.g. the Sparc.
malloc.h: Including <malloc.h> is now deprecated in favor of +<stdlib.h>.
MOTIF: This port requires Motif but does not define +REQUIRES_MOTIF. See the handbook +for details.
MOTIFLIB: This port requires Motif but does not refer to the libraries +using ${MOTIFLIB}. See handbook +for details.
munmap: POSIX specifies that munmap cannot be called on a zero-length file. +Because of this, during 4.X builds, if cp tries to copy a zero-length file, it +may fail saying, "cp: ...: Invalid argument". This is a problem with the +bindist image on pointyhat, and not the fault of the porter.
perl5: There is a problem in processing a perl5 module.
pod2man: perl is no longer included by default in the base +system, but your port's documentation process depends on it. While +this change helps avoid having a stale version of perl +in the base system, it also means that many ports now need to include +USE_PERL5.
python: The Makefile needs to define USE_PYTHON.
sed: sed is complaining about some kind of bogus regular +expression, probably as a side-effect of its being invoked by +${REINPLACE_COMMAND}. This is often a result of having +replaced usages of perl in the Makefile with usages +of ${REINPLACE_COMMAND} but having left +perl-specific regexps in place.
soundcard.h: machine/soundcard.h has been moved.
stdio: You need to bring your port up to date with the current +<stdio.h>.
stl: Your port requires the STL library but cannot find it.
struct changes: Your port is trying to refer to structure elements that are not +really there. This is often due to changes in the underlying +include files.
sysvipc: Your port is interacting badly with the System V InterProcess *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***