Report created on Mon May 29 00:13:51 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
astro/tkgeomap tcltk@FreeBSD.org configure_error    
audio/esperanza ports@FreeBSD.org configure_error    
audio/siren ports@FreeBSD.org configure_error    
databases/xapian-core sunpoet@FreeBSD.org configure_error    
devel/aarch64-binutils bapt@FreeBSD.org configure_error    
devel/aarch64-none-elf-gcc kan@FreeBSD.org configure_error    
devel/arm-none-eabi-gcc kan@FreeBSD.org configure_error    
devel/arm-none-eabi-gcc492 ian@FreeBSD.org configure_error    
devel/avr-gcc joerg@FreeBSD.org configure_error    
devel/clanlib22 ports@FreeBSD.org configure_error    
devel/creduce swills@FreeBSD.org configure_error    
devel/gcc-msp430-ti-toolchain lev@FreeBSD.org configure_error    
devel/libbfd joerg@FreeBSD.org configure_error    
devel/libdispatch brooks@FreeBSD.org configure_error    
devel/msgpack kuriyama@FreeBSD.org configure_error    
devel/qconf ports@FreeBSD.org configure_error    
devel/rubygem-rice ruby@FreeBSD.org configure_error    
devel/skalibs colin-ports@heliocat.net configure_error    
devel/tcltls mi@aldan.algebra.com configure_error    
emulators/mednafen acm@FreeBSD.org configure_error
linker_error
   
emulators/qemu-user-static sbruno@FreeBSD.org bad_C++_code
configure_error
   
graphics/enblend grog@FreeBSD.org configure_error    
graphics/exact-image ports@FreeBSD.org configure_error    
graphics/exrtools ehaupt@FreeBSD.org configure_error    
graphics/mozjpeg sunpoet@FreeBSD.org configure_error    
irc/ircd-ratbox moggie@elasticmind.net ???
configure_error
   
irc/srvx ports@FreeBSD.org configure_error    
java/classpath java@FreeBSD.org configure_error    
lang/gcc5 gerald@FreeBSD.org configure_error    
mail/bogofilter mandree@FreeBSD.org configure_error    
math/algae ports@FreeBSD.org configure_error    
math/wxMaxima nivit@FreeBSD.org configure_error    
misc/libsupertone fjoe@FreeBSD.org configure_error    
multimedia/tvheadend decke@FreeBSD.org configure_error    
net-im/psi ports@FreeBSD.org configure_error    
net-im/psimedia ports@FreeBSD.org configure_error    
net-mgmt/net-snmp zi@FreeBSD.org configure_error    
net-p2p/verlihub-plugins-chatroom me@skylord.ru configure_error    
net-p2p/verlihub-plugins-floodprotect me@skylord.ru configure_error    
net-p2p/verlihub-plugins-forbid me@skylord.ru configure_error    
net-p2p/verlihub-plugins-iplog me@skylord.ru configure_error    
net-p2p/verlihub-plugins-isp me@skylord.ru configure_error    
net-p2p/verlihub-plugins-luascript me@skylord.ru configure_error    
net-p2p/verlihub-plugins-messanger me@skylord.ru configure_error    
net-p2p/verlihub-plugins-stats me@skylord.ru configure_error    
net/arp-scan johans@FreeBSD.org configure_error    
net/asterisk11 madpilot@FreeBSD.org configure_error    
net/asterisk13 madpilot@FreeBSD.org configure_error    
net/ladvd ports@FreeBSD.org compiler_error
configure_error
   
net/linknx bkoenig@alpha-tierchen.de configure_error    
net/mpich2 thierry@FreeBSD.org configure_error    
net/shadowsocks-libev xiaoding+freebsd@xiaoding.org compiler_error
configure_error
   
net/sipsak jesusr@FreeBSD.org configure_error    
security/clambc zi@FreeBSD.org configure_error
coredump
   
security/duo zi@FreeBSD.org configure_error    
security/libprelude koobs@FreeBSD.org configure_error    
security/pecl-crypto gasol.wu@gmail.com configure_error    
security/snort zi@FreeBSD.org configure_error    
shells/rc quanstro@quanstro.net configure_error    
sysutils/fswatch-mon enrico.m.crisostomo@gmail.com configure_error    
sysutils/jobd mark@heily.com clang_werror
configure_error
   
www/kannel dbaio@FreeBSD.org configure_error    
www/node [I] bradleythughes@fastmail.fm configure_error    
www/node6 [I] bradleythughes@fastmail.fm configure_error    
ports shown: 64   ports with build errors: 64 ports with outstanding PRs: 0  
ports with either build errors or PRs: 64

Notes:

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 prQueryUtils.py 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.