2009/12/10 Sofia Tahseen <sofia.tahs...@gmail.com>:
> You are so right, Joel... I corrected my .so and now I could build the
> chrome browser ...finally!!  I copied the whole /src/out/Release directory
> to my jaunty on the BeagleBoard(256MB RAM). I try to launch chrome through:
> ./chrome
> It starts up chrome, and then immediately kills chrome. I get an Illegal
> Instruction. I restart and I can now see chrome as shown in the attachment
> but I cannot browse. When I reload the page, it again kills chrome saying
> Illegal instruction. Has anyone seen this before? I have my proxy settings
> set too..

This could be anything, but it might be this bug in some versions of
gcc:  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39604

If that's it then adding -fno-tree-sink to the flags used for V8 will
help.  It's a bug that only shows up on ARM and only on some versions
of gcc.



> Any help is highly appreciated.
> Thanks,
> Sofia
>
> On Wed, Dec 9, 2009 at 6:00 PM, Joel Stanley <j...@chromium.org> wrote:
>>
>> On Thu, Dec 10, 2009 at 05:14, Sofia Tahseen <sofia.tahs...@gmail.com>
>> wrote:
>>
>> >
>> > /home/adas/0_Data/0_Lin/091203_Chromium_OS/toolchain/arm-2009q1/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.3/../../../../arm-none-linux-gnueabi/bin/ld:
>> > skipping incompatible
>> >
>> > /home/adas/x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sys-root/usr/lib/librt.so
>> > when searching for -lrt
>>
>> The errors are indicative of trying to link against libraries from a
>> different platform.  To confirm: check the output of
>>
>>  $ 'file
>> /home/adas/x-tools/arm-unknown-linux-gnueabi/arm-unknown-linux-gnueabi/sys-root/usr/lib/librt.so
>>
>> I suspect it will tell you it's a symbolic link to /lib/librt.so.1,
>> which itself is a symbolic link to
>> /lib/librt-2.10.2.so - note these paths are relative to /, not to your
>> sysroot directory.
>>
>> You have two slightly solutions
>>  - adjust the symlinks in sys-root/usr/lib so they point to the files
>> in sys-root//lib
>>  - replace the smymlinks with the actual libraries, ie copy files from
>> sys-root/lib to sys-root/usr/lib
>>
>> I would be happy to hear a neater solution for this, but the above
>> worked for me.
>>
>> Cheers,
>>
>> Joel
>
> --
> Chromium Developers mailing list: chromium-dev@googlegroups.com
> View archives, change email options, or unsubscribe:
> http://groups.google.com/group/chromium-dev

-- 
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