Hello Kubuntu Developers and Jackson, I'm skeptical as to using an unofficial port of the V8 engine for just one architecture. After all, unofficial items should NOT be accepted into the Ubuntu archive at all. Jackson, do you think you can communicate with the person who ported the V8 engine to PowerPC to try and make it official? Personally I would want the entire PowerPC architecture port in Ubuntu killed, but my opinions about PowerPC do not comply with the general opinions of Ubuntu, Lubuntu and Kubuntu communities on the same matter. Nevertheless, I am not willing to see a V8 engine in our archive that is unofficial. But, we can wait probably until the official release of KDE Frameworks 5 and Plasma Workspaces 2. Then we will have to see if we can make the V8 engine official, or we just can't support Qt 5 on PowerPC. We can still support KDE Software Collection 4 for PowerPC users if the latter has to happen. Regards, Howard Chan (smartboyhw) Kubuntu Member <div class="gmail_quote">On 2013/9/1 上午10:53, "Jackson Doak" <<a href="mailto:noskcaj@ubuntu.com">noskcaj@ubuntu.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Forwarded to kubuntu since it affects them too ---------- Forwarded message ---------- From: Jackson Doak <<a href="mailto:noskcaj@ubuntu.com">noskcaj@ubuntu.com</a>> Date: Sun, Sep 1, 2013 at 8:36 AM Subject: Qt on PowerPC To: Julien Lavergne <<a href="mailto:gilir@ubuntu.com">gilir@ubuntu.com</a>>, "<a href="mailto:lubuntu-qa@lists.launchpad.net">lubuntu-qa@lists.launchpad.net</a>" <<a href="mailto:lubuntu-qa@lists.launchpad.net">lubuntu-qa@lists.launchpad.net</a>>, Phill Whiteside <<a href="mailto:PhillW@ubuntu.com">PhillW@ubuntu.com</a>> Currently most of Qt fails to build in ubuntu on powerpc. This is a huge bug for us since LXDE is rather dependant on Qt. The build issues can all be traced back to the javascript backend for Qt requiring google's v8 engine to work. The build log is at <a href="https://launchpadlibrarian.net/147271709/buildlog_ubuntu-saucy-powerpc.qtjsbackend-opensource-src_5.0.2-3_FAILEDTOBUILD.txt.gz" target="_blank">https://launchpadlibrarian.net/147271709/buildlog_ubuntu-saucy-powerpc.qtjsbackend-opensource-src_5.0.2-3_FAILEDTOBUILD.txt.gz</a> . v8 is also used by chrome and chromium as a backend. The FTBFS list is at <a href="http://qa.ubuntuwire.org/ftbfs/" target="_blank">http://qa.ubuntuwire.org/ftbfs/</a> One possible solution is using the un-official v8 port. The old version is at <a href="https://github.com/ic/v8-powerpc" target="_blank">https://github.com/ic/v8-powerpc</a> and the new version at <a href="https://github.com/andrewlow/v8ppc" target="_blank">https://github.com/andrewlow/v8ppc</a> . To-Do list (in no particular order): 1. Investigate which packages don't actually need the js backend and try to force them to build 2. Get julien to comment on this because he knows more than i do 3. Test both of the v8 git versions, see if either work well enough for us to use. 4. package the v8 git version we choose to use and patch the other code to be able to use it. 5. Contact the developers of the git versions for their help. It would be great if we could have this working by 14.04 Jackson -- kubuntu-devel mailing list <a href="mailto:kubuntu-devel@lists.ubuntu.com">kubuntu-devel@lists.ubuntu.com</a> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel</a> </blockquote></div>