WebKit in unstable
Thanks to whoever ftp-master who did the review and approval, WebKit is now in unstable. It has not yet been built on all architectures, but several FTBFSes have already shown up :
- on arm, because
#if defined(arm)
doesn't seem to do much with our toolchain, and because gcc doesn't pack a simple struct such asstruct { short x ; }
on arm, while it obviously does by default on all other architectures, - on hppa, apparently because of a kernel bug,
- on s390, maybe fixable by using gcc 4.2.
I already fixed the arm issue in our git tree, but am waiting for the last buildds to keep up before uploading a new release, in case some other architecture would fail to build. I'd be very much thankful if some people with alpha, x86_64, ia64, mips, or powerpc machines could do some basic testing with /usr/lib/WebKit/GdkLauncher
and /usr/lib/WebKit/QtLauncher
and report any problem (BTS preferred).
Again, interested people are invited to subscribe to the pkg-webkit-maintainers mailing list.
2007-08-26 10:22:32+0900
Both comments and pings are currently closed.
2007-08-26 20:38:56+0900
Tried it, love it (GdkLauncher)! I hope this will be part of regular Epiphany soon. I will try it out on my mips SGI indy soon.
2007-08-27 07:50:57+0900
Mike,
Thank You!
Regards
2007-08-29 09:57:14+0900
I noticed the ARM build log includes -fno-strict-aliasing. JavaScriptCore trunk should build with strict-aliasing and gets a significant performance boost out of it, though the rest of WebKit doesn’t work with it.
Also, I hope any appropriate platform support patches make their way back upstream.
2007-08-29 19:08:10+0900
Maciej: All patches I applied have been sent to your bugzilla, and most of them are already applied on trunk.