Am 25.06.2014 17:26, schrieb Romain Francoise: > In preparation of this switch David Suárez did a full archive rebuild on > EC2, the results of which are detailed in the post linked above. > In summary, the bulk of the failures is for packages that explicitly use > an older GCC version, which doesn't understand -fstack-protector-strong. > If your package is affected, you will need to filter out the new flag > and re-add the old one, or disable stack protection entirely (which is > the least preferred option). See dpkg-buildflags(1) for details on how > to do this.
No, the preferred fix is to use the default GCC. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53aafeaf.8080...@debian.org
