Packages in stretch/i386 which failed to build from source

133 (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.)

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

3 (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 ffile_prefix_map_passed_to_clang.

debian-installer# thunderbird llvm-toolchain-7

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.