Report created on Tue Sep 26 10:44:28 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/ardour5 linker_error    
audio/calf linker_error    
audio/ccaudio2 linker_error    
audio/jack linker_error    
audio/pulseaudio linker_error    
audio/smasher linker_error    
audio/spiralsynth linker_error    
audio/xsynth-dssi linker_error    
benchmarks/fio linker_error    
biology/seqan-apps ???
cad/kicad linker_error    
cad/librecad linker_error    
comms/sdr-wspr linker_error    
databases/fastdb linker_error
databases/kyotocabinet ???
databases/monetdb linker_error    
databases/mysql-q4m linker_error    
deskutils/cdcat linker_error
deskutils/gxneur linker_error    
devel/ace linker_error    
devel/ccrtp linker_error    
devel/codeblocks bad_C++_code
devel/libgit2 linker_error    
devel/libgpkg linker_error    
devel/libhtp linker_error    
devel/libqb compiler_error
devel/llvm-devel linker_error    
devel/ocl-icd linker_error    
editors/le linker_error    
emulators/mednafen configure_error
ftp/fastdfs linker_error    
games/alienarena linker_error    
games/caph linker_error    
games/cleanq3 linker_error    
games/dustrac linker_error    
games/edge linker_error    
games/egl linker_error    
games/evq3 linker_error    
games/ezquake linker_error    
games/flare-engine linker_error    
games/freedroidrpg linker_error    
games/frobtads linker_error    
games/gnomebreakout linker_error    
games/gnubg linker_error    
games/joequake linker_error    
games/lander linker_error    
games/nehquake linker_error    
games/powder-toy linker_error    
games/q2p linker_error    
games/quake2max linker_error    
games/qudos linker_error    
games/redeclipse linker_error    
games/searchandrescue linker_error    
games/tenebrae linker_error    
games/tremulous linker_error    
games/uhexen2 linker_error    
games/wesnoth linker_error    
games/worldofpadman linker_error    
graphics/a2png linker_error    
graphics/flam3 linker_error    
graphics/graphene linker_error    
graphics/graphviz linker_error    
graphics/luminance linker_error    
graphics/luminance-qt5 linker_error    
graphics/mandelbulber linker_error    
graphics/wayland linker_error    
irc/charybdis linker_error    
irc/ircd-ratbox-devel linker_error    
irc/undernet-ircu coredump
lang/ecl coredump
lang/erlang-runtime19 compiler_error
lang/erlang-runtime20 compiler_error
math/acalc linker_error    
math/ceres-solver linker_error    
math/msieve linker_error    
math/ogdf linker_error    
math/reduce linker_error    
multimedia/audacious linker_error    
multimedia/audacious-gtk3 linker_error    
multimedia/avidemux linker_error    
multimedia/libmtp linker_error    
multimedia/mediainfo linker_error    
multimedia/mlt linker_error    
multimedia/rage linker_error    
multimedia/xmms linker_error    
net-im/qTox linker_error    
net-mgmt/aircrack-ng linker_error    
net-mgmt/netxms linker_error    
net/haproxy linker_error    
net/haproxy-devel linker_error    
net/iaxmodem linker_error    
net/mediastreamer linker_error    
net/ntp linker_error    
net/radvd linker_error    
net/torsocks linker_error    
polish/qnapi linker_error    
print/gribouy linker_error    
science/InsightToolkit linker_error    
security/kickpass linker_error    
security/stunnel linker_error    
sysutils/cmogstored linker_error    
sysutils/lsof [I] linker_error    
sysutils/odo linker_error    
sysutils/pcapfix linker_error    
sysutils/procenv linker_error    
sysutils/psmisc linker_error    
sysutils/tlsdate linker_error    
sysutils/watchman linker_error    
textproc/libucl linker_error    
www/drood compiler_error
www/hypermail linker_error    
www/rubygem-passenger linker_error    
www/xshttpd linker_error    
www/xshttpd-devel linker_error    
x11-wm/cde linker_error
x11-wm/wmconfig linker_error    
ports shown: 116   ports with build errors: 116 ports with outstanding PRs: 0  
ports with either build errors or PRs: 116


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.