Date: Sat, 18 Jan 2003 13:14:20 -0600 (CST) From: Mark Linimon <linimon@lonesome.com> To: FreeBSD-gnats-submit@FreeBSD.org Subject: www/47194: rework of bento "package building logs and errors" web page Message-ID: <200301181914.h0IJEKlq032937@lonesome.lonesome.com>
next in thread | raw e-mail | index | archive | help
>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 @@
<li>The build is done on a shared (read-only) <tt>/usr/ports</tt>
with <a href=
-"http://www.freebsd.org/handbook/porting.html#PORTING-WRKDIRPREFIX">;
+"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-wrkdir.html">;
<tt>WRKDIRPREFIX</tt></a> set to <tt>/tmp</tt>. If your
<tt>WRKSRC</tt> looks funny, that's probably why.</li>
@@ -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.</li>
+a "can't fetch distfile" error again. Please pay attention to
+<a href="http://people.freebsd.org/~fenner/portsurvey/bad.html">;
+Bill Fenner's distfile checker</a>
+for that.</li>
<li>The ports are built on 4-stable machines. Some of the 5-current
failures may be because of that.
@@ -224,42 +226,138 @@
</ul>
<hr>
-<p>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.</p>
+<p><a name="errorlist">Here is an <b>alphabetical list of errors</b></a>
+detected by my AI script. Note that this is all just a rough guess --
+it is merely for your aid.</p>
+<p>Key (applies only to the items below):
<dl>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+ <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="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"alignment">alignment</a></dt>
+
+<dd>You've managed to confuse the assembler with a misaligned
+structure.</dd>
+
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
+"apxs">apxs</a></dt>
+
+<dd>Your port depends on Apache (in particular, the <tt>apxs</tt>
+binary) but the <tt>Makefile</tt> doesn't have Apache in
+<tt>BUILD_DEPENDS</tt> and/or <tt>LIB_DEPENDS</tt>.</dd>
+
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
+"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. 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 tag=
+"assert">assert</a></dt>
+
+<dd>Compilation failed due to an assert. This is often a variation
+on <tt>arch</tt> or <tt>missing header</tt>.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"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 tag=
+"autoheader">autoheader</a></dt>
+
+<dd>Your port depends on <tt>autoheader</tt>, but the <tt>Makefile</tt>
+cannot find it.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"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="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"awk">awk</a></dt>
+
+<dd><tt>awk</tt> is complaining about some kind of bogus string
+expression.</dd>
+
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
+"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 tag=
"bison">bison</a></dt>
-<dd>Your port requires <tt>bison</tt>, which doesn't exist in
+<dd>Your port requires <tt>bison</tt>, which does not exist in
4-stable or newer anymore. Either patch it to use <tt>byacc</tt>
instead, or define <tt>USE_BISON</tt>.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
-"cc">C compiler error</a></dt>
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
+"cc">compiler error</a></dt>
-<dd>There is a compiler error which is caused by something other
+<dd>There is a C compiler error which is caused by something other
than e.g. "new compiler error".</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"categories">CATEGORIES</a></dt>
<dd>The <tt>CATEGORIES</tt> line in <tt>Makefile</tt> includes an
invalid category.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"cgi-bin">cgi-bin</a></dt>
+
+<dd>Your port assumes that a directory (usually
+<tt>/usr/local/www/cgi-bin</tt>) already exists,
+but by default it doesn't.</dd>
+
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
"checksum">checksum</a></dt>
<dd>The checksum of one or more of the files is incorrect.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"chown">chown</a></dt>
+
+<dd><tt>POSIX</tt> has deprecated the usage
+"<tt>chown user.group filename</tt>" in favor of
+"<tt>chown user:group filename</tt>". This happened quite some time
+ago, actually, but it is only now being enforced. (The change was
+made to allow '.' in usernames).</dd>
+
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
"configure">configure error</a></dt>
<dd>The port's <tt>configure</tt> script produced some kind of
error.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"coredump">coredump</a></dt>
+
+<dd>Some process 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 tag=
"dependobj">depend object</a></dt>
<dd>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 <a href="#pkgadd">added from a package</a>.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"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="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a tag=
"df">disk full</a></dt>
<dd>The disk filled up on the build system. It is not your
fault.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"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="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
"distinfo">distinfo update</a></dt>
-<dd>The contents of <tt>distinfo</tt> doesn't match the list of
+<dd>The contents of <tt>distinfo</tt> does not match the list of
distfiles or patchfiles.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"elf">ELF</a></dt>
<dd>The port does not properly work in the new ELF world. It is
probably looking for an <tt>a.out</tt> object (e.g.,
<tt>crt0.o</tt>).</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
"fetch">fetch</a></dt>
-<dd>One or more of the files couldn't be fetched.</dd>
+<dd>One or more of the files could not be fetched.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"fetch-timeout">fetch timeout</a></dt>
<dd>Your fetch process was killed because it took too long. (More
@@ -315,65 +413,101 @@
put sites with better connectivity near the beginning of
<tt>MASTER_SITES</tt>.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
-"instal">install error</a></dt>
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"ffs_conflict">ffs conflict</a></dt>
+
+<dd>Both <tt>/usr/include/machine/cpufunc.h</tt> and
+<tt>/usr/include/strings.h</tt> are attempting to define <tt>int ffs()</tt>.
+The "correct" fix is not known at this time.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"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 tag=
+"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="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"getopt.h">getopt.h</a></dt>
+
+<dd><tt><getopt.h></tt> is conflicting with <tt>unistd.h</tt>.</dd>
+
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
+"install">install error</a></dt>
<dd>There was an error during installation.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
-"nfs">NFS</a></dt>
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
+"lc_r">lib c_r not found</a></dt>
-<dd>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).</dd>
+<dd>This library has not yet been ported to e.g. the
+Sparc. (This may have been fixed recently).</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
"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="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
"ld">linker error</a></dt>
<dd>There is a linker error which is caused by something other than
those flagged by e.g. MOTIF or MOTIFLIB.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
+"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 tag=
+"malloc.h">malloc.h</a></dt>
+
+<dd>Including <tt><malloc.h></tt> is now deprecated in favor of
+<tt><stdlib.h></tt>.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"manpage">manpage</a></dt>
-<dd>There is a manpage listed in a <tt>MAN?</tt> macro that doesn't
+<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="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
"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="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"motif">MOTIF</a></dt>
<dd>This port requires Motif but does not define
<tt>REQUIRES_MOTIF</tt>. See the <a href=
-"http://www.freebsd.org/handbook/porting.html#PORTING-MOTIF">handbook</a>;
+"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-motif.html">handbook</a>;
for details.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"motiflib">MOTIFLIB</a></dt>
<dd>This port requires Motif but does not refer to the libraries
using <tt>${MOTIFLIB}</tt>. See <a href=
-"http://www.freebsd.org/handbook/porting.html#PORTING-MOTIF">handbook</a>;
+"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-motif.html">handbook</a>;
for details.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"mtree">mtree</a></dt>
<dd>The port leaves <tt>${PREFIX}</tt> in a state that is not
-consistent with the mtree definiton after <tt>pkg_delete</tt>. This
+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.
@@ -381,42 +515,116 @@
it is not supposed to, or incorrectly modifying some directory's
permission.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
"newgcc">new compiler error</a></dt>
-<dd>The new gcc (2.95.x) doesn't like the source code. This is
+<dd>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.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(transient)" src="/errorlogs/images/green-ball.gif"><a tag=
+"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 tag=
"patch">patch</a></dt>
<dd>One or more of the patches failed.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
+"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="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"perl5">perl5</a></dt>
<dd>There is a problem in processing a <tt>perl5</tt> module.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
"plist">PLIST</a></dt>
-<dd>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
+<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="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
+"pod2man">pod2man</a></dt>
+
+<dd><tt>perl</tt> 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 <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 tag=
+"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 tag=
+"python">python</a></dt>
+
+<dd>The <tt>Makefile</tt> needs to define <tt>USE_PYTHON</tt>.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"runaway">runaway process</a></dt>
-<dd>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
+<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="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"sed">sed</a></dt>
+
+<dd><tt>sed</tt> is complaining about some kind of bogus regular
+expression, probably as a side-effect of its being invoked by
+<tt>${REINPLACE_COMMAND}</tt>. This is often a result of having
+replaced usages of <tt>perl</tt> in the <tt>Makefile</tt> with usages
+of <tt>${REINPLACE_COMMAND}</tt> but having left
+<tt>perl</tt>-specific regexps in place.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"soundcard.h">soundcard.h</a></dt>
+
+<dd><tt>machine/soundcard.h</tt> has been moved.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"values.h">values.h</a></dt>
+
+<dd><tt>values.h</tt> has been moved.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"stdio">stdio</a></dt>
+
+<dd>You need to bring your port up to date with the current
+<tt><stdio.h></tt>.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"stl">stl</a></dt>
+
+<dd>Your port requires the <tt>STL</tt> library but cannot find it.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"struct">struct changes</a></dt>
+
+<dd>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.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"texinfo">texinfo</a></dt>
<dd>The new <tt>makeinfo</tt> cannot process a texinfo source file.
@@ -424,32 +632,38 @@
through if you are sure it's correct regardless of what
<tt>makeinfo</tt> says.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
+"wait">union wait</a></dt>
+
+<dd>The compiler could not calculate the storage size of an object,
+often due to misuse of a union.</dd>
+
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"usexlib">USE_XLIB</a></dt>
<dd>You should specify <tt>USE_XLIB</tt> for this port since it
appears to use X.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"wrkdir">WRKDIR</a></dt>
<dd>The port is attempting to change something outside
<tt>${WRKDIR}</tt>. See <a href=
-"http://www.freebsd.org/handbook/porting.html#PORTING-WRKDIR">handbook</a>;
+"http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-wrkdir.html">handbook</a>;
for details.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
+<dt><img alt="(uncommon)" src="/errorlogs/images/purple-ball.gif"><a tag=
"xfree4man">X manpage</a></dt>
-<dd>This port doesn't install a manpage but imake rules are
+<dd>This port does not install a manpage but <tt>imake</tt> rules are
generating commands to convert manpages to HTML format. This is
most likely fixed by changing <tt>ComplexProgramTarget()</tt> in
-Imakefile to <tt>ComplexProgramTargetNoMan()</tt>. Note that
-defining <tt>NO_INSTALL_MANPAGES</tt> in the Makefile is no longer
-sufficient in XFree86-4.</dd>
+<tt>Imakefile</tt> to <tt>ComplexProgramTargetNoMan()</tt>. Note that
+defining <tt>NO_INSTALL_MANPAGES</tt> in the <tt>Makefile</tt> is no
+longer sufficient in XFree86-4.</dd>
-<dt><img alt="*" src="/errorlogs/images/green-ball.gif"><a tag=
-"unknown">???</a></dt>
+<dt><img alt="(common)" src="/errorlogs/images/blue-ball.gif"><a tag=
+"unknown">??? (unknown)</a></dt>
<dd>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</a></center>
</body>
</html>
-
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-www" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301181914.h0IJEKlq032937>