FreeBSD ports that you maintain which are currently marked broken

linimon at FreeBSD.org linimon at FreeBSD.org
Mon Apr 30 06:59:50 UTC 2007


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" in their Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  The most common problem is that recent versions
of -CURRENT include gcc3.4, 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 or more build environments that you do not
have access to, please ask for help on the freebsd-ports mailing
list.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The 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/5.x/6.x with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:           audio/prokyon3
broken because:     Does not compile
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.2007041501/prokyon3-0.9.2_2.log (Apr 20 09:24:59 UTC 2007)
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2007042518/prokyon3-0.9.2_2.log (Apr 19 23:07:37 UTC 2007)
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=prokyon3


portname:           chinese/xemacs
broken because:     Does not build even with fix for -lxpg4
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2007042804/zh-xemacs-20.4_2.log (Apr 29 04:49:44 UTC 2007)
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=xemacs


portname:           databases/postgis-jdbc
broken because:     Does not build
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgis-jdbc


portname:           ftp/junglemonkey
broken because:     Does not build
build errors:
http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.6.2007011603/junglemonkey-0.1.11_4.log (Jan 23 21:34:09 UTC 2007)
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2007042804/junglemonkey-0.1.11_5.log (Apr 29 07:59:25 UTC 2007)
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=ftp&portname=junglemonkey


portname:           games/hlserver-cs
broken because:     Incomplete fetch instructions
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=hlserver-cs


portname:           games/hlserver-dod
broken because:     Incomplete fetch instructions
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=hlserver-dod


portname:           japanese/lynx
broken because:     Leaves behind config file on deinstall
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=lynx


portname:           multimedia/ogmrip
broken because:     Incomplete pkg-plist
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2007042804/ogmrip-0.10.2.log (Mar  7 18:27:21 UTC 2007)
http://pointyhat.freebsd.org/errorlogs/ia64-errorlogs/e.7.2007021918/ogmrip-0.10.2.log (Mar 17 22:43:41 UTC 2007)
http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.2006122818/ogmrip-0.10.0.r4_1.log (Jan 15 22:09:58 UTC 2007)
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=ogmrip


portname:           net-mgmt/cflowd
broken because:     Does not compile
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=cflowd


portname:           palm/synce-trayicon
broken because:     Configure fails
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2007042804/synce-trayicon-0.9.0_5.log (Apr 29 09:35:27 UTC 2007)
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-trayicon


portname:           science/ovt
broken because:     Does not build
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=ovt


portname:           textproc/ruby-libxslt
broken because:     Configure fails on FreeBSD >= 5.x
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2007042804/ruby18-libxslt-0.3.0_1.log (Apr 28 21:35:41 UTC 2007)
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=ruby-libxslt


portname:           www/p5-Apache-AuthenCache
broken because:     Broken due the new mod_perl2 API
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=p5-Apache-AuthenCache


portname:           www/p5-Kwiki-Edit-RequireUserName
broken because:     Already bundled in www/p5-Kwiki (0.39 or latter)
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=p5-Kwiki-Edit-RequireUserName


portname:           www/p5-Kwiki-Infobox
broken because:     Already bundled in www/p5-Kwiki (0.39 or latter)
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2007042523/p5-Kwiki-Infobox-0.03.log (Apr 22 17:50:03 UTC 2007)
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=p5-Kwiki-Infobox


portname:           www/p5-Kwiki-ModPerl
broken because:     Already bundled in www/p5-Kwiki (0.39 or latter)
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2007042804/p5-Kwiki-ModPerl-0.09.log (Apr 28 22:36:18 UTC 2007)
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=p5-Kwiki-ModPerl


portname:           www/p5-Kwiki-NavigationToolbar
broken because:     Already bundled in www/p5-Kwiki (0.39 or latter)
build errors:
http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2007042523/p5-Kwiki-NavigationToolbar-0.02.log (Apr 22 17:51:03 UTC 2007)
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=p5-Kwiki-NavigationToolbar


portname:           www/p5-Kwiki-NewPage
broken because:     Already bundled in www/p5-Kwiki (0.39 or latter)
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2007042804/p5-Kwiki-NewPage-0.12.log (Apr 28 20:45:51 UTC 2007)
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=p5-Kwiki-NewPage


portname:           www/rt3
broken because:     Broken due the new mod_perl2 API
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt3


portname:           www/rt32
broken because:     Broken due the new mod_perl2 API
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt32


If these 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 error reports
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 errors fits that description,
please forward this email to the author of this software, Mark
Linimon <linimon at FreeBSD.org>, so that he can attempt to fix the
problem in the future.

Thanks for your efforts to help improve FreeBSD.


More information about the freebsd-ports mailing list