Thanks Matthias! According to upstream [up] if gcc 5 is pushed as default gcc version in unstable *before* Qt 5.4.2 hits unstable (which is probably going to be released by the end of next week, and this very same bug being the main blocker now) then apps compiled with gcc5 and Qt < 5.4.2 will need to get recompiled due to BIC. The only way to get this fixed is pushing Qt 5.4.2 (or a patched 5.4.1) to unstable, but we require a transition slot for that due to apps using private headers, so we would really like to wait until 5.4.2 is out. Could that work for you? [up] <https://bugreports.qt.io/browse/QTBUG-45755?focusedCommentId=281535&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-281535> Thanks, Lisandro. -- Un viejo proverbio de El.Machi dice que la memoria es como las papas fritas... ¡nunca sobran! Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Attachment:
signature.asc
Description: This is a digitally signed message part.