Bug 1363 - webkit build fail when cross-compile x86_64 target on i686 host
Summary: webkit build fail when cross-compile x86_64 target on i686 host
Status: RESOLVED WONTFIX
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.0-alpha
Hardware: x86 x86_64
: Medium normal
Target Milestone: 1.1
Assignee: Edwin Zhai
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-08-11 04:50 UTC by Edwin Zhai
Modified: 2011-08-18 21:49 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments
Build log from webkit-gtk-1.5.1+svnr90727-r0 (98.63 KB, application/octet-stream)
2011-08-11 04:50 UTC, Edwin Zhai
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Edwin Zhai 2011-08-11 04:50:34 UTC
Created attachment 203 [details]
Build log from webkit-gtk-1.5.1+svnr90727-r0

When cross-compile x86_64 target on i686 host, webkit-gtk build fail when do_install.

"x86_64-poky-linux-g++: error: ./.libs/libWebCore.a: Value too large for
defined data type", where libWebCore.a is ~ 2.5G.
Then x86_64-poky-linux-g++ complains about the big file when link the final
libwebkitgtk-1.0.so...

This bug only occurs when we cross-compile x86-64 target on
i686.  On my x86-64 host, or mips/arm on i686 host, everything runs well.

Attached log from Lei's machine.
Comment 1 Edwin Zhai 2011-08-11 05:00:58 UTC
Another tricky thing is: running script run.do_install from source directory
can work, but bitbake webkit-gtk always fail when install. I have checked both
use same command line, and share same ulimit.

It's caused by memory limitation on i686 host. Build chromium(also linked with
webkit) has same issue. Community suggestion is using x86-64 host: 

"This typically happens with 32bit linkers when building with debugging
symbols, they'll exhaust their address space when linking chrome. Switching to
a 64bit system or doing a release build will likely fix the issue."

I'd like to mark it as won't fix, and identify it as known issue.