tag 735488 - patch thanks I've tried to summarize the current arm64 situation. The following are my conclusions, feel free to point if something is wrong, give more info/feedback, etc. = Stuff under debian/ - As explained in a mail before, we don't like the idea of passing -fpermissive as it can lead to very strange crashes. The code will need proper fixing. - We are building webkit with a separate source, -no-javascript-jit and the relevant webkit patches should be applied in src:qtwebkit. The relevant patches contained in the patch submitted by Wookey come from Riku Voipio and seems too similar to other patches we already have there, so it should not be a problem to apply them once we have Qt4 ready form arm64. - It uses linux-g++ instead of linux-g++-64. While that could be the best fit, it would be good to know why. - The autotools changes seems unnecessary, as we are not building the 3rd party code that uses it. I've already added a lintian override to the autotools stuff warning in the repo. = Code patches aarch64.patch: - *No copyright* nor license. We need this at least to be able to apply it and ask upstream if they see it fit. There's the chance that some code comes from Ubuntu people. - Webkit stuff: as described above. - mkspecs: not necessary, just added for completeness. aarch64_fix_atomic_set.patch: - Copyright present. - Possibly needs the above patch applied. = Some extra remarks We need at least the proper copyright and license for the patches. In that way I'm able to apply them in the package and ping upstream wrt them. Of course, if the original author can push it to upstream's gerrit the better, because in case some objection arises I don't need to be in the middle as a (possibly noisy) proxy. Kinds regards, Lisandro. -- 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.