From: Phil Blundell <pb@pbcl.net>
To: "André Draszik" <andre.draszik@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] webkit-gtk: fix 'Memory exhausted' error
Date: Mon, 22 Jul 2013 10:48:14 +0100 [thread overview]
Message-ID: <1374486494.6324.44.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <1374481350.6719.83.camel@bril0118.bri.st.com>
Agreed, I think this sort of thing belongs in site.conf or some such
place, not in the recipe.
p.
On Mon, 2013-07-22 at 09:22 +0100, André Draszik wrote:
> Hi,
>
> 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?
>
> Not sure if it would make any difference, but do you see this only with
> full debug enabled (-ggdb)? If yes, can the debug flags be changed, or
> that linker flag only be added, if full debug is enabled?
>
>
> Cheers,
> Andre'
>
> On Mon, 2013-07-22 at 15:51 +0800, Kai Kang wrote:
> > Build webkit-gtk occupies lot of memory and fails on some host:
> > | ...tmp/sysroots/i686-linux/usr/libexec/x86_64-wrs-linux/gcc/x86_64-wrs-linux/4.8.1/ld:
> > failed to set dynamic section sizes: Memory exhausted
> > | collect2: error: ld returned 1 exit status
> > | make[1]: *** [libwebkitgtk-1.0.la] Error 1
> >
> > Add ld option to fix it.
> >
> > Refer to:
> > http://comments.gmane.org/gmane.os.opendarwin.webkit.devel/20078
> >
> > Signed-off-by: Kai Kang <kai.kang@windriver.com>
> > ---
> > meta/recipes-sato/webkit/webkit-gtk_1.8.3.bb | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/recipes-sato/webkit/webkit-gtk_1.8.3.bb b/meta/recipes-sato/webkit/webkit-gtk_1.8.3.bb
> > index 5691d3f..90625a3 100644
> > --- a/meta/recipes-sato/webkit/webkit-gtk_1.8.3.bb
> > +++ b/meta/recipes-sato/webkit/webkit-gtk_1.8.3.bb
> > @@ -60,6 +60,8 @@ CPPFLAGS_append_powerpc = " -I${STAGING_INCDIR}/pango-1.0 \
> >
> > EXTRA_AUTORECONF = " -I Source/autotools "
> >
> > +# Fix compile error: "ld: failed to set dynamic section sizes: Memory exhausted"
> > +LDFLAGS += " -Wl,--no-keep-memory"
> >
> > #| ./Source/JavaScriptCore/heap/HandleTypes.h: In static member function 'static T* JSC::HandleTypes<T>::getFromSlot(JSC::HandleSlot) [with T = JSC::Structure, JSC::HandleTypes<T>::ExternalType = JSC::Structure*, JSC::HandleSlot = JSC::JSValue*]':
> > #| ./Source/JavaScriptCore/heap/Handle.h:141:79: instantiated from 'JSC::Handle<T>::ExternalType JSC::Handle<T>::get() const [with T = JSC::Structure, JSC::Handle<T>::ExternalType = JSC::Structure*]'
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2013-07-22 9:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 7:51 [PATCH 0/1] Fix webkit-gtk 'Memory Exhaust' issue Kai Kang
2013-07-22 7:51 ` [PATCH 1/1] webkit-gtk: fix 'Memory exhausted' error Kai Kang
2013-07-22 8:22 ` André Draszik
2013-07-22 9:48 ` Phil Blundell [this message]
2013-07-24 2:19 ` Kang Kai
2013-07-24 7:49 ` Burton, Ross
2013-07-24 8:31 ` Paul Barker
2013-07-24 9:47 ` Phil Blundell
2013-07-25 4:58 ` Randy MacLeod
2013-07-25 5:53 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1374486494.6324.44.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--cc=andre.draszik@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox