Someone mentioned to me that the bleeding_edge branch as i64 support,  
so I tried compiling that with the arch=x64 flag, but no such luck.  
Different error though:

[3][0] ~/scratch/v8-bleeding $ scons arch=x64
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
g++ -o obj/release/platform-macos.o -c -Wall -Werror -W -Wno-unused- 
parameter -pedantic -fno-strict-aliasing -O3 -fomit-frame-pointer - 
fdata-sections -ffunction-sections -ansi -mmacosx-version-min=10.4 - 
m64 -fno-rtti -fno-exceptions -Wall -Werror -W -Wno-unused-parameter - 
pedantic -fno-strict-aliasing -O3 -fomit-frame-pointer -fdata-sections  
-ffunction-sections -ansi -mmacosx-version-min=10.4 -m64 - 
DV8_TARGET_ARCH_X64 -DENABLE_LOGGING_AND_PROFILING -Isrc src/platform- 
macos.cc
In file included from src/platform-macos.cc:31:
/usr/include/ucontext.h:42:2: error: #error ucontext routines are  
deprecated, and require _XOPEN_SOURCE to be defined
scons: *** [obj/release/platform-macos.o] Error 1
scons: building terminated because of errors.

I get the same error if I add the "-arch i386" error to the gcc  
"CCFLAGS" in the SConstruct file, but compilation does get a lot  
further than before.

On Jul 16, 2009, at 2:16 AM, Stephan Beal wrote:

> On Thu, Jul 16, 2009 at 3:23 AM, Tom Robinson <tlrobin...@gmail.com>  
> wrote:
> #define __amd64 1
>
> According to the v8 home page, i32 and ARM are supported, but not  
> i64. Then again, the wording is a bit ambiguous:
>
>
> "...runs on Windows XP and Vista, Mac OS X 10.5 (Leopard), and Linux  
> systems that use IA-32 or ARM processors."
>
> which could be interpreted to mean that only the Linux ports have  
> that limitation, whereas Win/Mac don't (but i doubt that's the  
> intention of the text).
>
> :-?
>
> -- 
> ----- stephan beal
> http://wanderinghorse.net/home/stephan/
>
> >


--~--~---------~--~----~------------~-------~--~----~
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to