[OE-core] [PATCH 1/1] webkit-gtk: fix 'Memory exhausted' error

Paul Barker paul at paulbarker.me.uk
Wed Jul 24 08:31:16 UTC 2013


On 24 July 2013 08:49, Burton, Ross <ross.burton at intel.com> wrote:
> On 24 July 2013 03:19, Kang Kai <Kai.Kang at windriver.com> wrote:
>>> Instead of penalising everybody, would it be possible to make this
>>> change dependent on the build machine (ram + swap)? Or to only add
>>> -Wl,--no-keep-memory if the build failed without it?
>>
>> Yes, it doesn't fail on every build machine. But it seems that build fails
>> randomly on different build machines.
>
> I'm in agreement with the others - this is how individual build
> machine admins make a webkit-gtk build work on their machine if it
> doesn't have enough memory available.  We should probably document how
> to do this in local.conf in the recipe for reference, but not make it
> a default.
>

Perhaps create a bbclass for this that can be globally inherited in
local.conf? I ran into a similar thing with gnuradio and had to drop
PARALLEL_MAKE to get the build to complete with my amount of RAM+swap.
Something like "lean-build.bbclass" that handles known issues for
systems with limited memory.

Would variables like LDFLAGS_webkit-gtk and PARALLEL_MAKE_gnuradio be
applied to the appropriate recipes if they were set in local.conf or a
globally inherited bbclass, or am I misunderstanding how bitbake
parses variables?

--
Paul Barker

Email: paul at paulbarker.me.uk
http://www.paulbarker.me.uk



More information about the Openembedded-core mailing list