[webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted
Hi all, I am facing a problem while compiling the webkit-nightly build in debug mode. At the time of linking*(eg. CXXLD libwebkitgtk-3.0.la)*, it gets stopped with an error(*eg. /usr/bin/ld: failed to set dynamic section sizes: Memory exhausted)* What, I have tried: 1)By resizing the swappiness value(/proc/sys/vm/swappiness). 2)By creating a swap partition(eg. /mnt/512MiB.swap). But didn't get the problem resolved. Presently I have 4GB of main memory equipped. The same nightly build has no such an issue if debug mode is disabled. Please help me and let me know for a solution. Thanks Regards, Sanjeet ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted
I think you have to have at least 8 GiB of RAM (16 GiB is recommended) and 64-bit OS to compile webkit in debug mode. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted
Or you can add 8 GiB of swap, like I did before I upgraded my machine: https://lists.webkit.org/pipermail/webkit-help/2011-November/002678.html ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted
Hi John, Thanks for your instant response. But, I had been compiling webkit in debug mode earlier, with the same configurations with no such any error. And thats why I doubt whether increasing the RAM, is an proper and generic solution. Thanks, Sanjeet On Fri, Mar 23, 2012 at 3:18 PM, John Yani van...@gmail.com wrote: I think you have to have at least 8 GiB of RAM (16 GiB is recommended) and 64-bit OS to compile webkit in debug mode. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted
WebKit's codebase increases every day, so It's not strange that it requires more and more memory to link. On 23 March 2012 12:03, Sanjeet Pratap Singh sanjeetpratapsi...@gmail.com wrote: Hi John, Thanks for your instant response. But, I had been compiling webkit in debug mode earlier, with the same configurations with no such any error. And thats why I doubt whether increasing the RAM, is an proper and generic solution. Thanks, Sanjeet On Fri, Mar 23, 2012 at 3:18 PM, John Yani van...@gmail.com wrote: I think you have to have at least 8 GiB of RAM (16 GiB is recommended) and 64-bit OS to compile webkit in debug mode. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted
Hi Sanjeet, I can confirm that the memory is most likely the problem. Especially WebKit/WebCore is growing steadily, whenever code is being added. And with WebCore we (Qt) had the problem on mac of crossing the 4GB boundary just a few days ago. So it is very likely that other ports will experience similar problems. In our case we had to make use of some of the *AllInOne files. Because we are building WebCore as a static library. And on mac you currently can't build static libs 4GB at all it seems. Ranlib always crashes when trying to build the symbol table. This even affects 64bit systems with 12GB of ram. :-| Best Regards, Zeno On Fri, Mar 23, 2012 at 11:03 AM, Sanjeet Pratap Singh sanjeetpratapsi...@gmail.com wrote: Hi John, Thanks for your instant response. But, I had been compiling webkit in debug mode earlier, with the same configurations with no such any error. And thats why I doubt whether increasing the RAM, is an proper and generic solution. Thanks, Sanjeet On Fri, Mar 23, 2012 at 3:18 PM, John Yani van...@gmail.com wrote: I think you have to have at least 8 GiB of RAM (16 GiB is recommended) and 64-bit OS to compile webkit in debug mode. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted
This even affects 64bit systems with 12GB of ram. :-| So you're saying that you've tried to build webkit on 64bit system with 12GiB of RAM and failed? How much memory is used when build is not running? ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted
On Fri, Mar 23, 2012 at 11:14 AM, John Yani van...@gmail.com wrote: This even affects 64bit systems with 12GB of ram. :-| So you're saying that you've tried to build webkit on 64bit system with 12GiB of RAM and failed? How much memory is used when build is not running? Yes, this is a bug or undocumented limitation in ranlib/libtool i believe. I can reproduce it with any static library/archive that is 4GB. While building the archive itself works fine, ranlib fails to build a symbol table for the archive. So why is that not a problem for the Apple port? - Simple answer: They are building WebCore as a framework (dynamic library). :-) The available memory is for sure not the problem in my case. Because even when building/linking i still have about 6GB free (free+inactive). ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Problem In Compiling Webkit in Debug mode : failed to set dynamic section sizes: Memory exhausted
On Fri, 2012-03-23 at 12:08 +0200, John Yani wrote: WebKit's codebase increases every day, so It's not strange that it requires more and more memory to link. The maintainer of the WebKitGTK+ package in Ubuntu told me about a linker switch they are using to avoid problems when building in 32 bits systems: --no-keep-memory ld normally optimizes for speed over memory usage by caching the symbol tables of input files in memory. This option tells ld to instead optimize for memory usage, by rereading the symbol tables as necessary. This may be required if ld runs out of memory space while linking a large executable. Notice that that seems to only work for GNU ld - the gold linker has this as a no-op for compatibility only. Cheers, -- Gustavo Noronha Silva g...@gnome.org GNOME Project ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
