Report created on Mon May 29 00:12:07 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/bristol new_compiler_error    
audio/liblo compiler_error    
cad/freecad new_compiler_error    
databases/gnats4 compiler_error    
databases/tarantool-c clang
databases/virtuoso compiler_error    
databases/xapian-core10 ???
devel/bcc new_compiler_error    
devel/boehm-gc compiler_error    
devel/cheritrace-devel new_compiler_error    
devel/cjose compiler_error    
devel/include-what-you-use new_compiler_error    
devel/kore compiler_error
devel/kore-notls compiler_error    
devel/libepoll-shim new_compiler_error    
devel/libgrading missing_header
devel/libqb compiler_error
devel/linenoise-ng new_compiler_error    
devel/pure-stllib new_compiler_error    
devel/py-libzfs [I] compiler_error    
devel/py3-libzfs [I] compiler_error    
devel/spdlog new_compiler_error    
devel/talloc new_compiler_error    
editors/mp compiler_error    
emulators/simh new_compiler_error    
ftp/curlpp new_compiler_error    
ftp/vsftpd compiler_error    
games/bunnysay new_compiler_error    
graphics/hugin new_compiler_error    
graphics/libboard new_compiler_error    
graphics/opencolorio new_compiler_error    
graphics/pencil compiler_error    
japanese/mh bad_C++_code
japanese/mutt-devel compiler_error    
lang/dmd2 coredump
lang/erlang-runtime19 compiler_error
lang/io ???
lang/mosh compiler_error
lang/newlisp new_compiler_error    
lang/newlisp-devel new_compiler_error    
lang/squirrel new_compiler_error    
mail/mailfromd compiler_error    
math/amath compiler_error    
net-im/gale compiler_error    
net-mgmt/ipv6calc compiler_error    
net/corosync compiler_error    
net/ladvd compiler_error
net/nethogs new_compiler_error    
net/ns3 new_compiler_error    
net/openvswitch new_compiler_error    
net/pvm compiler_error    
net/shadowsocks-libev compiler_error
net/yami4 new_compiler_error    
security/honggfuzz new_compiler_error    
security/py-xmlsec [B] compiler_error    
security/sha1collisiondetection clang_werror
sysutils/fluent-bit compiler_error    
sysutils/lnav new_compiler_error    
sysutils/mbgtools [I] clang
sysutils/p5-BSD-Sysctl new_compiler_error    
sysutils/p5-Unix-Processors compiler_error    
sysutils/sample [I] compiler_error    
sysutils/scprotect [I] clang
sysutils/torque compiler_error
textproc/ansifilter new_compiler_error    
textproc/htdig new_compiler_error    
textproc/msort clang
textproc/opengrm-ngram new_compiler_error    
textproc/uncrustify ???
www/drood compiler_error
www/py-libsass new_compiler_error    
www/swish-e compiler_error    
ports shown: 72   ports with build errors: 72 ports with outstanding PRs: 0  
ports with either build errors or PRs: 72


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.