Report created on Tue Sep 26 10:44:05 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/audacity configure_error    
benchmarks/polygraph configure_error    
databases/xapian-core configure_error    
devel/aarch64-none-elf-gcc configure_error    
devel/arm-none-eabi-gcc configure_error    
devel/avr-gcc configure_error    
devel/breakpad configure_error    
devel/ccache-memcached-static configure_error    
devel/courier-unicode configure_error    
devel/creduce configure_error    
devel/gcc-msp430-ti-toolchain configure_error    
devel/gearmand configure_error    
devel/gearmand-devel configure_error    
devel/libbfd configure_error    
devel/libdispatch configure_error    
devel/msgpack configure_error    
devel/skalibs configure_error    
devel/tcltls configure_error    
editors/libreoffice configure_error    
emulators/mednafen configure_error
emulators/qemu-user-static configure_error    
emulators/stella configure_error    
games/warzone2100 configure_error    
graphics/mozjpeg configure_error    
graphics/pfstmo configure_error    
graphics/sam2p configure_error    
irc/ircd-ratbox ???
irc/srvx configure_error    
java/openjdk8-jre configure_error    
math/wxMaxima configure_error    
multimedia/tvheadend configure_error    
net-mgmt/net-snmp configure_error    
net/arp-scan configure_error    
net/mpich2 configure_error    
net/shadowsocks-libev compiler_error
net/sipsak configure_error    
polish/ekg configure_error    
security/duo configure_error    
security/snort configure_error    
sysutils/fswatch-mon configure_error    
sysutils/jobd configure_error    
ports shown: 41   ports with build errors: 41 ports with outstanding PRs: 0  
ports with either build errors or PRs: 41


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.