Report created on Tue Sep 26 09:05:49 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/mpdas new_compiler_error    
biology/phyml clang
cad/freecad new_compiler_error    
cad/freehdl new_compiler_error    
comms/sunxi-tools new_compiler_error    
databases/fastdb linker_error
devel/bcc new_compiler_error    
devel/cheritrace-devel new_compiler_error    
devel/include-what-you-use new_compiler_error    
devel/judy new_compiler_error    
devel/libepoll-shim new_compiler_error    
devel/libgrading missing_header
devel/pure-stllib new_compiler_error    
devel/spdlog ???
devel/talloc new_compiler_error    
dns/packetq new_compiler_error    
emulators/simh new_compiler_error    
ftp/curlpp ???
games/bunnysay new_compiler_error    
games/crafty ???
graphics/animorph new_compiler_error    
graphics/hugin new_compiler_error    
graphics/libboard new_compiler_error    
graphics/opencollada arch
graphics/rawtherapee new_compiler_error    
graphics/rawtherapee-devel (unknown) new_compiler_error    
lang/dmd2 new_compiler_error    
lang/newlisp new_compiler_error    
lang/newlisp-devel new_compiler_error    
lang/squirrel new_compiler_error    
net/nethogs new_compiler_error    
net/ns3 new_compiler_error    
net/openvswitch new_compiler_error    
net/yami4 new_compiler_error    
security/honggfuzz new_compiler_error    
security/sha1collisiondetection new_compiler_error    
sysutils/lnav new_compiler_error    
sysutils/p5-BSD-Sysctl new_compiler_error    
sysutils/py-psutil121 clang
textproc/ansifilter new_compiler_error    
textproc/ffe new_compiler_error    
textproc/htdig new_compiler_error    
textproc/opengrm-ngram new_compiler_error    
textproc/teckit new_compiler_error    
www/py-libsass new_compiler_error    
ports shown: 45   ports with build errors: 45 ports with outstanding PRs: 0  
ports with either build errors or PRs: 45


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.