Notes for gcc-6 - reproducible builds result

Version annotated: 6.1.1-3
Identified issues:
Identifier: blacklisted_on_jenkins
Description Some packages have been blacklisted in our test infrastructure because
their build hangs, takes too long, spawns processes that are not killed, or
simply because they use too many resources for our current capacity. (This
is purely practical step - we would like to test these packages.)
Comments: Comments imported from gcc-5

* Uses profile-guided optimizations on major architectures

https://sources.debian.net/src/gcc-5/5.3.1-7/debian/rules2/?hl=731#L731

If we want to keep that, can we think of a way *.gcda files be packaged
and later reused?

* Order of symbols issue:

- libgo/syscall.o

* gcj uses random temp filenames:

- libjava/.libs/gnu-CORBA.o

* Timestamps in jar:

- build/*/libjava/libgcj-tools-5.jar

Add post-processing in libjava/Makefile.am?
Or touch before creating tools.zip in libjava/classpath/tools/Makefile.am?
 

Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise).