On Tue, Dec 8, 2009 at 1:54 PM, Richard Zhao <linux...@gmail.com> wrote:
> On Tue, Dec 8, 2009 at 1:03 PM, Antoine Labour <pi...@chromium.org> wrote:
>>
>>
>> On Mon, Dec 7, 2009 at 8:58 PM, Richard Zhao <linux...@gmail.com> wrote:
>>>
>>> On Tue, Dec 8, 2009 at 12:41 PM, Antoine Labour <pi...@chromium.org>
>>> wrote:
>>> >
>>> >
>>> > On Mon, Dec 7, 2009 at 8:35 PM, Richard Zhao <linux...@gmail.com> wrote:
>>> >>
>>> >> On Tue, Dec 8, 2009 at 11:41 AM, Antoine Labour <pi...@chromium.org>
>>> >> wrote:
>>> >> >
>>> >> >
>>> >> > On Mon, Dec 7, 2009 at 7:30 PM, Richard Zhao <linux...@gmail.com>
>>> >> > wrote:
>>> >> >>
>>> >> >> I found many places using -m32 cflags. but my gcc can recognize it.
>>> >> >> How do you compile?
>>> >> >
>>> >> > http://code.google.com/p/chromium/wiki/LinuxChromiumArm
>>> >> It's about cross-compile. I'm doing native compile.
>>> >
>>> > Good luck with that.
>>> > Chrome takes several gigabytes of RAM to link, and >15 minutes to link
>>> > on a
>>> > PC. It will take hours on any existing ARM machine.
>>> >
>>> >>
>>> >> Does
>>> >>    'disable_nacl': 1,
>>> >>    'use_system_ffmpeg' : '1',
>>> >> help?
>>> >
>>> > They will be needed, as well as target_arch=arm.
>>> >
>>> >>
>>> >> chromiumos.git/src/scripts/build_chrome.sh don't have this two define.
>>> >
>>> > Chromium OS doesn't yet build for ARM.
>>>
>>> I'm building chromiumos on arm ubuntu manually. Most things got from
>>> ubuntu arm repo.
>>> It seems chromiumos don't has ffmpeg package installed, so I don't
>>> need to add "'use_system_ffmpeg' : '1'"?
>>
>> If you don't set use_system_ffmpeg=1, the build system will try to build x86
>> assembly with and x86 assembler and it won't work.
>>
>>>
>>> What about disable_nacl?
>>
>> You need it as well.
>>
>>>
>>> I've substituted all -m32 with " ".
>>
>> Really, set target_arch=arm
>> That will fix your -m32 issues, as well as many others (like trying to
>> compile sse code).
>> Antoine
> export GYP_DEFINES="chromeos=1 target_arch=arm disable_nacl=1
> use_system_ffmpeg=1"
> It won't fix the -m32 issues.
Log:
  TOUCH 
out/Release/obj.target/third_party/WebKit/WebCore/WebCore.gyp/webcore_bindings_sources.stamp
  ACTION js2c_js2c out/Release/obj/gen/libraries.cc
  TOUCH out/Release/obj.host/v8/tools/gyp/js2c.stamp
  CXX(host) out/Release/obj.host/v8_nosnapshot/gen/libraries.o
cc1plus: error: unrecognized command line option "-m32"
make: *** [out/Release/obj.host/v8_nosnapshot/gen/libraries.o] Error 1

-- 
Chromium Developers mailing list: chromium-dev@googlegroups.com 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev

Reply via email to