I have the same version of Xcode you do.  However, it's not clear the assembler 
you have is the x86_64 version.  It may be a 64 bit binary executable that 
generates 32 bit code…

I suggest you try doing a command line build of v8, which I assure you works 
with the Xcode tools I have installed.

something like:

$ svn checkout http://v8.googlecode.com/svn/trunk/ v8-read-only
$ cd v8-read-only
$ make dependencies
$ GYP_GENERATORS=make make x64.release library=shared

Or even try compiling hello.cpp:

// hello.cpp
#include <stdio.h>
int main(int ac, char *av[]) {
  printf("Hello, world\n");
}

$ g++ hello.cpp

(see if it complains about missing assembler)

Normally the toolchain does  a few passes (separate tools/commands) on your 
source code to make a .o:
1) pass 1: C/C++ preprocessor
2) pass 2: compile C/C++ to assembly language
3) pass 3: run assembly language through assembler to generate the .o

Pass 3 allows a MIPS processor, ARM processor, X86/32, X86/64, etc., code 
generator to be used interchangeably, and to facilitate cross compiling 
(generate ARM binary on your X86 linux/OSX system).

The g++ command (or gcc command) is going to run those behind the scenes for 
you.  The error message in your output says "can't find assembler to generate 
x64 .o files" (rough translation)

Another thought is maybe you have homebrew or some other package installation 
system that has installed a toolchain in parallel to Xcode and the paths are 
screwed up.




On Aug 13, 2013, at 10:20 AM, Jim Acquavella <[email protected]> wrote:

> Hi Michael.  I have the assembler and it even has the x86_64 architecture:
> 
> jacquave-MacPro:4.2.1 jacquave$ pwd
> /Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1
> jacquave-MacPro:4.2.1 jacquave$ lipo as -info
> Non-fat file: as is architecture: x86_64
> jacquave-MacPro:4.2.1 jacquave$ as -v
> Apple Inc version cctools-839, GNU assembler version 1.38
> 
> Are you using XCode?  If so which version?  And which version of as do you 
> have?
> 
> 
> On Mon, Aug 12, 2013 at 6:05 PM, Michael Schwartz <[email protected]> wrote:
> Looks to me like your command line tools aren't installed properly or 
> something's erased one of the files or broken one of the filesystem soft/hard 
> links.
> 
> This is what I have on my system.
> 
> The error message in your compilation said "no assemblers installed" so it 
> could not find "as"
> 
> mschwartz@dionysus:~$ ls -l 
> /Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/as
> lrwxr-xr-x  1 root  wheel  21 Jul 25  2012 
> /Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/as
>  -> ../../../../../bin/as
> 
> 
> On Aug 8, 2013, at 1:34 PM, Jim Acquavella <[email protected]> wrote:
> 
>> /Applications/Xcode.app/Contents/Developer/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/as
> 
> 
> -- 
> -- 
> v8-users mailing list
> [email protected]
> http://groups.google.com/group/v8-users
> --- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "v8-users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/v8-users/UnNwhqKhARk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  
> 
> 
> -- 
> -- 
> v8-users mailing list
> [email protected]
> http://groups.google.com/group/v8-users
> --- 
> You received this message because you are subscribed to the Google Groups 
> "v8-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to