Thanks for the replies. I don't know what happened... well, I'll rephrase 
that, I somehow created a directory called build/gyp_v8 , but I don't know 
how. Twice. (face palm) 
I've only been getting 3 or 4 hours sleep a day (sometimes two) trying to 
get a project started. That likely has a lot to do with it LOL
Anyways, figured it out that day, or night, or when ever.... oh yes, 6:30 
am. I guess it was morning.

On Sunday, December 16, 2012 6:36:47 AM UTC-8, [email protected] wrote:
>
> I followed everything correctly, and verified by browsing to the folder 
> that the file isnt there. Heres a dump of the dir:
>
>  Directory of C:\dev\svn\build\gyp_v8
>
> 12/16/2012  05:02 AM    <DIR>          .
> 12/16/2012  05:02 AM    <DIR>          ..
> 12/16/2012  05:02 AM                 6 .gitignore
> 12/16/2012  05:02 AM               190 AUTHORS
> 12/16/2012  05:02 AM    <DIR>          buildbot
> 12/16/2012  05:02 AM               358 codereview.settings
> 12/16/2012  05:02 AM               635 DEPS
> 12/16/2012  05:02 AM               466 gyp
> 12/16/2012  05:02 AM               194 gyp.bat
> 12/16/2012  05:02 AM             7,764 gyptest.py
> 12/16/2012  05:02 AM               190 gyp_dummy.c
> 12/16/2012  05:02 AM             1,475 LICENSE
> 12/16/2012  05:02 AM               463 MANIFEST
> 12/16/2012  05:02 AM                 2 OWNERS
> 12/16/2012  05:02 AM             2,919 PRESUBMIT.py
> 12/16/2012  05:02 AM    <DIR>          pylib
> 12/16/2012  05:02 AM            10,005 pylintrc
> 12/16/2012  05:02 AM    <DIR>          samples
> 12/16/2012  05:02 AM               788 setup.py
> 12/16/2012  05:02 AM    <DIR>          test
> 12/16/2012  05:02 AM    <DIR>          tools
>               14 File(s)         25,455 bytes
>                7 Dir(s)  62,618,566,656 bytes free
>
> What could I have done wrong? Using the ver of python downloaded from 
> google 'how to build v8' page. double checked and have redone everything 
> twice.
> Thanks
>

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

Reply via email to