Hi Yoann:

Unfortunately I keep getting the same error. When I set
CAN_USE_THUMB_INSTRUCTIONS symbol I can build the code but I cannot
run on mini2440 for some reason - says file not found meaning that it
cannot recognise the executable format.

Btw my linux flavour is Angstrom, and I build with GCC version 4.2.4.
I start to think that that might be related to the toolchain that I am
using although I can compile and run other apps without any problem.

Any other suggestions?

thanks.

On Sep 2, 1:53 am, Yoann Sculo <[email protected]> wrote:
> I've successfully built V8 for my Samsung S3C2440AL-40N
> Maybe my previous investigations will help you
>
> So, it works with these lines :
>
> export GCC_VERSION=44
> export CC="<path_to_your_crosschain>/arm-linux-gcc"
> export CXX="<path_to_your_crosschain>/arm-linux-g++"
>
> export CXXFLAGS="-I. -mcpu=arm920t"
> export CFLAGS="-I. -mcpu=arm920t"
>
> scons mode=release arch=arm library=shared prof=off os=linux
> profilingsupport=off snapshot=off
>
> I'm using a fake execinfo.h I just put at the root of the project to
> deal with backtrace errors during compiling.
>
> #ifndef _EXECINFO_H_
> #define _EXECINFO_H_ 1
>
> #include <sys/cdefs.h>
>
> __BEGIN_DECLS
>
> int backtrace(void**,int){ return 0; }
> char** backtrace_symbols(void* const*,int){return NULL; }
> void backtrace_symbols_fd(void* const*,int,int){}
>
> __END_DECLS
>
> #endif /* !_EXECINFO_H_ */
>
> And because I discovered a small bug in the code for ARM some weeks
> ago, it has been fixed in the 
> trunkhttp://groups.google.fr/group/v8-users/browse_thread/thread/8dd63321f...
> So you have to use the trunk to get the patch for arm
>
> I hope it will work for you
>
> Yoann
>
> On 2 sep, 00:43, Emre <[email protected]> wrote:
>
> > I get the following in that case:
>
> > /home/me/Dev/mini2440/oe/build/cross/armv4t/bin/arm-angstrom-linux-
> > gnueabi-gcc -o obj/release/dtoa-config.os -c -I. -march=armv4 -Werror -
> > Wno-uninitialized -O3 -fomit-frame-pointer -fdata-sections -ffunction-
> > sections -ansi -fPIC -DV8_TARGET_ARCH_ARM -DV8_SHARED -
> > DENABLE_VMSTATE_TRACKING -DENABLE_LOGGING_AND_PROFILING -
> > DENABLE_DEBUGGER_SUPPORT -Isrc src/dtoa-config.c
> > cc1: warnings being treated as errors
> > src/dtoa-config.c:1: warning: target CPU does not support interworking
> > scons: *** [obj/release/dtoa-config.os] Error 1
> > scons: building terminated because of errors.
>
> > On Sep 1, 2:51 pm, Rodolph Perfetta <[email protected]>
> > wrote:
>
> > > V8 does not support armv4t, but it does support armv4 so try -march=armv4
>
> > > On 1 September 2010 19:17, Emre <[email protected]> wrote:
>
> > > > Hi all:
>
> > > > I am trying to cross-compile V8 for friendlyArm (mini2440) board
> > > > (Samsung S3C2440). I get the following error:
>
> > > > /home/me/Dev/mini2440/oe/build/cross/armv4t/bin/arm-angstrom-linux-
> > > > gnueabi-g++ -o obj/release/arm/macro-assembler-arm.os -c -I. -
> > > > march=armv4t -Wall -Werror -W -Wno-unused-parameter -Wnon-virtual-dtor
> > > > -pedantic -O3 -fomit-frame-pointer -fdata-sections -ffunction-sections
> > > > -ansi -fno-rtti -fno-exceptions -fvisibility=hidden -Wall -Werror -W -
> > > > Wno-unused-parameter -Wnon-virtual-dtor -pedantic -O3 -fomit-frame-
> > > > pointer -fdata-sections -ffunction-sections -ansi -fPIC -
> > > > DV8_TARGET_ARCH_ARM -DV8_SHARED -DENABLE_VMSTATE_TRACKING -
> > > > DENABLE_LOGGING_AND_PROFILING -DENABLE_DEBUGGER_SUPPORT -Isrc src/arm/
> > > > macro-assembler-arm.cc
> > > > src/arm/macro-assembler-arm.cc:59:3: error: #error "For thumb inter-
> > > > working we require an architecture which supports blx"
> > > > scons: *** [obj/release/arm/macro-assembler-arm.os] Error 1
> > > > scons: building terminated because of errors.
>
> > > > I set CC, CXX, RANLIB and AR environment variables to point out the
> > > > armv4t toolchain. Also set CFLAGS and CXXFLAGS to "-I. -
> > > > march=armv4t".
>
> > > > Do you have any idea how I can fix that.
>
> > > >  Thanks in advance.
>
> > > > --
> > > > v8-users mailing list
> > > > [email protected]
> > > >http://groups.google.com/group/v8-users

-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users

Reply via email to