"
USE_WXNEEDED, add "-Wl,-z,wxneeded" to pkg-config files
WebKit violates W^X, so binaries linked with it need to be "wxneeded".
Pkg-config files seem to be an appropriate mean of automating this task.
"
the past 3 bulks, or forever.
Various reasons: no d^Hrecent compiler available, base gcc generating
nice internal compiler errors, no atomic ops, etc, etc.
While here, mark all webkits as BROKEN-hppa, since this also requires
clang or g++ 4.7. Our g++ 4.8 port only builds on
i386|amd64|powerpc|sparc64 anyway...
if you're interested^Wbored to death, full past logs at
http://build-failures.rhaalovely.net/alpha/...
that time to workaround a gmake weirdness triggering forkbombs, but now
apparently it causes weird build failures with binutils error messages
when using MAKE_JOBS>=4, as experienced by sthen@, naddy@ & espie@.
Unfortunately, i don't have hardware with 4 cores or more, so didnt see
those... Removing the chunk doesnt seem to show gmake weirdness anymore,
so just do it (tm). Analysed by espie@.
Note that gtk3 FLAVOR is broken on powerpc with "undefined reference to
`__atomic_fetch_add_8'". /me goes crying in a corner.
building webkit is hard, let's go shopping.
See http://webkitgtk.org/2014/03/24/webkitgtk2.4.0-released.html. Note
that Webkit2 API is still broken, on OpenBSD(and FreeBSD) and this might
be the last release shipping the Webkit1 API.
Pass -DLOG_DISABLED=0 to CPPFLAGS to somewhat allow debugging.
Use the same ruby version on sparc64 as other archs now that they're
more reliable.
Remove some patches merged upstream, and add links to upstream bz for
most of the remaining patches.
Note: this needs gnu/usr.bin/binutils/include/opcode/i386.h r1.15 to
build. And gcc 4.8 (and python, ruby & perl :)
Built numerous times on amd64/ppc/sparc64 (broken at runtime on the last
two, but that's not a regression from 2.2..) and went in a bunch of
bulks.
