Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 7 Mar 2014 08:28:05 GMT
From:      linimon@FreeBSD.org
To:        ports@freebsd.org
Subject:   FreeBSD unmaintained ports which are currently marked broken
Message-ID:  <201403070828.s278S53O074657@portsmon.freebsd.org>

next in thread | raw e-mail | index | archive | help
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions.
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.

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 7.x/8.x/9.x/-current 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:           chinese/hztty
broken because:     fails to build with new utmpx
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty


portname:           korean/eterm
broken because:     fails to build with new utmpx
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=korean&portname=eterm


portname:           mail/biffer
broken because:     fails to build with new utmpx
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=biffer


portname:           net-im/ysm
broken because:     Fails to install
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=ysm


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


portname:           net/rmsg
broken because:     Does not build after the removal of utmp(5)
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=rmsg


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


portname:           security/pam_alreadyloggedin
broken because:     Does not build with utmpx.
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=pam_alreadyloggedin


portname:           sysutils/hyperic-sigar
broken because:     fails to build with new utmpx
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=hyperic-sigar



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201403070828.s278S53O074657>