Report created on Mon May 29 00:11:32 2017. back to main menu

Enter a new build error (partial match is ok) to get information about FreeBSD ports with that error:

Build error: 

For explanatory information and summary details, see the notes below.

portname maintainer build error logs Problem Reports Responsible
audio/gnuspeechsa ???
audio/vsound clang    
audio/wildmidi clang    
benchmarks/nosqlbench clang    
biology/bedtools clang    
cad/layouteditor clang    
chinese/tin clang    
comms/uartlirc [I] clang    
databases/galera clang    
databases/rocksdb-lite clang    
databases/sqliteodbc-sqlite2 clang    
databases/tarantool clang    
databases/tarantool-c clang
devel/blame ???
devel/byacc clang    
devel/cvs-devel ???
devel/dmucs clang    
devel/dyncall clang    
devel/jna ???
devel/libgtop clang    
devel/libnfc clang    
devel/llvm38 ???
devel/lpc21isp clang    
devel/obby clang    
devel/plan9port clang
devel/py-pyinstaller clang    
devel/radare2 ???
devel/smv clang    
dns/dnscrypt-proxy clang    
dns/getdns clang    
emulators/dtcyber ???
emulators/gngeo clang-bug    
emulators/open-vm-tools [I] clang
emulators/open-vm-tools-nox11 [I] clang_werror    
ftp/wxdfast clang    
games/cataclysm-dda clang_werror    
games/fkiss clang    
games/stonesoup clang    
games/trigger-rally clang    
graphics/azpainter clang    
graphics/dia clang    
graphics/hiptext clang    
graphics/picpuz clang    
graphics/pixie clang    
graphics/sdump clang    
irc/irssi-xmpp clang    
lang/lua53 clang    
lang/pfe clang    
lang/pypy3 clang    
lang/v8-devel clang    
mail/deforaos-mailer clang-bug    
math/gambit clang    
math/openlibm clang
multimedia/cuse4bsd-kmod [I] clang    
multimedia/kissdx clang    
net-im/pidgin-sipe clang_werror    
net-mgmt/yaf clang    
net/aoe [I] clang    
net/bnxt-kmod [I] clang    
net/intel-em-kmod [I] clang    
net/isboot-kmod [I] clang    
net/xorp clang_werror    
news/tin clang    
russian/ircd-hybrid clang    
science/hdf clang    
security/opencryptoki clang    
security/sha1collisiondetection clang_werror
sysutils/atop clang    
sysutils/jobd clang_werror
sysutils/mbgtools [I] clang
sysutils/pefs-kmod [I] clang    
sysutils/pesign clang_werror    
sysutils/py-psutil clang    
sysutils/py-psutil121 clang    
sysutils/scprotect [I] clang
textproc/msort clang
www/mod_perl2 clang-bug    
ports shown: 77   ports with build errors: 77 ports with outstanding PRs: 0  
ports with either build errors or PRs: 77


Clicking on each column heading will cause the report to be redone sorted by that column. Clicking again will reverse the sort.

The portname column includes links to a more complete overview for that port.

The maintainer column includes links to a page showing the status of all ports for that maintainer.

The build error logs column represents the list of unique errors noticed in any build environment (if any). The errors are listed alphabetically. Each entry is a link to a particular errorlog. (In cases where the same error occurs in multiple build environments, the latest errorlog is used.)

The list of build errors that are detected, and a short description of each one, can be found here.

The PRs (if any) for the given port are listed numerically in the Problem Reports column. Thus, for each port, they should also be in order from earliest to latest.

Currently, no effort is made to correlate any individual build error with any individual PR. They are listed in adjacent columns only for your viewing convenience.

The underlying technology of this report relies on trying to extract information from the existing PR database entries. These entries are entered by human users using the send-pr command. As such, the quality of the entries varies greatly.

The fastest, and easiest, information is gleaned from a PR entry whose subject line contains the port category and port name, separated by a slash. However, if this algorithm only flagged those, it would miss nearly 50% of the ports PRs, not to mention all the 'framework' PRs.

So, as an extension, various heuristics are used to guess what it is the user really intended. See the code in for the gory details. What's important to understand is this: there is no possible algorithm that will correctly identify all the ambiguous PRs without getting a few false identifications and still run in less than geological time. So, before you are tempted to file a PR on this algorithm itself, read the code to understand its design tradeoffs, and then consider instead filing followup PRs to the ambiguous PRs that would disambiguate them instead. Thanks -- the author.