Packages in stretch/i386 which failed to build from source

121 (0.5%) packages which failed to build from source in stretch/i386: (this list is filtered and only shows unexpected ftbfs issues - see the list below for expected failures.)

llvm-toolchain-7 xapian-core icu mpqc3 ants# sagemath# golang-1.8 yade scilab subversion# yadifa llvm-toolchain-3.9 python-django libtemplate-plugin-calendar-simple-perl python-apt zookeeper ncbi-vdb ipywidgets libio-socket-ssl-perl ruby2.3 gridengine# strace+ elixir-lang urwid crash node-grunt-contrib-copy node-marked-man python-kdcproxy 0ad prometheus x264 node-yargs watcher refind# cadabra dico custodia txfixtures debci sra-sdk python-babel android-platform-external-doclava traverso mkosi zfs-fuse sword botch python-arrayfire galera-3 tap.py pbbam neovim zeroc-ice ecere-sdk translate-toolkit cups# sketch validator.js python-formencode sslsplit dc-qt tcc user-mode-linux saga qbs wiredtiger sbcl ryu libio-socket-multicast6-perl polygen soundscaperenderer kmer xpp regina-rexx the+ ruby-eventmachine python-gammu nuitka llvm-toolchain-3.8 php-sabre-vobject-3 python-argcomplete python-biplist nodejs handbrake natbraille libpqtypes bcftools### quantlib-swig kvmtool nbd openbios gatos latrace# openmsx exec-maven-plugin argyll meson ocrmypdf jetty9 kbuild golang-github-boltdb-bolt mlton blockdiag gammu libffado jnr-posix ruby-diaspora-vines scilab-plotlib git-build-recipe iodine# 3270font cinder scilab-celestlab cross-toolchain-base-ports cvc3 scilab-ann trilinos snap-aligner llvm-toolchain-4.0 checkinstall bagelP

1 (0.0%) packages which failed to build from source in stretch/i386 due to our changes in the toolchain or due to our setup. This list includes packages tagged or ftbfs_build-indep_not_build_on_some_archs.

debian-installer#

A package name displayed with a bold font is an indication that this package has a note. Visited packages are linked in green, those which have not been visited are linked in blue.
A # sign after the name of a package indicates that a bug is filed against it. Likewise, a + sign indicates there is a patch available, a P means a pending bug while # indicates a closed bug. In cases of several bugs, the symbol is repeated.