libproxy B-D on webkitgtk

[Thorsten Glaser]

John Paul Adrian Glaubitz dixit:

>Unfortunately, this seems to be impossible at the moment since libproxy
>has a build dependency on webkitgtk which takes huge amounts of memory
>to compile and eventually fails:

It needs porting anyway (at least to m68k), and symbols handling
(adding -gstabs to CFLAGS/CXXFLAGS/LDFLAGS on non-mainstream arches).

>This is on a sh4 buildd with 6 GiB of swap and 512 MiB of RAM. I am

Ugh. Few, but maybe barely manageable. Get more RAM, if possible.

>However, I am still wondering whether the build dependency of
>libproxy on webkitgtk is actually really necessary? The problem
>is that libproxy has many important reverse dependencies and
>we can't build things like graphviz or SANE because of this
>issue.

http://snapshot.debian.org/archive/debian-ports/20140502T193204Z/pool-m68k/main/libp/libproxy/libproxy_0.4.11-4+m68k.1.dsc


libproxy (0.4.11-4+m68k.1) unreleased; urgency=low

  * Disable mozjs and Webkit on m68k, where they need major porting

 -- Thorsten Glaser <tg at mirbsd.de>  Fri, 02 May 2014 15:25:02 +0200


This is “good enough” for dependencies, anyway. No idea why it needs
them at run-time, though.

bye,
//mirabilos
-- 
This space for rent.