On Wed, Nov 15, 2017 at 05:28:06PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> There is one *excellent* method to settle this once and forever: submit the
> __FILE__ patch to GCC devs. If it gets accepted then Qt and whatever
> project is affected should change it.
It's forwarded, and it was rejected with some concerns, none of which
where those rised in this thread. We are working on settling those
concerns and will hopefully soon to be able to send another batch for
review.
> If it does not gets accepted then it's a Debian regression.
Remember that for now this patch it is *not* in the Debian's GCC, only
in our patched variant that is used only for the unstable tests in
tests.reproducible-builds.org
> Until that is done I will consider this a non-Qt bug but a GCC regression.
> Show me that GCC upstream devs agree with you Xi and I'll happily forward
> the bug to Qt upstream.
Yes, that's also what I was recommending to my team mates on IRC
yesterday. In the meantime, please feel free to mark the bug as wontfix
as it indeed clearly is.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature