From owner-freebsd-www Sat Jan 18 11:20:17 2003 Delivered-To: freebsd-www@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5A1337B401 for ; Sat, 18 Jan 2003 11:20:02 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3683143F1E for ; Sat, 18 Jan 2003 11:20:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h0IJK1NS014630 for ; Sat, 18 Jan 2003 11:20:01 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h0IJK10g014629; Sat, 18 Jan 2003 11:20:01 -0800 (PST) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52EB937B401 for ; Sat, 18 Jan 2003 11:14:07 -0800 (PST) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 364C243E4A for ; Sat, 18 Jan 2003 11:14:06 -0800 (PST) (envelope-from linimon@lonesome.com) Received: from lonesome.lonesome.com (cs2876-77.austin.rr.com [24.28.76.77]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.soaustin.net (Postfix) with ESMTP id F0140140B7 for ; Sat, 18 Jan 2003 13:14:03 -0600 (CST) Received: from lonesome.lonesome.com (localhost.lonesome.com [127.0.0.1]) by lonesome.lonesome.com (8.12.6/8.12.3) with ESMTP id h0IJELWm032938 for ; Sat, 18 Jan 2003 13:14:21 -0600 (CST) (envelope-from linimon@lonesome.lonesome.com) Received: (from linimon@localhost) by lonesome.lonesome.com (8.12.7/8.12.6/Submit) id h0IJEKlq032937; Sat, 18 Jan 2003 13:14:20 -0600 (CST) (envelope-from linimon) Message-Id: <200301181914.h0IJEKlq032937@lonesome.lonesome.com> Date: Sat, 18 Jan 2003 13:14:20 -0600 (CST) From: Mark Linimon To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113.1 Subject: www/47194: rework of bento "package building logs and errors" web page Sender: owner-freebsd-www@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 47194 >Category: www >Synopsis: rework of bento "package building logs and errors" web page >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-www >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sat Jan 18 11:20:00 PST 2003 >Closed-Date: >Last-Modified: >Originator: Mark Linimon >Release: FreeBSD-4.7 >Organization: FreeBSD >Environment: N/A >Description: Together with my PR www/44919, these changes help classify more than half of the errorlog summaries currently reported as '???' into something more useful -- in particular, flagging as 'arch' most cases of build failures on alpha and ia64 that are due to various i386-edness enabled by default. As well, some broken links into the handbook are fixed. As an experiment, since so many error explanations are added, an attempt is made to color-code their icons by "common/ uncommon/not-your-fault" as a further help to novice and intermediate porters. >How-To-Repeat: N/A >Fix: --- index.html.dist Sat Jan 11 01:48:39 2003 +++ index.html Mon Jan 13 01:05:25 2003 @@ -198,7 +198,7 @@
  • The build is done on a shared (read-only) /usr/ports with +"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-wrkdir.html"> WRKDIRPREFIX set to /tmp. If your WRKSRC looks funny, that's probably why.
    • @@ -211,8 +211,10 @@ 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 Bill -Fenner's distfile checker for that. +a "can't fetch distfile" error again. Please pay attention to + +Bill Fenner's distfile checker +for that.
  • The ports are built on 4-stable machines. Some of the 5-current failures may be because of that. @@ -224,42 +226,138 @@
    -

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

    +

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

    +

    Key (applies only to the items below):

    -
    *(common)The most common + errors.
    +
    (uncommon)Some less common + errors.
    +
    (transient)Transient + errors. These may not be your fault.
    +
    +

    + +

    +

    +
    (uncommon)alignment
    + +
    You've managed to confuse the assembler with a misaligned +structure.
    + +
    (common)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.
    + +
    (common)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. In other cases +the problems run much deeper, in which case ONLY_FOR_ARCHS +may be needed.
    + +
    (uncommon)assert
    + +
    Compilation failed due to an assert. This is often a variation +on arch or missing header.
    + +
    (uncommon)autoconf
    + +
    Your port depends on autoconf, but the Makefile +either doesn't have USE_AUTOCONF, or does not use +USE_AUTOCONF_VER correctly.
    + +
    (uncommon)autoheader
    + +
    Your port depends on autoheader, but the Makefile +cannot find it.
    + +
    (uncommon)automake
    + +
    Your port depends on automake, but the Makefile +either doesn't have USE_AUTOMAKE, or does not use +USE_AUTOMAKE_VER correctly.
    + +
    (uncommon)awk
    + +
    awk is complaining about some kind of bogus string +expression.
    + +
    (common)bad C++ code
    + +
    There is a compiler error which is caused by something specific +to C++.
    + +
    (common)bison
    -
    Your port requires bison, which doesn't exist in +
    Your port requires bison, which does not exist in 4-stable or newer anymore. Either patch it to use byacc instead, or define USE_BISON.
    -
    *C compiler error
    +
    (common)compiler error
    -
    There is a compiler error which is caused by something other +
    There is a C compiler error which is caused by something other than e.g. "new compiler error".
    -
    *(uncommon)CATEGORIES
    The CATEGORIES line in Makefile includes an invalid category.
    -
    *(uncommon)cgi-bin
    + +
    Your port assumes that a directory (usually +/usr/local/www/cgi-bin) already exists, +but by default it doesn't.
    + +
    (common)checksum
    The checksum of one or more of the files is incorrect.
    -
    *(uncommon)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).
    + +
    (common)configure error
    The port's configure script produced some kind of error.
    -
    *(uncommon)coredump
    + +
    Some process dropped core. While your port may indeed be faulty, +the process that dropped core should also be fixed.
    + +
    (uncommon)depend object
    The port is trying to reinstall a dependency that already @@ -269,45 +367,45 @@ by the dependency, causing it to be rebuilt even though it has already been added from a package.
    -
    *(uncommon)depend package
    There was an error during adding dependencies from packages. It is the fault of the package being added, not this port.
    -
    *(transient)disk full
    The disk filled up on the build system. It is not your fault.
    -
    *(uncommon)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.
    -
    *(common)distinfo update
    -
    The contents of distinfo doesn't match the list of +
    The contents of distinfo does not match the list of distfiles or patchfiles.
    -
    *(uncommon)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).
    -
    *(common)fetch
    -
    One or more of the files couldn't be fetched.
    +
    One or more of the files could not be fetched.
    -
    *(uncommon)fetch timeout
    Your fetch process was killed because it took too long. (More @@ -315,65 +413,101 @@ put sites with better connectivity near the beginning of MASTER_SITES.
    -
    *install error
    +
    (uncommon)ffs conflict
    + +
    Both /usr/include/machine/cpufunc.h and +/usr/include/strings.h are attempting to define int ffs(). +The "correct" fix is not known at this time.
    + +
    (uncommon)forbidden
    + +
    Someone has marked this port as "forbidden", almost always due +to security concerns. See the logfile for more information.
    + +
    (uncommon)gcc bug
    + +
    You have tickled a bug in gcc itself. See the +GNU bug report documentation +for further information.
    + +
    (uncommon)getopt.h
    + +
    <getopt.h> is conflicting with unistd.h.
    + +
    (common)install error
    There was an error during installation.
    -
    *NFS
    +
    (common)lib c_r not found
    -
    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).
    +
    This library has not yet been ported to e.g. the +Sparc. (This may have been fixed recently).
    -
    *(common)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.
    -
    *(common)linker error
    There is a linker error which is caused by something other than those flagged by e.g. MOTIF or MOTIFLIB.
    -
    *(common)makefile
    + +
    There is an error in the Makefile, possibly in the default +targets.
    + +
    (uncommon)malloc.h
    + +
    Including <malloc.h> is now deprecated in favor of +<stdlib.h>.
    + +
    (uncommon)manpage
    -
    There is a manpage listed in a MAN? macro that doesn't +
    There is a manpage listed in a MAN? macro that does not exist or is not installed in the right place.
    -
    *(common)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.
    -
    *(uncommon)MOTIF
    This port requires Motif but does not define REQUIRES_MOTIF. See the handbook +"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-motif.html">handbook for details.
    -
    *(uncommon)MOTIFLIB
    This port requires Motif but does not refer to the libraries using ${MOTIFLIB}. See handbook +"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-motif.html">handbook for details.
    -
    *(uncommon)mtree
    The port leaves ${PREFIX} in a state that is not -consistent with the mtree definiton after pkg_delete. This +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. @@ -381,42 +515,116 @@ it is not supposed to, or incorrectly modifying some directory's permission.
    -
    *(common)new compiler error
    -
    The new gcc (2.95.x) doesn't like the source code. This is +
    The new gcc (2.95.x or above) does not like the source code. This is usually due to stricter C++ type checking or changes in register allocation policy.
    -
    *(transient)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).
    + +
    (common)patch
    One or more of the patches failed.
    -
    *(common)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.
    + +
    (uncommon)perl5
    There is a problem in processing a perl5 module.
    -
    *(common)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 +
    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.
    -
    *(common)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.
    + +
    (common)process failed
    + +
    The make process terminated unexpectedly, due to +something like a signal 11 or bus error.
    + +
    (uncommon)python
    + +
    The Makefile needs to define USE_PYTHON.
    + +
    (uncommon)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 +
    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.
    -
    *(uncommon)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.
    + +
    (uncommon)soundcard.h
    + +
    machine/soundcard.h has been moved.
    + +
    (uncommon)values.h
    + +
    values.h has been moved.
    + +
    (uncommon)stdio
    + +
    You need to bring your port up to date with the current +<stdio.h>.
    + +
    (uncommon)stl
    + +
    Your port requires the STL library but cannot find it.
    + +
    (uncommon)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.
    + +
    (uncommon)texinfo
    The new makeinfo cannot process a texinfo source file. @@ -424,32 +632,38 @@ through if you are sure it's correct regardless of what makeinfo says.
    -
    *(uncommon)union wait
    + +
    The compiler could not calculate the storage size of an object, +often due to misuse of a union.
    + +
    (uncommon)USE_XLIB
    You should specify USE_XLIB for this port since it appears to use X.
    -
    *(uncommon)WRKDIR
    The port is attempting to change something outside ${WRKDIR}. See handbook +"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-wrkdir.html">handbook for details.
    -
    *(uncommon)X manpage
    -
    This port doesn't install a manpage but imake rules are +
    This port does not install a manpage but imake rules are generating commands to convert manpages to HTML format. This is most likely fixed by changing ComplexProgramTarget() in -Imakefile to ComplexProgramTargetNoMan(). Note that -defining NO_INSTALL_MANPAGES in the Makefile is no longer -sufficient in XFree86-4.
    +Imakefile to ComplexProgramTargetNoMan(). Note that +defining NO_INSTALL_MANPAGES in the Makefile is no +longer sufficient in XFree86-4. -
    *???
    +
    (common)??? (unknown)
    The automated script cannot even guess what is wrong with your port. Either the script is really stupid (more likely), or your @@ -462,4 +676,3 @@ page - >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-www" in the body of the message