Dear FreeBSD port maintainer:
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: www/libxul
broken because: build error on js/xpconnect/src/libxpconnect_s.a.desc
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=wwwportname=libxul
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 lini...@freebsd.org, so that he can attempt to fix the
problem in the future.
Thanks for your efforts to help improve FreeBSD.
___
freebsd-gecko@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-gecko
To unsubscribe, send any mail to freebsd-gecko-unsubscr...@freebsd.org
