FreeBSD ports that you maintain which are currently marked broken

[linimon at FreeBSD.org]

Dear FreeBSD port maintainer:

As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we are attempting to notify maintainers of
ports that are marked as BROKEN by the Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  The most common problem is that the latest
-CURRENT includes gcc3.3, which is much stricter about such things
as function declarations, literal strings constants that continue
over several physical lines, and forcing the deprecation of antique
header files such as varargs.h (we should now be using stdargs.h).

The next most common problem is that compiles succeed on the
i386 architecture (e.g. the common Intel PC), but fail on one
or more of the other architectures due to assumptions about things
such as size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

If you need help in one ore more build environments that you do not
have access to, please ask for help on the freebsd-ports mailing
list.

The build errors are listed below.  In the case where the same
problem exists on more than one build environment, the URL points
to the latest errorlog for that type.  (By 'build environment'
here we mean 'combination of 4.x or 5.x, with target architecture'.)

portname:     x11-toolkits/libXt
build errors: 
<a href="http://bento.FreeBSD.org/errorlogs/amd64-5-full/libXt-0.1.4_2.log">USE XLIB</a> (Feb 25 10:01:08 GMT 2004)

portname:     x11/libSM
build errors: 
<a href="http://bento.FreeBSD.org/errorlogs/amd64-5-full/libSM-6.0.1.p2_1.log">USE XLIB</a> (Feb 25 11:29:39 GMT 2004)

If these build errors are ones that you are already aware of, please
accept our apologies and ignore this message.  On the other hand, if
you no longer wish to maintain this port (or ports), please reply
with a message stating that, and accept our thanks for your efforts
in the past.

Every effort has been made to make sure that these build errors
really do correspond to a port that you maintain.  However, due to
the fact that this is an automated process, it may indeed generate
false matches.  If one of these build errors fits that description,
please forward this email to the author of this software, Mark
Linimon <linimon at lonesome.com>, so that he can attempt to fix the
problem in the future.

Thanks for your efforts to help improve FreeBSD.