Re: [v8-users] Building v8 without PIC

[Jakob Kummerow]

I'm afraid those flags are not configurable. You'll have to edit
build/config/compiler/BUILD.gn (for -fPIC) and build/config/gcc/BUILD.gn and
gni/v8.gni (for -pie) -- but none of the BUILD.gn files under src :-)

Note that this is entirely independent of how you build V8; gm.py has
nothing to do with it.

Obviously, if this leads to strange issues, you're on your own -- hacking
the build files with your custom settings is officially unsupported. Good
luck!


On Wed, Jul 3, 2019 at 1:17 AM Noah Cantor  wrote:

> My project builds v8 via gm.py. Is there a way to get it to build non-PIC
> (i.e. without -fPIC and -pie flags) without modifying all the BUILD.gn
> files under src?
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/v8-users/bc6c0edb-aa77-46e2-8d00-e2dda1be4eff%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-users/CAKSzg3RsF9wAn2WTj9DWCiMyiPynxjJKfohmK%3DRDWP5y5xD6kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8

[Rodolph Perfetta]

Have you tried using linux on windows with WSL:
https://docs.microsoft.com/en-us/windows/wsl/about ?

On Tue, 26 Mar 2019 at 11:01, Marto Parts  wrote:

> Yeah I have also a 64 bit machine but it is Windows and i wasn’t able to
> build it over there since the documentation is sparse and doesn’t work
> otherwise I will be happy to run it in the 64bit machine
>
> On Tue, 26 Mar 2019 at 15:19, Rodolph Perfetta 
> wrote:
>
>> You can build a 32-bit v8 binary on a 64-bit machine and the resulting
>> binary will run on a 32-bit machine.
>>
>> If you need to build on a 32-bit machine, then it is more involved and
>> not officially documented. As said earlier this will likely require you to
>> install tools, update config and scripts.
>>
>> On Tue, 26 Mar 2019 at 09:00, Marto Parts  wrote:
>>
>>> So long story short I can’t run v8 cause of 32 bit ?
>>>
>>> On Tue, 26 Mar 2019 at 00:27, Rodolph Perfetta <
>>> rodolph.perfe...@gmail.com> wrote:
>>>
 To use the bundled tools, you need a 64-bit machine.

 if this is not an option you could try installing all the dependencies
 yourself (and disabling the use of bundled tools by specifying
 is_clang=false and probably more), but I don't believe this is documented.

 On Mon, 25 Mar 2019 at 17:36,  wrote:

> I'm currently trying to build V8 for debug purposes on a Xubuntu
> machine (32 bit)
> Cloned the depot tools
> fetched V8 in a new folder
> and gclient sync but can't execute it or  build it with GN as it says
> it is missing.
> Wasn't able to find a *single *working documentation on the entire
> process.
>
> If someone could provide any tips and maybe on how to execute scripts
> so it happens something like this
> pass V8 a script to execute (JS file) and then attach to that process
> with a debugger, problem is can't launch it ..
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 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 v8-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>> --
>>> v8-users mailing list
>>> v8-users@googlegroups.com
>>> 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 v8-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> 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 v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8

[Marto Parts]

Yeah I have also a 64 bit machine but it is Windows and i wasn’t able to
build it over there since the documentation is sparse and doesn’t work
otherwise I will be happy to run it in the 64bit machine

On Tue, 26 Mar 2019 at 15:19, Rodolph Perfetta 
wrote:

> You can build a 32-bit v8 binary on a 64-bit machine and the resulting
> binary will run on a 32-bit machine.
>
> If you need to build on a 32-bit machine, then it is more involved and not
> officially documented. As said earlier this will likely require you to
> install tools, update config and scripts.
>
> On Tue, 26 Mar 2019 at 09:00, Marto Parts  wrote:
>
>> So long story short I can’t run v8 cause of 32 bit ?
>>
>> On Tue, 26 Mar 2019 at 00:27, Rodolph Perfetta <
>> rodolph.perfe...@gmail.com> wrote:
>>
>>> To use the bundled tools, you need a 64-bit machine.
>>>
>>> if this is not an option you could try installing all the dependencies
>>> yourself (and disabling the use of bundled tools by specifying
>>> is_clang=false and probably more), but I don't believe this is documented.
>>>
>>> On Mon, 25 Mar 2019 at 17:36,  wrote:
>>>
 I'm currently trying to build V8 for debug purposes on a Xubuntu
 machine (32 bit)
 Cloned the depot tools
 fetched V8 in a new folder
 and gclient sync but can't execute it or  build it with GN as it says
 it is missing.
 Wasn't able to find a *single *working documentation on the entire
 process.

 If someone could provide any tips and maybe on how to execute scripts
 so it happens something like this
 pass V8 a script to execute (JS file) and then attach to that process
 with a debugger, problem is can't launch it ..

 --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 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 v8-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>> --
>>> v8-users mailing list
>>> v8-users@googlegroups.com
>>> 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 v8-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> 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 v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8

[Rodolph Perfetta]

You can build a 32-bit v8 binary on a 64-bit machine and the resulting
binary will run on a 32-bit machine.

If you need to build on a 32-bit machine, then it is more involved and not
officially documented. As said earlier this will likely require you to
install tools, update config and scripts.

On Tue, 26 Mar 2019 at 09:00, Marto Parts  wrote:

> So long story short I can’t run v8 cause of 32 bit ?
>
> On Tue, 26 Mar 2019 at 00:27, Rodolph Perfetta 
> wrote:
>
>> To use the bundled tools, you need a 64-bit machine.
>>
>> if this is not an option you could try installing all the dependencies
>> yourself (and disabling the use of bundled tools by specifying
>> is_clang=false and probably more), but I don't believe this is documented.
>>
>> On Mon, 25 Mar 2019 at 17:36,  wrote:
>>
>>> I'm currently trying to build V8 for debug purposes on a Xubuntu machine
>>> (32 bit)
>>> Cloned the depot tools
>>> fetched V8 in a new folder
>>> and gclient sync but can't execute it or  build it with GN as it says it
>>> is missing.
>>> Wasn't able to find a *single *working documentation on the entire
>>> process.
>>>
>>> If someone could provide any tips and maybe on how to execute scripts so
>>> it happens something like this
>>> pass V8 a script to execute (JS file) and then attach to that process
>>> with a debugger, problem is can't launch it ..
>>>
>>> --
>>> --
>>> v8-users mailing list
>>> v8-users@googlegroups.com
>>> 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 v8-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> 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 v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8

[Marto Parts]

So long story short I can’t run v8 cause of 32 bit ?

On Tue, 26 Mar 2019 at 00:27, Rodolph Perfetta 
wrote:

> To use the bundled tools, you need a 64-bit machine.
>
> if this is not an option you could try installing all the dependencies
> yourself (and disabling the use of bundled tools by specifying
> is_clang=false and probably more), but I don't believe this is documented.
>
> On Mon, 25 Mar 2019 at 17:36,  wrote:
>
>> I'm currently trying to build V8 for debug purposes on a Xubuntu machine
>> (32 bit)
>> Cloned the depot tools
>> fetched V8 in a new folder
>> and gclient sync but can't execute it or  build it with GN as it says it
>> is missing.
>> Wasn't able to find a *single *working documentation on the entire
>> process.
>>
>> If someone could provide any tips and maybe on how to execute scripts so
>> it happens something like this
>> pass V8 a script to execute (JS file) and then attach to that process
>> with a debugger, problem is can't launch it ..
>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> 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 v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8

[Rodolph Perfetta]

To use the bundled tools, you need a 64-bit machine.

if this is not an option you could try installing all the dependencies
yourself (and disabling the use of bundled tools by specifying
is_clang=false and probably more), but I don't believe this is documented.

On Mon, 25 Mar 2019 at 17:36,  wrote:

> I'm currently trying to build V8 for debug purposes on a Xubuntu machine
> (32 bit)
> Cloned the depot tools
> fetched V8 in a new folder
> and gclient sync but can't execute it or  build it with GN as it says it
> is missing.
> Wasn't able to find a *single *working documentation on the entire
> process.
>
> If someone could provide any tips and maybe on how to execute scripts so
> it happens something like this
> pass V8 a script to execute (JS file) and then attach to that process with
> a debugger, problem is can't launch it ..
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Makefile

[madana gopal]

Thanks for details Jakob and Peter.
 

> Node has been using Makefile mechanism. I am interested to use ninja 
> mechanism here and trying it out first. With use_sysroot = false, is it 
> possible to explicitly mention alternate sysroot path as part of ninja 
> build? Please let me know.


Thanks.

Regards,
Madan 

 

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Makefile

[Peter Schow]

Node has been built with yocto, correct?  You may want to see see how
the Node yocto recipe(s) work, and see if someone has already done the
heavy-lifting for V8.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Makefile

[Jakob Kummerow]

You can put:

is_clang = false
use_sysroot = false

into args.gn to make the V8 build use your system toolchain and libraries
instead of the bundled ones.

On Mon, Nov 12, 2018 at 9:18 PM madana gopal 
wrote:

> Hi,
>
> Also, v8 is using its own toolchain for arm,mips  etc, and we have
> toolchain already present as part of our yocto build system.So, do we have
> any way to make v8 build to point to our own toolchain?. please clarify.
>
> Thanks.
>
> Regards,
> Madan
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Makefile

[madana gopal]

Hi,

Also, v8 is using its own toolchain for arm,mips  etc, and we have 
toolchain already present as part of our yocto build system.So, do we have 
any way to make v8 build to point to our own toolchain?. please clarify.

Thanks.

Regards,
Madan

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Makefile

[Jakob Kummerow]

Ninja is the only officially supported build system for V8.

I don't know the requirements of the yocto build system. If all you need is
a wrapper, it should be very straightforward to create a two-liner Makefile
that invokes the GN/ninja based build.

If you need to replace GN/ninja entirely, you'll have to create a complete
Makefile yourself. I'm not aware of any existing tool to do this directly;
however the Node.js project maintains GYP files for V8, and one can
generate Makefiles from those, so that path might be worth looking into.
It's also certainly possible to create a tool yourself that generates
Makefiles from GN files, but that's probably quite a bit of work.


On Sun, Nov 11, 2018 at 6:30 PM madana gopal 
wrote:

> Hi Team,
>
> I am trying to prepare a build for v8 in yocto build system. I saw v8 is
> using ninja. Can we generate Makefile for v8 instead of ninja file?.
>
> If so, please share the steps.
>
> Thanks.
>
> Regards,
> Madan
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 as a static library generates build errors, but ptoduces usable libraries

[A.M.]

On Thursday, 3 May 2018 12:44:14 UTC-4, Ben Noordhuis wrote:
>
> V8 by default links statically against the bundled libc++ in 
> buildtools/third_party/libc++ but dynamically against libc, librt, 
> etc. 
>

Hmm... seeing how `v8.h` includes `memory`, it could cause problems 
regardless of whether it's a static build or not if the v8 itself was built 
against `buildtools/third_party/libc++` and the project including `v8.h` 
included `memory` from the standard include path. I guess I will cross this 
Rubicon when I get there. It's good to know about the bundled `libc++`. 

Thanks again for your insights, Ben.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 as a static library generates build errors, but ptoduces usable libraries

[Ben Noordhuis]

On Wed, May 2, 2018 at 11:27 PM, A.M.  wrote:
> On Saturday, 28 April 2018 05:30:17 UTC-4, Ben Noordhuis wrote:
>>
>> the CRT linking logic is effectively hard-coded in
>> build/config/win/BUILD.gn; look for 'default_crt'.  You could try
>> sending a CL that adds a build flag to override the default or simply
>> patch the file locally.
>
>
> Ben, thank you for pointing out where to change the CRT type in the GN
> build. You saved me a ton of time trying to figure out how to do it. After
> spending a few hours trying to isolate memory allocations in a large app I
> ended up changing `default_crt` to `dynamic_crt` and it's working fine in
> all of my tests.
>
> The application I'm working on is a Windows app, but it will be ported to
> Linux at some point. Do you know if the static v8 libraries link against a
> static `libstdc++` or any other critical libraries like this one? Thanks,
> again.

V8 by default links statically against the bundled libc++ in
buildtools/third_party/libc++ but dynamically against libc, librt,
etc.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 as a static library generates build errors, but ptoduces usable libraries

[A.M.]

On Saturday, 28 April 2018 05:30:17 UTC-4, Ben Noordhuis wrote:
>
> the CRT linking logic is effectively hard-coded in 
> build/config/win/BUILD.gn; look for 'default_crt'.  You could try 
> sending a CL that adds a build flag to override the default or simply 
> patch the file locally. 
>

Ben, thank you for pointing out where to change the CRT type in the GN 
build. You saved me a ton of time trying to figure out how to do it. After 
spending a few hours trying to isolate memory allocations in a large app I 
ended up changing `default_crt` to `dynamic_crt` and it's working fine in 
all of my tests.

The application I'm working on is a Windows app, but it will be ported to 
Linux at some point. Do you know if the static v8 libraries link against a 
static `libstdc++` or any other critical libraries like this one? Thanks, 
again. 


-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 as a static library generates build errors, but ptoduces usable libraries

[A.M.]

On Monday, 30 April 2018 10:16:10 UTC-4, Ben Noordhuis wrote:

> Node.js doesn't use GN.  It uses a monolithic GYP build that links 
> everything together with /MT.
>

Never had to look inside node-gyp/Node.lib before and was wondering how one 
of the apps I was working on links against the dynamic VC++ CRT and 
realized that Node.lib an import library and everything is exported from 
node.exe, so modules are free to use whatever option they need. I see now 
how /MT is working out for Node. 

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 as a static library generates build errors, but ptoduces usable libraries

[A.M.]

On Monday, 30 April 2018 10:16:10 UTC-4, Ben Noordhuis wrote:
>
> Node.js doesn't use GN.  It uses a monolithic GYP build that links 
> everything together with /MT.
>

Interesting. Didn't know that. Thanks for pointing out. 

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 as a static library generates build errors, but ptoduces usable libraries

[Ben Noordhuis]

On Mon, Apr 30, 2018 at 3:25 PM, A.M.  wrote:
> Node.js is not suffering from this because it's using the component build,
> which uses a CRT in a DLL

Node.js doesn't use GN.  It uses a monolithic GYP build that links
everything together with /MT.  (And yes, it's not without its
downsides, too.)

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 as a static library generates build errors, but ptoduces usable libraries

[A.M.]

> Dynamically linking to the CRT there doesn't gain you much

Not sure what you mean. Linking in dynamic CRT gives you so much that one 
should even consider whether to even work with a statically-linked CRT for 
any large project. The biggest issue is the heap CRT uses - if a project 
uses multiple DLLs, which is pretty much the norm for any large project, 
then the code linking against static v8 libraries must also use static CRT, 
which means that it cannot share memory allocations with the rest of the 
code, which in turn means I cannot even pass around things like 
`std::string` between these DLLs because if memory is moved to a string 
constructed in another DLL, it will just corrupt memory. There are other 
reasons as well, but this one is significant on its own and the bottom line 
that one has to design a whole interface to move things carefully across 
the boundary of such DLL. Not a trivial task. 

> Node.js) rather than a standalone library.

Node.js is not suffering from this because it's using the component build, 
which uses a CRT in a DLL


-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 as a static library generates build errors, but ptoduces usable libraries

[Ben Noordhuis]

On Sat, Apr 28, 2018 at 7:25 PM, A.M.  wrote:
> Thanks for responding, Ben. Your feedback is always appreciated.
>
>> but apropos (2),
>> the CRT linking logic is effectively hard-coded in
>> build/config/win/BUILD.gn;
>
> This is surprising - it makes the static build of v8 quite expensive and
> error-prone to maintain for a multi-DLL project, given that hundreds of
> implementation callbacks would have to be implemented with `extern "C"`
> linkage, as none of the STL, etc stuff can be shared between DLLs.
>
>> You could try
>> sending a CL that adds a build flag to override the default or simply
>> patch the file locally.
>
> If this is hard-coded in this day and age, it makes me think that Google did
> it for a reason that I may not realize until I'm too deep into the project.
>
> May be I should switch to Chakra for this project. It's not as fast as the
> v8, but there will be no compatibility issues when running multi-threaded
> JavaScript within a Node process.

The reason is probably that V8 is designed to be shipped as part of a
monolithic binary (Chromium, Node.js) rather than a standalone
library.

Dynamically linking to the CRT there doesn't gain you much and you
lose some in predictability and reproducibility.  From a QA
perspective, it's great to have full control over all your components.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 as a static library generates build errors, but ptoduces usable libraries

[A.M.]

Thanks for responding, Ben. Your feedback is always appreciated. 

> but apropos (2), 
> the CRT linking logic is effectively hard-coded in 
> build/config/win/BUILD.gn;

This is surprising - it makes the static build of v8 quite expensive and 
error-prone to maintain for a multi-DLL project, given that hundreds of 
implementation callbacks would have to be implemented with `extern "C"` 
linkage, as none of the STL, etc stuff can be shared between DLLs. 

> You could try 
> sending a CL that adds a build flag to override the default or simply 
> patch the file locally.

If this is hard-coded in this day and age, it makes me think that Google 
did it for a reason that I may not realize until I'm too deep into the 
project. 

May be I should switch to Chakra for this project. It's not as fast as the 
v8, but there will be no compatibility issues when running multi-threaded 
JavaScript within a Node process. 

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 as a static library generates build errors, but ptoduces usable libraries

[Ben Noordhuis]

On Sat, Apr 28, 2018 at 1:06 AM, A.M.  wrote:
> I have two questions related to building the v8 as a static library.
>
> 1. I'm building on Windows and the build fails very close to the end with
> this output:
>
> ninja -C out.gn/x64.debug
> ninja: Entering directory `out.gn/x64.debug'
> [1/1] Regenerating ninja files
> [1441/1543] LINK unittests.exe unittests.exe.pdb
> FAILED: unittests.exe unittests.exe.pdb
> C:/dev/v8/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe
> ../../build/toolchain/win/tool_wrapper.py
> link-wrapper environment.x64 False link.exe /nologo /OUT:./unittests.exe
> /PDB:./unittests.exe.pdb @./unittests.exe.rsp
> LINK : warning LNK4001: no object files specified; libraries used
> LINK : error LNK1218: warning treated as error; no output file generated
> [1446/1543] CXX obj/test/cctest/cctest_sources/test-code-generator.obj
> ninja: build stopped: subcommand failed.Enter code here...
>
> Apparently, no object files were supplied to the linker, only libraries,
> which is a warnings, but warnings are treated as errors, hence it fails the
> build. By the time it reaches this point, all v8 libraries are built, so I
> can use the v8 for my purposes, but it would be nice if it built as it is
> supposed to.
>
> Anybody has any idea how to remedy this problem?
>
> 2. Static v8 libraries are build against static VC++ CRT (i.e. with the
> `/MT` and `/MTd` flags), which means that they will not pick up any security
> updates from MS and also that the project cannot share memory C++
> allocations (i.e. `malloc`/`operator new`), CRT callbacks and some other
> things with the rest of the code, so it would need to be completely
> encapsulated within its own DLL. I found a really old thread from 2012:
>
> https://groups.google.com/forum/#!topic/v8-users/PpA3mhICTiM
>
> , but it's just too old to be of any significance.
>
> Is there a way to build v8 static libraries against VC++ DLL CRT (i.e. with
> `/MD` and `/MDd` flags)?
>
> Thanks!

I don't know about (1), haven't run into that myself, but apropos (2),
the CRT linking logic is effectively hard-coded in
build/config/win/BUILD.gn; look for 'default_crt'.  You could try
sending a CL that adds a build flag to override the default or simply
patch the file locally.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] building V8 for Android on Mac or ubuntu w static libs?

[Mindy DelliCarpini]

In case the issue is this, I'm running El Capitan 10.11.6

On Saturday, December 24, 2016 at 12:04:00 PM UTC-8, Mindy DelliCarpini 
wrote:
>
> Ok so did this to the .gclient file 1 directory up:
> solutions = [
>   {
> "url": "https://chromium.googlesource.com/v8/v8.git;,
> "managed": False,
> "name": "v8",
> "deps_file": "DEPS",
> "custom_deps": {},
> "target_os" : ['android', 'mac']
>   },
> ]
>
> Then: gclient sync
> Then  tools/dev/v8gen.py arm.release
>
> Then this in args.gn
> is_debug = false
> target_cpu = "arm"
> v8_target_cpu = "arm"
> target_os="android"
>
> Then:
>
> ninja -C out.gn/arm.release/
>
>
> This error persists:
>
> mindyp-macbookpro:v8 mindyp$ ninja -C out.gn/arm.release/
>
> ninja: Entering directory `out.gn/arm.release/'
>
> [1/1] Regenerating ninja files
>
> FAILED: build.ninja 
>
> /Users/mindyp/local/src/v8/buildtools/mac/gn 
> --root=/Users/mindyp/local/src/v8 -q --check gen .
>
> ERROR Unresolved dependencies.
>
> //:run_mkpeephole(//build/toolchain/android:android_arm)
>
>   needs //:mkpeephole(//build/toolchain/mac:clang_x86_v8_arm)
>
> //:run_mksnapshot(//build/toolchain/android:android_arm)
>
>   needs //:mksnapshot(//build/toolchain/mac:clang_x86_v8_arm)
>
>
> ninja: error: rebuilding 'build.ninja': subcommand failed
>
> [1]+  Donemate ../.gclient
>
>
>
>
>
>
> On Thursday, December 22, 2016 at 11:46:38 PM UTC-8, Jochen Eisinger wrote:
>>
>> hey,
>>
>> to build for android, you should add target_os = "android" and target_cpu 
>> = "arm".
>>
>> you'll also have to add target_os = ['android', 'mac'] to your .gclient 
>> file (which should be one level up from your v8 checkout), so gclient sync 
>> will download the android specific deps
>>
>> hth
>> -jochen
>>
>> On Thu, Dec 22, 2016 at 5:41 PM 'Mindy DelliCarpini' via v8-users <
>> v8-u...@googlegroups.com> wrote:
>>
>>> Need a V8 build for our prototyping tool (boom.googleplex.com). The 
>>> tool runs with a Mac simulator, so the build has to be completed on a Mac.
>>>
>>> The TOT v8 builds are broken for Mac, and also for building static full 
>>> libraries (no the thin .a files, which wouldn't be shareable)
>>>
>>> I'm interested in getting any of the following working (preference for 
>>> Mac build, but I know its not a common thing)
>>>
>>> 1) *Build v8 on my mac*
>>> Tried old instructions, but failed with missing libraries (standard c++?)
>>> https://github.com/v8/v8/wiki/D8-on-Android
>>> Tried new instructions:
>>> tools/dev/v8gen.py arm.release
>>> Added: target_os=arm
>>> Getting this failure:
>>>
>>> /Users/mindyp/local/src/v8/buildtools/mac/gn 
>>> --root=/Users/mindyp/local/src/v8 -q --check gen .
>>>
>>> ERROR Unresolved dependencies.
>>>
>>> //:run_mkpeephole(//build/toolchain/android:android_arm)
>>>
>>>   needs //:mkpeephole(//build/toolchain/mac:clang_x86_v8_arm)
>>>
>>> //:run_mksnapshot(//build/toolchain/android:android_arm)
>>>
>>>   needs //:mksnapshot(//build/toolchain/mac:clang_x86_v8_arm)
>>>
>>>
>>> 2) *Full static library build on Linux that is not just the .a, so I 
>>> can transfer it to my mac*
>>> Followed: 
>>> http://linuxplayer.org/2013/12/how-to-build-v8-static-library
>>> But this breaks during the LD phase
>>> Added: https://bugs.chromium.org/p/v8/issues/detail?id=5617#c1
>>>  (LDFLAGS=-lc++)
>>> Still broken
>>>
>>> -- 
>>> -- 
>>> v8-users mailing list
>>> v8-u...@googlegroups.com
>>> 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 v8-users+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] building V8 for Android on Mac or ubuntu w static libs?

[Mindy DelliCarpini]

Ok so did this to the .gclient file 1 directory up:
solutions = [
  {
"url": "https://chromium.googlesource.com/v8/v8.git;,
"managed": False,
"name": "v8",
"deps_file": "DEPS",
"custom_deps": {},
"target_os" : ['android', 'mac']
  },
]

Then: gclient sync
Then  tools/dev/v8gen.py arm.release

Then this in args.gn
is_debug = false
target_cpu = "arm"
v8_target_cpu = "arm"
target_os="android"

Then:

ninja -C out.gn/arm.release/


This error persists:

mindyp-macbookpro:v8 mindyp$ ninja -C out.gn/arm.release/

ninja: Entering directory `out.gn/arm.release/'

[1/1] Regenerating ninja files

FAILED: build.ninja 

/Users/mindyp/local/src/v8/buildtools/mac/gn 
--root=/Users/mindyp/local/src/v8 -q --check gen .

ERROR Unresolved dependencies.

//:run_mkpeephole(//build/toolchain/android:android_arm)

  needs //:mkpeephole(//build/toolchain/mac:clang_x86_v8_arm)

//:run_mksnapshot(//build/toolchain/android:android_arm)

  needs //:mksnapshot(//build/toolchain/mac:clang_x86_v8_arm)


ninja: error: rebuilding 'build.ninja': subcommand failed

[1]+  Donemate ../.gclient






On Thursday, December 22, 2016 at 11:46:38 PM UTC-8, Jochen Eisinger wrote:
>
> hey,
>
> to build for android, you should add target_os = "android" and target_cpu 
> = "arm".
>
> you'll also have to add target_os = ['android', 'mac'] to your .gclient 
> file (which should be one level up from your v8 checkout), so gclient sync 
> will download the android specific deps
>
> hth
> -jochen
>
> On Thu, Dec 22, 2016 at 5:41 PM 'Mindy DelliCarpini' via v8-users <
> v8-u...@googlegroups.com > wrote:
>
>> Need a V8 build for our prototyping tool (boom.googleplex.com). The tool 
>> runs with a Mac simulator, so the build has to be completed on a Mac.
>>
>> The TOT v8 builds are broken for Mac, and also for building static full 
>> libraries (no the thin .a files, which wouldn't be shareable)
>>
>> I'm interested in getting any of the following working (preference for 
>> Mac build, but I know its not a common thing)
>>
>> 1) *Build v8 on my mac*
>> Tried old instructions, but failed with missing libraries (standard c++?)
>> https://github.com/v8/v8/wiki/D8-on-Android
>> Tried new instructions:
>> tools/dev/v8gen.py arm.release
>> Added: target_os=arm
>> Getting this failure:
>>
>> /Users/mindyp/local/src/v8/buildtools/mac/gn 
>> --root=/Users/mindyp/local/src/v8 -q --check gen .
>>
>> ERROR Unresolved dependencies.
>>
>> //:run_mkpeephole(//build/toolchain/android:android_arm)
>>
>>   needs //:mkpeephole(//build/toolchain/mac:clang_x86_v8_arm)
>>
>> //:run_mksnapshot(//build/toolchain/android:android_arm)
>>
>>   needs //:mksnapshot(//build/toolchain/mac:clang_x86_v8_arm)
>>
>>
>> 2) *Full static library build on Linux that is not just the .a, so I can 
>> transfer it to my mac*
>> Followed: 
>> http://linuxplayer.org/2013/12/how-to-build-v8-static-library
>> But this breaks during the LD phase
>> Added: https://bugs.chromium.org/p/v8/issues/detail?id=5617#c1
>>  (LDFLAGS=-lc++)
>> Still broken
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com 
>> 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 v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] building V8 for Android on Mac or ubuntu w static libs?

[Jochen Eisinger]

hey,

to build for android, you should add target_os = "android" and target_cpu =
"arm".

you'll also have to add target_os = ['android', 'mac'] to your .gclient
file (which should be one level up from your v8 checkout), so gclient sync
will download the android specific deps

hth
-jochen

On Thu, Dec 22, 2016 at 5:41 PM 'Mindy DelliCarpini' via v8-users <
v8-users@googlegroups.com> wrote:

> Need a V8 build for our prototyping tool (boom.googleplex.com). The tool
> runs with a Mac simulator, so the build has to be completed on a Mac.
>
> The TOT v8 builds are broken for Mac, and also for building static full
> libraries (no the thin .a files, which wouldn't be shareable)
>
> I'm interested in getting any of the following working (preference for Mac
> build, but I know its not a common thing)
>
> 1) *Build v8 on my mac*
> Tried old instructions, but failed with missing libraries (standard c++?)
> https://github.com/v8/v8/wiki/D8-on-Android
> Tried new instructions:
> tools/dev/v8gen.py arm.release
> Added: target_os=arm
> Getting this failure:
>
> /Users/mindyp/local/src/v8/buildtools/mac/gn
> --root=/Users/mindyp/local/src/v8 -q --check gen .
>
> ERROR Unresolved dependencies.
>
> //:run_mkpeephole(//build/toolchain/android:android_arm)
>
>   needs //:mkpeephole(//build/toolchain/mac:clang_x86_v8_arm)
>
> //:run_mksnapshot(//build/toolchain/android:android_arm)
>
>   needs //:mksnapshot(//build/toolchain/mac:clang_x86_v8_arm)
>
>
> 2) *Full static library build on Linux that is not just the .a, so I can
> transfer it to my mac*
> Followed:
> http://linuxplayer.org/2013/12/how-to-build-v8-static-library
> But this breaks during the LD phase
> Added: https://bugs.chromium.org/p/v8/issues/detail?id=5617#c1
>  (LDFLAGS=-lc++)
> Still broken
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Visual Studio 2015 on Windows 10

['Michael Achenbach' via v8-users]

I don't know if the --ide option can be used for building V8. We don't 
officially support it. The stackoverflow link you provided contains also 
the answer we officially support:
http://stackoverflow.com/a/39550343

Could you try building with ninja and see if it works for you?

Of course, if you or anybody makes building with msbuild work, feel free to 
post it here.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Visual Studio 2015 on Windows 10

[jan . ehrhardt]

Or:

D:\chromium\v8>gn gen --help | grep -A10 ide=
  --ide=
  Generate files for an IDE. Currently supported values:
  "eclipse" - Eclipse CDT settings file.
  "vs" - Visual Studio project/solution files.
 (default Visual Studio version: 2015)
  "vs2013" - Visual Studio 2013 project/solution files.
  "vs2015" - Visual Studio 2015 project/solution files.
  "xcode" - Xcode workspace/solution files.
  "qtcreator" - QtCreator project files.
  "json" - JSON file containing target information

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Visual Studio 2015 on Windows 10

[jan . ehrhardt]

http://stackoverflow.com/questions/38674676/building-and-linking-v8-in-visual-studio
And it is in in the gn help:

D:\chromium\v8>gn gen --help | grep ide
  gn gen [] 
  GN optionally generates files for IDE. Possibilities for 
  --ide=
  Override default sln file name ("all"). Solution file is written
  Override defaut workspace file name ("all"). The workspace file
  Overrides default file name (project.json) of generated JSON file.
  --json-ide-script=
  --json-ide-script-args=

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Visual Studio 2015 on Windows 10

['Michael Achenbach' via v8-users]

Please refer to the authors of the gn --ide=vs extension. I don't know what 
this is supposed to be doing.

V8 officially only supports building with ninja. E.g.
gn gen v5.4/x64.release
ninja -C v5.4/x64.release d8

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Visual Studio 2015 on Windows 10

[jan . ehrhardt]

Take a look at how I built V8 5.4.500.43:
https://github.com/phpv8/v8js/issues/272#issuecomment-262848754

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 libs for Android on Windows 10

[sdaniel]

Jochen
I have the latest g++ packages installed .

However I discovered that all components of the V8 package did not 
download. The command "gclient sync --with_branch_heads" seems to fail with 
this message:


..
Downloading 
/home/sanjit/V8Dev/v8/third_party/binutils/Linux_x64/binutils.tar.bz2
Traceback (most recent call last):
  File "v8/third_party/binutils/download.py", line 117, in 
sys.exit(main(sys.argv))
  File "v8/third_party/binutils/download.py", line 106, in main
return FetchAndExtract(arch)
  File "v8/third_party/binutils/download.py", line 81, in FetchAndExtract
'-s', sha1file])
  File "/usr/lib/python2.7/subprocess.py", line 541, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['download_from_google_storage', 
'--no_resume', '--no_auth', '--bucket', 'chromium-binutils', '-s', 
'/home/sanjit/V8Dev/v8/third_party/binutils/Linux_x64/binutils.tar.bz2.sha1']' 
returned non-zero exit status 1
Error: Command '/usr/bin/python v8/third_party/binutils/download.py' 
returned non-zero exit status 1





On Tuesday, November 8, 2016 at 8:00:33 AM UTC, Jochen Eisinger wrote:
>
> Looks like you might need to install the g++ package?
>
> On Mon, Nov 7, 2016 at 12:39 PM Trekkie Ufo  > wrote:
>
>> Hi, managed to install everything on Ubuntu Linux and fired off a V8 
>> build for Android. 
>>
>> (1) gn gen out.gn/foo --args='is_debug=false target_cpu="arm64" 
>> v8_target_cpu="arm64" use_goma=false target_os = "android" 
>> is_component_build = true '
>> (2) ninja -C out.gn/foo
>>
>> I keep getting errors like the following, any suggestions ?
>>
>>
>> compilation terminated.
>> [604/2337] CXX obj/lib_wasm_section_fuzzer/wasm-section-fuzzers.o
>> FAILED: obj/lib_wasm_section_fuzzer/wasm-section-fuzzers.o 
>> ../../third_party/android_tools/ndk/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android-g++
>>  
>> -MMD -MF obj/lib_wasm_section_fuzzer/wasm-section-fuzzers.o.d 
>> -DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS -DENABLE_PRINTING=1 
>> -DENABLE_BASIC_PRINTING=1 -DENABLE_SPELLCHECK=1 
>> -DUSE_BROWSER_SPELLCHECKER=1 -DUSE_OPENSSL_CERTS=1 -DNO_TCMALLOC 
>> -DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL 
>> -DENABLE_SUPERVISED_USERS=1 -DSAFE_BROWSING_DB_REMOTE -DCHROMIUM_BUILD 
>> -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64 
>> -DANDROID -DHAVE_SYS_UIO_H -DANDROID_NDK_VERSION=r12b -DCOMPONENT_BUILD 
>> -D__GNU_SOURCE=1 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 
>> -DUSING_V8_SHARED -DV8_IMMINENT_DEPRECATION_WARNINGS -DV8_I18N_SUPPORT 
>> -DENABLE_HANDLE_ZAPPING -DV8_USE_EXTERNAL_STARTUP_DATA 
>> -DV8_TARGET_ARCH_ARM64 -I../.. -Igen -I../../include -Igen/include -I../.. 
>> -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector 
>> -funwind-tables -fPIC -pipe -ffunction-sections -fno-short-enums 
>> -finline-limit=64 -fno-omit-frame-pointer -gdwarf-3 -g2 
>> --sysroot=../../third_party/android_tools/ndk/platforms/android-21/arch-arm64
>>  
>> -fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized 
>> -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident 
>> -fdata-sections -ffunction-sections -fno-threadsafe-statics 
>> -fvisibility-inlines-hidden -std=gnu++11 -fno-rtti 
>> -isystem../../third_party/android_tools/ndk/sources/cxx-stl/llvm-libc++/libcxx/include
>>  
>> -isystem../../third_party/android_tools/ndk/sources/cxx-stl/llvm-libc++abi/libcxxabi/include
>>  
>> -isystem../../third_party/android_tools/ndk/sources/android/support/include 
>> -fno-exceptions -Wno-deprecated -Wno-narrowing -c 
>> ../../test/fuzzer/wasm-section-fuzzers.cc -o 
>> obj/lib_wasm_section_fuzzer/wasm-section-fuzzers.o
>> In file included from ../../test/fuzzer/wasm-section-fuzzers.h:11:0,
>>  from ../../test/fuzzer/wasm-section-fuzzers.cc:5:
>> ../../src/wasm/wasm-module.h:8:18: fatal error: memory: No such file or 
>> directory
>>  #include 
>>   ^
>> compilation terminated.
>> [607/2337] CXX 
>> clang_x64_v8_arm64/obj/...pector/inspector/v8-stack-trace-impl.o
>> ninja: build stopped: subcommand failed.
>> sanjit@sanjit-VirtualBox:~/v8$ 
>>  
>>
>>>
> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com 
>> 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 v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more 

Re: [v8-users] Building V8 libs for Android on Windows 10

[Jochen Eisinger]

Looks like you might need to install the g++ package?

On Mon, Nov 7, 2016 at 12:39 PM Trekkie Ufo  wrote:

> Hi, managed to install everything on Ubuntu Linux and fired off a V8 build
> for Android.
>
> (1) gn gen out.gn/foo --args='is_debug=false target_cpu="arm64"
> v8_target_cpu="arm64" use_goma=false target_os = "android"
> is_component_build = true '
> (2) ninja -C out.gn/foo
>
> I keep getting errors like the following, any suggestions ?
>
>
> compilation terminated.
> [604/2337] CXX obj/lib_wasm_section_fuzzer/wasm-section-fuzzers.o
> FAILED: obj/lib_wasm_section_fuzzer/wasm-section-fuzzers.o
> ../../third_party/android_tools/ndk/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android-g++
> -MMD -MF obj/lib_wasm_section_fuzzer/wasm-section-fuzzers.o.d
> -DV8_DEPRECATION_WARNINGS -DENABLE_NOTIFICATIONS -DENABLE_PRINTING=1
> -DENABLE_BASIC_PRINTING=1 -DENABLE_SPELLCHECK=1
> -DUSE_BROWSER_SPELLCHECKER=1 -DUSE_OPENSSL_CERTS=1 -DNO_TCMALLOC
> -DUSE_EXTERNAL_POPUP_MENU=1 -DENABLE_WEBRTC=1 -DDISABLE_NACL
> -DENABLE_SUPERVISED_USERS=1 -DSAFE_BROWSING_DB_REMOTE -DCHROMIUM_BUILD
> -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED -D_FILE_OFFSET_BITS=64
> -DANDROID -DHAVE_SYS_UIO_H -DANDROID_NDK_VERSION=r12b -DCOMPONENT_BUILD
> -D__GNU_SOURCE=1 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0
> -DUSING_V8_SHARED -DV8_IMMINENT_DEPRECATION_WARNINGS -DV8_I18N_SUPPORT
> -DENABLE_HANDLE_ZAPPING -DV8_USE_EXTERNAL_STARTUP_DATA
> -DV8_TARGET_ARCH_ARM64 -I../.. -Igen -I../../include -Igen/include -I../..
> -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector
> -funwind-tables -fPIC -pipe -ffunction-sections -fno-short-enums
> -finline-limit=64 -fno-omit-frame-pointer -gdwarf-3 -g2
> --sysroot=../../third_party/android_tools/ndk/platforms/android-21/arch-arm64
> -fvisibility=hidden -Wno-unused-local-typedefs -Wno-maybe-uninitialized
> -Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident
> -fdata-sections -ffunction-sections -fno-threadsafe-statics
> -fvisibility-inlines-hidden -std=gnu++11 -fno-rtti
> -isystem../../third_party/android_tools/ndk/sources/cxx-stl/llvm-libc++/libcxx/include
> -isystem../../third_party/android_tools/ndk/sources/cxx-stl/llvm-libc++abi/libcxxabi/include
> -isystem../../third_party/android_tools/ndk/sources/android/support/include
> -fno-exceptions -Wno-deprecated -Wno-narrowing -c
> ../../test/fuzzer/wasm-section-fuzzers.cc -o
> obj/lib_wasm_section_fuzzer/wasm-section-fuzzers.o
> In file included from ../../test/fuzzer/wasm-section-fuzzers.h:11:0,
>  from ../../test/fuzzer/wasm-section-fuzzers.cc:5:
> ../../src/wasm/wasm-module.h:8:18: fatal error: memory: No such file or
> directory
>  #include 
>   ^
> compilation terminated.
> [607/2337] CXX
> clang_x64_v8_arm64/obj/...pector/inspector/v8-stack-trace-impl.o
> ninja: build stopped: subcommand failed.
> sanjit@sanjit-VirtualBox:~/v8$
>
>
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 libs for Android on Windows 10

[Trekkie Ufo]

Ah thanks Jochen ! 
Got  Ubuntu running in a Virtual box and making good progress. 

Sanjit


On Monday, 7 November 2016 07:35:35 UTC, Jochen Eisinger wrote:
>
> Hi,
>
> we currently only support building for Android on a Linux or a Mac host.
>
> best
> -jochen
>
> On Sun, Nov 6, 2016 at 2:37 PM Trekkie Ufo  > wrote:
>
>> Hi
>> I am trying to build V8 for use in a plugin I am developing for the Unreal
>> Engine 4. My aim is to run the project on the Google Daydream VR platform
>> and hence I need V8 Android libraries. Ive tried everything in your
>> documentation but it just doesnt work. Ninja seems to be
>> using it and I get compile errors.. Is there a clean step by step doc
>> which explains how this is done ?
>>
>> Thanks for the help !
>>
>> Sanjit
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com 
>> 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 v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 libs for Android on Windows 10

[Jochen Eisinger]

Hi,

we currently only support building for Android on a Linux or a Mac host.

best
-jochen

On Sun, Nov 6, 2016 at 2:37 PM Trekkie Ufo  wrote:

> Hi
> I am trying to build V8 for use in a plugin I am developing for the Unreal
> Engine 4. My aim is to run the project on the Google Daydream VR platform
> and hence I need V8 Android libraries. Ive tried everything in your
> documentation but it just doesnt work. Ninja seems to be
> using it and I get compile errors.. Is there a clean step by step doc
> which explains how this is done ?
>
> Thanks for the help !
>
> Sanjit
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8

[Travis Sharp]

I had to manually create the .a file. I will see if I can dig up the script
I used to generate it.

On Mon, Oct 17, 2016 at 7:19 AM, Temuri Imnaishvili 
wrote:

> I've tried that.
>
> What I need in order to compile v8js is libv8_libplatform.a alongside its
> .so.
>
> I can still get everything I need if I compile off 5.1.x branch with gyp.
> Then I'd do this and all would be fine:
>
> echo -e "create /usr/lib/libv8_libplatform.a\naddlib 
> out/native/obj.target/tools/gyp/libv8_libplatform.a\nsave\nend" | sudo ar -M
>
>
> I've just recompiled v8 with "is_component_build = true", but
> tools/gyp/libv8_libplatform.a is not being generated.
>
> Could you please explain the problem?
>
> Thanks!
>
>
> On Monday, 17 October 2016 09:00:18 UTC-4, Jochen Eisinger wrote:
>>
>> support for compiling libplatform as a shared library landed a few days
>> ago. If you compile with the gn flag is_component_build = true, you should
>> get a shared library
>>
>> On Sat, Oct 15, 2016 at 10:06 PM Temuri Imnaishvili 
>> wrote:
>>
>>> Jochen,
>>>
>>> Facing the same problem. Can you provide us with help on compiling it
>>> correctly?
>>>
>>> Thanks!
>>>
>>>
>>> On Tuesday, 20 September 2016 03:25:21 UTC-4, Jochen Eisinger wrote:
>>>
 If you want to build v8 with shared libraries, set the gn arg
 is_component_build=true

 Yes, we intend to update the embedder guide. Contributions or bug
 reports are always welcome!

 On Fri, Sep 16, 2016 at 7:43 PM Furious Scissors 
 wrote:

> Ok - i'll try and give that a shot. Are there any plans on upgrading
> the Embedded Guide to something more recent than v4.8?
> If I work this out - would I be able to contribute to the wiki to
> update it for everyone else?
>
>
> On Thursday, September 15, 2016 at 10:11:01 PM UTC-7, Jochen Eisinger
> wrote:
>
>> by default, we build thin archives which are suitable for static
>> linking against other apps, and yes, you will need the .o files around 
>> for
>> that.
>>
>> If you'd rather have shared libraries (.so files), set the gn
>> arg is_component_build = true
>>
>> br
>> -jochen
>>
>> On Thu, Sep 15, 2016 at 5:07 PM Travis Sharp 
>> wrote:
>>
> I've followed the current instructions for building v8 with GN on
>>> https://github.com/v8/v8/wiki/Building%20with%20GN but after
>>> further inspection it looks as if the build only links the .o output
>>> instead of creating libraries for use in other applications.
>>>
>>> Am I missing a step or is this intended? I am trying to use the
>>> output library in another application.
>>>
>>> V8 Build-Head 5.4, Linux x64
>>>
>>> --
>>> --
>>> v8-users mailing list
>>>
>> v8-u...@googlegroups.com
>>
>>
>>> 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 v8-users+u...@googlegroups.com.
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> v8-users mailing list
> v8-u...@googlegroups.com
> 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 v8-users+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> --
>>> v8-users mailing list
>>> v8-u...@googlegroups.com
>>> 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 v8-users+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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/vEr5qpGNvl4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more 

Re: [v8-users] Building v8

[Temuri Imnaishvili]

I've tried that.

What I need in order to compile v8js is libv8_libplatform.a alongside its 
.so.

I can still get everything I need if I compile off 5.1.x branch with gyp. 
Then I'd do this and all would be fine:

echo -e "create /usr/lib/libv8_libplatform.a\naddlib 
out/native/obj.target/tools/gyp/libv8_libplatform.a\nsave\nend" | sudo ar -M


I've just recompiled v8 with "is_component_build = true", but 
tools/gyp/libv8_libplatform.a is not being generated.

Could you please explain the problem?

Thanks!


On Monday, 17 October 2016 09:00:18 UTC-4, Jochen Eisinger wrote:
>
> support for compiling libplatform as a shared library landed a few days 
> ago. If you compile with the gn flag is_component_build = true, you should 
> get a shared library
>
> On Sat, Oct 15, 2016 at 10:06 PM Temuri Imnaishvili  > wrote:
>
>> Jochen,
>>
>> Facing the same problem. Can you provide us with help on compiling it 
>> correctly?
>>
>> Thanks!
>>
>>
>> On Tuesday, 20 September 2016 03:25:21 UTC-4, Jochen Eisinger wrote:
>>
>>> If you want to build v8 with shared libraries, set the gn arg 
>>> is_component_build=true
>>>
>>> Yes, we intend to update the embedder guide. Contributions or bug 
>>> reports are always welcome!
>>>
>>> On Fri, Sep 16, 2016 at 7:43 PM Furious Scissors  
>>> wrote:
>>>
 Ok - i'll try and give that a shot. Are there any plans on upgrading 
 the Embedded Guide to something more recent than v4.8?
 If I work this out - would I be able to contribute to the wiki to 
 update it for everyone else?


 On Thursday, September 15, 2016 at 10:11:01 PM UTC-7, Jochen Eisinger 
 wrote:

> by default, we build thin archives which are suitable for static 
> linking against other apps, and yes, you will need the .o files around 
> for 
> that.
>
> If you'd rather have shared libraries (.so files), set the gn 
> arg is_component_build = true
>
> br
> -jochen
>
> On Thu, Sep 15, 2016 at 5:07 PM Travis Sharp  
> wrote:
>
 I've followed the current instructions for building v8 with GN on 
>> https://github.com/v8/v8/wiki/Building%20with%20GN but after further 
>> inspection it looks as if the build only links the .o output instead of 
>> creating libraries for use in other applications.
>>
>> Am I missing a step or is this intended? I am trying to use the 
>> output library in another application.
>>
>> V8 Build-Head 5.4, Linux x64
>>
>> -- 
>> -- 
>> v8-users mailing list
>>
> v8-u...@googlegroups.com
>
>
>> 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 v8-users+u...@googlegroups.com.
>
>
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
 -- 
 v8-users mailing list
 v8-u...@googlegroups.com
 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 v8-users+u...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com 
>> 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 v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8

[Jochen Eisinger]

support for compiling libplatform as a shared library landed a few days
ago. If you compile with the gn flag is_component_build = true, you should
get a shared library

On Sat, Oct 15, 2016 at 10:06 PM Temuri Imnaishvili 
wrote:

> Jochen,
>
> Facing the same problem. Can you provide us with help on compiling it
> correctly?
>
> Thanks!
>
>
> On Tuesday, 20 September 2016 03:25:21 UTC-4, Jochen Eisinger wrote:
>
> If you want to build v8 with shared libraries, set the gn arg
> is_component_build=true
>
> Yes, we intend to update the embedder guide. Contributions or bug reports
> are always welcome!
>
> On Fri, Sep 16, 2016 at 7:43 PM Furious Scissors 
> wrote:
>
> Ok - i'll try and give that a shot. Are there any plans on upgrading the
> Embedded Guide to something more recent than v4.8?
> If I work this out - would I be able to contribute to the wiki to update
> it for everyone else?
>
>
> On Thursday, September 15, 2016 at 10:11:01 PM UTC-7, Jochen Eisinger
> wrote:
>
> by default, we build thin archives which are suitable for static linking
> against other apps, and yes, you will need the .o files around for that.
>
> If you'd rather have shared libraries (.so files), set the gn
> arg is_component_build = true
>
> br
> -jochen
>
> On Thu, Sep 15, 2016 at 5:07 PM Travis Sharp  wrote:
>
> I've followed the current instructions for building v8 with GN on
> https://github.com/v8/v8/wiki/Building%20with%20GN but after further
> inspection it looks as if the build only links the .o output instead of
> creating libraries for use in other applications.
>
> Am I missing a step or is this intended? I am trying to use the output
> library in another application.
>
> V8 Build-Head 5.4, Linux x64
>
> --
> --
> v8-users mailing list
>
> v8-u...@googlegroups.com
>
>
> 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 v8-users+u...@googlegroups.com.
>
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> --
> v8-users mailing list
> v8-u...@googlegroups.com
> 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 v8-users+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8

[Temuri Imnaishvili]

Jochen,

Facing the same problem. Can you provide us with help on compiling it 
correctly?

Thanks!

On Tuesday, 20 September 2016 03:25:21 UTC-4, Jochen Eisinger wrote:
>
> If you want to build v8 with shared libraries, set the gn arg 
> is_component_build=true
>
> Yes, we intend to update the embedder guide. Contributions or bug reports 
> are always welcome!
>
> On Fri, Sep 16, 2016 at 7:43 PM Furious Scissors  > wrote:
>
>> Ok - i'll try and give that a shot. Are there any plans on upgrading the 
>> Embedded Guide to something more recent than v4.8?
>> If I work this out - would I be able to contribute to the wiki to update 
>> it for everyone else?
>>
>>
>> On Thursday, September 15, 2016 at 10:11:01 PM UTC-7, Jochen Eisinger 
>> wrote:
>>
>>> by default, we build thin archives which are suitable for static linking 
>>> against other apps, and yes, you will need the .o files around for that.
>>>
>>> If you'd rather have shared libraries (.so files), set the gn 
>>> arg is_component_build = true
>>>
>>> br
>>> -jochen
>>>
>>> On Thu, Sep 15, 2016 at 5:07 PM Travis Sharp  
>>> wrote:
>>>
>> I've followed the current instructions for building v8 with GN on 
 https://github.com/v8/v8/wiki/Building%20with%20GN but after further 
 inspection it looks as if the build only links the .o output instead of 
 creating libraries for use in other applications.

 Am I missing a step or is this intended? I am trying to use the output 
 library in another application.

 V8 Build-Head 5.4, Linux x64

 -- 
 -- 
 v8-users mailing list

>>> v8-u...@googlegroups.com
>>>
>>>
 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 v8-users+u...@googlegroups.com.
>>>
>>>
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com 
>> 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 v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with gn.

[Jane Chen]

I figured out how to build with gyp now.  Would still be nice to know how 
to link libv8_libplatform.lib and libv8_libbase.lib with the gn approach.

Thanks.

On Sunday, October 2, 2016 at 3:12:02 PM UTC-7, Jane Chen wrote:
>
> I specified "is_component_build=true" on 5.3-lkgr.  I do get libv8.so, but 
> I don't get libv8_libplatform.a or libv8_libbase.a.  This is not a problem 
> for me on Linux, since I could still build with gyp.  But on Windows, I 
> only seem to be able to build using gn now, and I need a way to generate 
> the .lib files out of the .obj files under v8_base etc.  Any suggestions?
>
> On Thursday, September 22, 2016 at 1:04:48 AM UTC-7, Jochen Eisinger wrote:
>>
>>
>>
>> On Thu, Sep 22, 2016 at 1:22 AM Jane Chen  wrote:
>>
>>> Trying to build v8 5.3-lkgr with gn for embedding use.
>>>
>>> When I build with GYP, I need to set 
>>> "-Dv8_use_external_startup_data=0".  Is there an equivalent setting flag 
>>> for gn?
>>>
>>
>> the equivalent gn setting is v8_use_external_startup_data = false
>>
>>
>>> Also if I build with gn and I need to link with libv8_libplatform.a, 
>>> libv8_libbase.a etc, is there a flag to generate those static libs?
>>>
>>>
>> those should be generated automatically when compiling v8
>>  
>>
>>> Thanks!
>>>
>>> -- 
>>> -- 
>>> v8-users mailing list
>>> v8-u...@googlegroups.com
>>> 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 v8-users+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with gn.

[Jane Chen]

I specified "is_component_build=true" on 5.3-lkgr.  I do get libv8.so, but 
I don't get libv8_libplatform.a or libv8_libbase.a.  This is not a problem 
for me on Linux, since I could still build with gyp.  But on Windows, I 
only seem to be able to build using gn now, and I need a way to generate 
the .lib files out of the .obj files under v8_base etc.  Any suggestions?

On Thursday, September 22, 2016 at 1:04:48 AM UTC-7, Jochen Eisinger wrote:
>
>
>
> On Thu, Sep 22, 2016 at 1:22 AM Jane Chen  
> wrote:
>
>> Trying to build v8 5.3-lkgr with gn for embedding use.
>>
>> When I build with GYP, I need to set "-Dv8_use_external_startup_data=0".  
>> Is there an equivalent setting flag for gn?
>>
>
> the equivalent gn setting is v8_use_external_startup_data = false
>
>
>> Also if I build with gn and I need to link with libv8_libplatform.a, 
>> libv8_libbase.a etc, is there a flag to generate those static libs?
>>
>>
> those should be generated automatically when compiling v8
>  
>
>> Thanks!
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com 
>> 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 v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with gn.

[Jochen Eisinger]

On Thu, Sep 22, 2016 at 1:22 AM Jane Chen  wrote:

> Trying to build v8 5.3-lkgr with gn for embedding use.
>
> When I build with GYP, I need to set "-Dv8_use_external_startup_data=0".
> Is there an equivalent setting flag for gn?
>

the equivalent gn setting is v8_use_external_startup_data = false


> Also if I build with gn and I need to link with libv8_libplatform.a,
> libv8_libbase.a etc, is there a flag to generate those static libs?
>
>
those should be generated automatically when compiling v8


> Thanks!
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Visual Studio 2015 on Windows 10

['Michael Achenbach' via v8-users]

That'd be with
set GYP_GENERATORS=msvs

But I'm afraid we dropped official support for this a while back.

Why not build with ninja? E.g. gyp_generator like you specified and then 
build with:
ninja -C out\Release

on x64 platforms might require:
ninja -C out\Release_x64

On Wednesday, September 21, 2016 at 10:56:55 AM UTC+2, Pieter wrote:
>
> Thanks for the reply Jochen,
> How do I specify the msvs gyp generator?
>
> On Wednesday, 21 September 2016 10:54:39 UTC+2, Jochen Eisinger wrote:
>>
>> If you want to build with MSVS, you need the msvs gyp generator. 
>> msvs-ninja only supports browsing the project, not building it
>>
>> On Tue, Sep 20, 2016 at 10:04 AM Pieter  wrote:
>>
>>>
>>> I have been struggling for a couple of days to get the correct 
>>> incantations to get a build of v8 working on windows 10 with visual studio 
>>> 2015.
>>>
>>> In short the steps that i've been attempting are as follows
>>>
>>>- set DEPOT_TOOLS_WIN_TOOLCHAIN=0
>>>- set GYP_MSVS_VERSION=2015
>>>- set GYP_GENERATORS=msvs-ninja,ninja
>>>- Get depot tools from: wget 
>>>https://storage.googleapis.com/chrome-infra/depot_tools.zip -OutFile 
>>>depot_tools.zip
>>>- Expand Archive: Expand-Archive .\depot_tools.zip -dest depot_tools
>>>- Set the path for depot tools
>>>- Checkout the v8 source code by running: fetch v8
>>>- Change directory to /v8 and checkout 5.2: git checkout 
>>>branch-heads/5.2
>>>- Run sync so that all the dependencies are up to date with the 
>>>branch: gclient sync
>>>- To generate the project files run: third_party/python_26/python.exe 
>>>build\gyp_v8 -Dtarget_arch=x64
>>>- To build: : "c:\Program Files (x86)\Microsoft Visual Studio 
>>>14.0\Common7\IDE\devenv.com" /build Release gypfiles\All.sln
>>>
>>> I am running into all kinds of issues related with the build and after 
>>> running the last command it ends with
>>>
>>> The first occurrence of the error is 
>>>
>>> 1>  ninja -t msvc -e environment.x64 -- "C:\Program Files 
>>> (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64\cl.exe" /nologo /
>>> showIncludes /FC @obj\third_party\icu\source\i18n\icui18n.collationkeys.
>>> obj.rsp /c..\..\third_party\icu\source\i18n\collationkeys.cpp /Foobj\
>>> third_party\icu\source\i18n\icui18n.collationkeys.obj /Fdobj\third_party
>>> \icu\icui18n.cc.pdb
>>> 1>C:\source\v8build\v8\third_party\icu\source\i18n\collationkeys.cpp : 
>>> fatal 
>>> error C1083: Cannot open compiler generated file: 
>>> 'C:\source\v8build\v8\out\Release_x64\obj\third_party\icu\source\i18n\icui18n.collationkeys.obj'
>>> : Permission denied
>>>
>>> I am not sure why i'm getting a permission denied.
>>>
>>> the build then ends with
>>>
>>> 40>  ninja: build stopped: subcommand failed.
>>> 40>ninja : warning : premature end of file; recovering
>>> 40>C:\source\v8build\v8\test\fuzzer\wasm_fuzzer.vcxproj(334,5): error 
>>> MSB3073: The command "call ninja.exe -C ..\..\out\Release_x64\ 
>>> wasm_fuzzer" exited with code 1.
>>>
>>>  ..\..\out\Release_x64\ wasm_fuzzer" exited with code 1.
>>> == Build: 20 succeeded, 21 failed, 0 up-to-date, 0 skipped 
>>> ==
>>>
>>>
>>> Any help would be much appreciated
>>>
>>> -- 
>>> -- 
>>> v8-users mailing list
>>> v8-u...@googlegroups.com
>>> 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 v8-users+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Visual Studio 2015 on Windows 10

[Pieter]

Thanks for the reply Jochen,
How do I specify the msvs gyp generator?

On Wednesday, 21 September 2016 10:54:39 UTC+2, Jochen Eisinger wrote:
>
> If you want to build with MSVS, you need the msvs gyp generator. 
> msvs-ninja only supports browsing the project, not building it
>
> On Tue, Sep 20, 2016 at 10:04 AM Pieter  > wrote:
>
>>
>> I have been struggling for a couple of days to get the correct 
>> incantations to get a build of v8 working on windows 10 with visual studio 
>> 2015.
>>
>> In short the steps that i've been attempting are as follows
>>
>>- set DEPOT_TOOLS_WIN_TOOLCHAIN=0
>>- set GYP_MSVS_VERSION=2015
>>- set GYP_GENERATORS=msvs-ninja,ninja
>>- Get depot tools from: wget 
>>https://storage.googleapis.com/chrome-infra/depot_tools.zip -OutFile 
>>depot_tools.zip
>>- Expand Archive: Expand-Archive .\depot_tools.zip -dest depot_tools
>>- Set the path for depot tools
>>- Checkout the v8 source code by running: fetch v8
>>- Change directory to /v8 and checkout 5.2: git checkout 
>>branch-heads/5.2
>>- Run sync so that all the dependencies are up to date with the 
>>branch: gclient sync
>>- To generate the project files run: third_party/python_26/python.exe 
>>build\gyp_v8 -Dtarget_arch=x64
>>- To build: : "c:\Program Files (x86)\Microsoft Visual Studio 
>>14.0\Common7\IDE\devenv.com" /build Release gypfiles\All.sln
>>
>> I am running into all kinds of issues related with the build and after 
>> running the last command it ends with
>>
>> The first occurrence of the error is 
>>
>> 1>  ninja -t msvc -e environment.x64 -- "C:\Program Files 
>> (x86)\Microsoft Visual Studio 14.0\VC\bin\amd64\cl.exe" /nologo /
>> showIncludes /FC @obj\third_party\icu\source\i18n\icui18n.collationkeys.
>> obj.rsp /c..\..\third_party\icu\source\i18n\collationkeys.cpp /Foobj\
>> third_party\icu\source\i18n\icui18n.collationkeys.obj /Fdobj\third_party\
>> icu\icui18n.cc.pdb
>> 1>C:\source\v8build\v8\third_party\icu\source\i18n\collationkeys.cpp : fatal 
>> error C1083: Cannot open compiler generated file: 
>> 'C:\source\v8build\v8\out\Release_x64\obj\third_party\icu\source\i18n\icui18n.collationkeys.obj'
>> : Permission denied
>>
>> I am not sure why i'm getting a permission denied.
>>
>> the build then ends with
>>
>> 40>  ninja: build stopped: subcommand failed.
>> 40>ninja : warning : premature end of file; recovering
>> 40>C:\source\v8build\v8\test\fuzzer\wasm_fuzzer.vcxproj(334,5): error 
>> MSB3073: The command "call ninja.exe -C ..\..\out\Release_x64\ 
>> wasm_fuzzer" exited with code 1.
>>
>>  ..\..\out\Release_x64\ wasm_fuzzer" exited with code 1.
>> == Build: 20 succeeded, 21 failed, 0 up-to-date, 0 skipped 
>> ==
>>
>>
>> Any help would be much appreciated
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com 
>> 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 v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Visual Studio 2015 on Windows 10

[Jochen Eisinger]

If you want to build with MSVS, you need the msvs gyp generator. msvs-ninja
only supports browsing the project, not building it

On Tue, Sep 20, 2016 at 10:04 AM Pieter  wrote:

>
> I have been struggling for a couple of days to get the correct
> incantations to get a build of v8 working on windows 10 with visual studio
> 2015.
>
> In short the steps that i've been attempting are as follows
>
>- set DEPOT_TOOLS_WIN_TOOLCHAIN=0
>- set GYP_MSVS_VERSION=2015
>- set GYP_GENERATORS=msvs-ninja,ninja
>- Get depot tools from: wget
>https://storage.googleapis.com/chrome-infra/depot_tools.zip -OutFile
>depot_tools.zip
>- Expand Archive: Expand-Archive .\depot_tools.zip -dest depot_tools
>- Set the path for depot tools
>- Checkout the v8 source code by running: fetch v8
>- Change directory to /v8 and checkout 5.2: git checkout
>branch-heads/5.2
>- Run sync so that all the dependencies are up to date with the
>branch: gclient sync
>- To generate the project files run: third_party/python_26/python.exe
>build\gyp_v8 -Dtarget_arch=x64
>- To build: : "c:\Program Files (x86)\Microsoft Visual Studio
>14.0\Common7\IDE\devenv.com" /build Release gypfiles\All.sln
>
> I am running into all kinds of issues related with the build and after
> running the last command it ends with
>
> The first occurrence of the error is
>
> 1>  ninja -t msvc -e environment.x64 -- "C:\Program Files (x86)\Microsoft
> Visual Studio 14.0\VC\bin\amd64\cl.exe" /nologo /showIncludes /FC @obj\
> third_party\icu\source\i18n\icui18n.collationkeys.obj.rsp /c..\..\
> third_party\icu\source\i18n\collationkeys.cpp /Foobj\third_party\icu\
> source\i18n\icui18n.collationkeys.obj /Fdobj\third_party\icu\icui18n.cc.
> pdb
> 1>C:\source\v8build\v8\third_party\icu\source\i18n\collationkeys.cpp : fatal
> error C1083: Cannot open compiler generated file:
> 'C:\source\v8build\v8\out\Release_x64\obj\third_party\icu\source\i18n\icui18n.collationkeys.obj'
> : Permission denied
>
> I am not sure why i'm getting a permission denied.
>
> the build then ends with
>
> 40>  ninja: build stopped: subcommand failed.
> 40>ninja : warning : premature end of file; recovering
> 40>C:\source\v8build\v8\test\fuzzer\wasm_fuzzer.vcxproj(334,5): error
> MSB3073: The command "call ninja.exe -C ..\..\out\Release_x64\
> wasm_fuzzer" exited with code 1.
>
>  ..\..\out\Release_x64\ wasm_fuzzer" exited with code 1.
> == Build: 20 succeeded, 21 failed, 0 up-to-date, 0 skipped
> ==
>
>
> Any help would be much appreciated
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8

[Jochen Eisinger]

If you want to build v8 with shared libraries, set the gn arg
is_component_build=true

Yes, we intend to update the embedder guide. Contributions or bug reports
are always welcome!

On Fri, Sep 16, 2016 at 7:43 PM Furious Scissors 
wrote:

> Ok - i'll try and give that a shot. Are there any plans on upgrading the
> Embedded Guide to something more recent than v4.8?
> If I work this out - would I be able to contribute to the wiki to update
> it for everyone else?
>
>
> On Thursday, September 15, 2016 at 10:11:01 PM UTC-7, Jochen Eisinger
> wrote:
>
> by default, we build thin archives which are suitable for static linking
> against other apps, and yes, you will need the .o files around for that.
>
> If you'd rather have shared libraries (.so files), set the gn
> arg is_component_build = true
>
> br
> -jochen
>
> On Thu, Sep 15, 2016 at 5:07 PM Travis Sharp  wrote:
>
> I've followed the current instructions for building v8 with GN on
> https://github.com/v8/v8/wiki/Building%20with%20GN but after further
> inspection it looks as if the build only links the .o output instead of
> creating libraries for use in other applications.
>
> Am I missing a step or is this intended? I am trying to use the output
> library in another application.
>
> V8 Build-Head 5.4, Linux x64
>
> --
> --
> v8-users mailing list
>
> v8-u...@googlegroups.com
>
>
> 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 v8-users+u...@googlegroups.com.
>
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8

[Furious Scissors]

Ok - i'll try and give that a shot. Are there any plans on upgrading the 
Embedded Guide to something more recent than v4.8?
If I work this out - would I be able to contribute to the wiki to update it 
for everyone else?

On Thursday, September 15, 2016 at 10:11:01 PM UTC-7, Jochen Eisinger wrote:
>
> by default, we build thin archives which are suitable for static linking 
> against other apps, and yes, you will need the .o files around for that.
>
> If you'd rather have shared libraries (.so files), set the gn 
> arg is_component_build = true
>
> br
> -jochen
>
> On Thu, Sep 15, 2016 at 5:07 PM Travis Sharp  > wrote:
>
>> I've followed the current instructions for building v8 with GN on 
>> https://github.com/v8/v8/wiki/Building%20with%20GN but after further 
>> inspection it looks as if the build only links the .o output instead of 
>> creating libraries for use in other applications.
>>
>> Am I missing a step or is this intended? I am trying to use the output 
>> library in another application.
>>
>> V8 Build-Head 5.4, Linux x64
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com 
>> 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 v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8

[Andre Cunha]

Hi,

Is there an option to build a shared version of libplatform? I'm upgrading 
a project I'm working on from v8 5.3 (with static linking) to 5.4 (with 
dynamic linking), and I use libplatform. I used to link against 
libv8_libplatform.a, but now I cannot find an option in gn that 
automatically generates libv8_libplatform.so. As a workaround, I generate 
the shared library by hand:

$ cd out.gn/x64.debug
$ gcc -shared -o libv8_libplatform.so obj/v8_libplatform/*.o

Is there a better way to do this?

Thank you very much.
Andre

On Friday, September 16, 2016 at 2:11:01 AM UTC-3, Jochen Eisinger wrote:
>
> by default, we build thin archives which are suitable for static linking 
> against other apps, and yes, you will need the .o files around for that.
>
> If you'd rather have shared libraries (.so files), set the gn 
> arg is_component_build = true
>
> br
> -jochen
>
> On Thu, Sep 15, 2016 at 5:07 PM Travis Sharp  > wrote:
>
>> I've followed the current instructions for building v8 with GN on 
>> https://github.com/v8/v8/wiki/Building%20with%20GN but after further 
>> inspection it looks as if the build only links the .o output instead of 
>> creating libraries for use in other applications.
>>
>> Am I missing a step or is this intended? I am trying to use the output 
>> library in another application.
>>
>> V8 Build-Head 5.4, Linux x64
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com 
>> 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 v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8

[Jochen Eisinger]

by default, we build thin archives which are suitable for static linking
against other apps, and yes, you will need the .o files around for that.

If you'd rather have shared libraries (.so files), set the gn
arg is_component_build = true

br
-jochen

On Thu, Sep 15, 2016 at 5:07 PM Travis Sharp 
wrote:

> I've followed the current instructions for building v8 with GN on
> https://github.com/v8/v8/wiki/Building%20with%20GN but after further
> inspection it looks as if the build only links the .o output instead of
> creating libraries for use in other applications.
>
> Am I missing a step or is this intended? I am trying to use the output
> library in another application.
>
> V8 Build-Head 5.4, Linux x64
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with a networking stack

[Jochen Eisinger]

chromium's implementation is here:
https://cs.chromium.org/chromium/src/net/proxy/proxy_resolver_v8.cc?rcl=1472733616=703

On Fri, Sep 2, 2016 at 3:53 AM Nick Chambers  wrote:

> Hello everyone! I have successfully built v8, however I have run into a
> snag. Essentially what I am after is the smallest amount of v8/chromium
> source that parses/resolves pac files. I know where to find the
> implementation of the basic functions like shExpMatch, but have been unable
> to find functions like dnsResolve and build it as a part of v8. Does anyone
> have steps/a good starting point for this? Thank you and have a great day!
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 Libraries Help. (Repositories Offline?)

[Ben Noordhuis]

On Wed, Jul 20, 2016 at 8:59 AM, Jochen Eisinger  wrote:
> Please reach out to IBM team. The svn server referenced in that
> documentation doesn't exist anymore, however, the s390(x) port is meanwhile
> (completely?) upstream, so just following the regular v8 build instructions
> might work?

I've passed it on to my coworkers at IBM.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 Libraries Help. (Repositories Offline?)

[Ben Noordhuis]

On Wed, Jul 20, 2016 at 12:33 AM, Allen Ng  wrote:
> Hello all,
>
> I do not know if this is the right place for this but it can't hurt to try!
> I am currently trying to build V8 Libraries following this tutorial,
> Building V8 Libraries Tutorial. I am trying to build these on a s390x Ubuntu
> Docker Container on a SLES 12  instance on the LinuxONE Community Cloud. I
> have been following along with it but when it comes time to do "make
> dependencies" I get an error that sasy teh SVN can not connect to the
> gyp.googlecode.com/svn/trunks repository. I looked around on Google and it
> seems that repository has been taken offline. There are two other
> repositories down the line, googletest and googlemock repositories, that
> also seem to have been taken down and merged into one single repository.
>
> So I was wondering if any of you know of a different tutorial that would
> help me here. I have found github mirrors of gyp.googlecode.com/svn/trunk
> and it seems to work but when I run the next command of  "make s390x -j4
> library=shared" i get an error after replacing the googletest and googlemock
> repositories with the new combined repository managed by Google. The error
> is a "No rule to make target for gtest_main.o.
>
> The main thing I am looking for is if there are any up to date tutorials on
> building the V8 Libraries on a LinuxONE Community Cloud Instance. If you
> need anymore information please feel free to ask.
>
>
> Thanks,
> Allen

What V8 version are you trying to build?  To the best of my knowledge,
V8 5.1 and up should build out of the box on s390x if you follow the
steps described here[0].

[0] https://github.com/v8/v8/wiki -> Usage -> Building from source

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 Libraries Help. (Repositories Offline?)

[Jochen Eisinger]

Please reach out to IBM team. The svn server referenced in that
documentation doesn't exist anymore, however, the s390(x) port is meanwhile
(completely?) upstream, so just following the regular v8 build instructions
might work?

On Wed, Jul 20, 2016 at 12:33 AM Allen Ng  wrote:

> Hello all,
>
> I do not know if this is the right place for this but it can't hurt to
> try! I am currently trying to build V8 Libraries following this tutorial, 
> Building
> V8 Libraries Tutorial
> . I am
> trying to build these on a s390x Ubuntu Docker Container on a SLES 12
>  instance on the LinuxONE Community Cloud. I have been following along with
> it but when it comes time to do "make dependencies" I get an error that
> sasy teh SVN can not connect to the gyp.googlecode.com/svn/trunks
> repository. I looked around on Google and it seems that repository has been
> taken offline. There are two other repositories down the line, googletest
> and googlemock repositories, that also seem to have been taken down and
> merged into one single repository.
>
> So I was wondering if any of you know of a different tutorial that would
> help me here. I have found github mirrors of gyp.googlecode.com/svn/trunk
> and it seems to work but when I run the next command of  "make s390x -j4
> library=shared" i get an error after replacing the googletest and
> googlemock repositories with the new combined repository managed by Google.
> The error is a "No rule to make target for gtest_main.o.
>
> The main thing I am looking for is if there are any up to date tutorials
> on building the V8 Libraries on a LinuxONE Community Cloud Instance. If you
> need anymore information please feel free to ask.
>
>
> Thanks,
> Allen
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 without natives_blob.bin and snapshot_blob.bin

[Dawid Skurzok]

It works, thank you!

W dniu wtorek, 28 czerwca 2016 16:33:20 UTC+2 użytkownik Ben Noordhuis 
napisał:
>
> On Tue, Jun 28, 2016 at 3:55 PM, Dawid Skurzok  > wrote: 
> > I have problems with building V8 without external data files. I have 
> asked 
> > same question on SO but with no success. I think I'm missing something 
> > simple, I don't know much of GYP. 
> > 
> > I already build V8 and its working correctly, but binary needs two 
> "external 
> > data" files. I don want this files. 
> > 
> > I was trying to build V8 without "external startup data". I tried to set 
> > v8_use_external_startup_data : 0, in build.common.gypi and 
> > build/standalone.gypi, but then make is reporting failure at some point. 
> > 
> > I'm using following code to build v8: 
> > 
> > git clone 
> https://chromium.googlesource.com/chromium/tool/depot_tools.git 
> > export PATH=`pwd`/depot_tools:"$PATH" 
> > fetch v8 
> > gclient sync 
> > cd v8 
> > git checkout branch-heads/5.1 
> > # ... modifying gyni files 
> > make x64.release -j 20 
> > 
> > I'm using default, static linking. How I can build V8 without need of 
> > natives_blob.bin and snapshot_blob.bin ? 
>
> `make -j20 x64.release GYPFLAGS="-Dv8_use_external_startup_data=0"` should 
> work. 
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 without natives_blob.bin and snapshot_blob.bin

[Ben Noordhuis]

On Tue, Jun 28, 2016 at 3:55 PM, Dawid Skurzok  wrote:
> I have problems with building V8 without external data files. I have asked
> same question on SO but with no success. I think I'm missing something
> simple, I don't know much of GYP.
>
> I already build V8 and its working correctly, but binary needs two "external
> data" files. I don want this files.
>
> I was trying to build V8 without "external startup data". I tried to set
> v8_use_external_startup_data : 0, in build.common.gypi and
> build/standalone.gypi, but then make is reporting failure at some point.
>
> I'm using following code to build v8:
>
> git clone https://chromium.googlesource.com/chromium/tool/depot_tools.git
> export PATH=`pwd`/depot_tools:"$PATH"
> fetch v8
> gclient sync
> cd v8
> git checkout branch-heads/5.1
> # ... modifying gyni files
> make x64.release -j 20
>
> I'm using default, static linking. How I can build V8 without need of
> natives_blob.bin and snapshot_blob.bin ?

`make -j20 x64.release GYPFLAGS="-Dv8_use_external_startup_data=0"` should work.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 in an lxc container

[Caleb Everett]

Added the "o" flag to the extract line here:
https://github.com/v8/v8/blob/5749d710bc73ef40f9b9e8b94ec290e0412d3f57/third_party/binutils/download.py#L91

and that worked, but then ran into another snag, similar to this one:
https://bbs.archlinux.org/viewtopic.php?id=209871

Bailed on the build from source and installed libv8 from this repo:
https://launchpad.net/~pinepain/+archive/ubuntu/libv8-5.2

On Fri, May 27, 2016 at 11:39 AM,  wrote:

> I'm trying to build v8 in an lxc container and am getting the following
> errors when I try to run gclient sync, I believe because the ownership
> uid:gid of the files that are being extracted is out outside of the range
> of uid:gid available to the container. How can I add the --no-same-owner
> flag to the files that are being extracted?
>
> tar: ./lib/ldscripts/elf_k1om.xr: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_i386.xw: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_i386.xd: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_l1om.xn: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_i386.xr: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_i386.xs: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_k1om.xsw: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_l1om.x: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_x86_64.xu: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf32_x86_64.xd: Cannot change ownership to uid
> 179961, gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_x86_64.xd: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_l1om.xsc: Cannot change ownership to uid 179961,
> gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf_x86_64.xsw: Cannot change ownership to uid
> 179961, gid 5000: Invalid argument
> tar: ./lib/ldscripts/elf32_x86_64.xbn: Cannot change ownership to uid
> 179961, gid 5000: Invalid argument
> ...
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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/3vPQZ2Nod2Q/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 Older versions

[Jakob Kummerow]

3.9.24, are you sure? That's a daily development snapshot from almost 4
years ago! I'd strongly advise against using it for anything, as it is
probably full of bugs, including security vulnerabilities. I wouldn't be
surprised if it didn't even compile any more with modern compilers, as
toolchains tend to get stricter over time.

I realize that this isn't what you wanted to hear. Sorry about that.

On Thu, Feb 11, 2016 at 8:16 AM, hitesh mehata 
wrote:

> Hi,
>
> I am very new to v8, by looking at documentation, I could compile the
> latest version of v8 javascript engine and as well able to write some
> sample C++ programs.
>
> But my requirement is to build version 3.9.24 for x86/x64 Linux platform.
> I couldn't find any steps and no clue how can I proceed further.
>
> Any help is much appreciated.
>
> Thanks,
> Hitesh
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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 v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 Older versions

[hitesh mehata]

Yeap, I completely understand. This is for the test purpose and I got few
dependencies which requires me to use this version. I see programs used to
compile with this version now fail to compile with newer versions, and
can't change/modify these programs.

Thanks,
Hitesh


On Thu, Feb 11, 2016 at 3:25 PM, Jakob Kummerow 
wrote:

> 3.9.24, are you sure? That's a daily development snapshot from almost 4
> years ago! I'd strongly advise against using it for anything, as it is
> probably full of bugs, including security vulnerabilities. I wouldn't be
> surprised if it didn't even compile any more with modern compilers, as
> toolchains tend to get stricter over time.
>
> I realize that this isn't what you wanted to hear. Sorry about that.
>
> On Thu, Feb 11, 2016 at 8:16 AM, hitesh mehata 
> wrote:
>
>> Hi,
>>
>> I am very new to v8, by looking at documentation, I could compile the
>> latest version of v8 javascript engine and as well able to write some
>> sample C++ programs.
>>
>> But my requirement is to build version 3.9.24 for x86/x64 Linux platform.
>> I couldn't find any steps and no clue how can I proceed further.
>>
>> Any help is much appreciated.
>>
>> Thanks,
>> Hitesh
>>
>> --
>> --
>> v8-users mailing list
>> v8-users@googlegroups.com
>> 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 v8-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> --
> v8-users mailing list
> v8-users@googlegroups.com
> 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/DF6-TGtlX-Q/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> v8-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 using Visual Studio 2015

[Michael Eng]

I was only able to get V8 to build with VS2015 by editing 
build/standalone.gypi as Michael Collins posted. At this time, is V8 tested 
to work with MSVS 2015? Is there a plan to switch soon?

Thanks,
Michael

On Monday, July 27, 2015 at 9:54:01 AM UTC-7, Jochen Eisinger wrote:
>
> I landed some config changes to make v8 compile with MSVS 2015, however, I 
> haven't ran tests yet.
>
> Since we don't have MSVS 2015 builders yet, that configuration might 
> break, however, eventually, we'll switch to MSVS 2015, just not yet now.
>
> best
> -jochen
>
> On Thu, Jul 23, 2015 at 5:19 PM Michael Collins <
> michael...@imaginaryrealities.com > wrote:
>
>> I managed to get v8 to build under Visual Studio 2015 RTM. The issues 
>> that I ran into were with treating warnings as errors. Some things that 
>> were allowed under VS2013 now cause warnings with the VS2015 C++ compiler. 
>> There's a warning about a "typedef enum" without a name in dbghelp.h (line 
>> 1544) that causes some of the warnings. Others appear to be 
>> reinterpret_cast warnings going from int to void *. I'm assuming since 
>> this was ok in VS2013 that they're also ok in VS2015, but I haven't done a 
>> significant amount of testing with the VS2015 build yet.
>>
>> To get this to work, follow the wiki instructions up until the point that 
>> you run "python build\gyp_v8". Before doing that, you have to turn off the 
>> /WX compiler flag. The only way that I found to do this was to edit 
>> build/standalone.gypi and modify line 682 by setting 'WarnAsError' to 
>> 'false'. After doing that, I ran the build\gyp_v8 script:
>>
>> python build\gyp_v8 -Dtarget_arch=x64 -Dcomponent=shared_library
>>
>> Finally, run MSBuild to build the project:
>>
>> msbuild /p:Configuration=Release build\All.sln
>>
>> I tried different options like passing in "-Dwerror=no" or trying to turn 
>> off /WX by passing properties to MSBuild, but nothing else seems to 
>> work.Editing standalone.gypi seems like the only option. If anyone has any 
>> other options for turning this off with Visual Studio, please let me know.
>>
>> -- 
>> -- 
>> v8-users mailing list
>> v8-u...@googlegroups.com 
>> 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 v8-users+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 using Visual Studio 2015

[Mike Moening]

Are you building & debugging with the Visual Studio IDE? 
Using a Visual Studio solution (.sln) file?
I'm still on VS2013 and would LOVE to be able to use the IDE over DOS ninja 
commands.

Can you point me to those instructions on how to make this happen?

Thanks a lot!

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 using Visual Studio 2015

[Michael Eng]

I followed 
https://chromium.googlesource.com/v8/v8/+/master/docs/building_with_gyp.md


1. Install Visual Studio 2015 Enterprise (Visual Studio 2013 Ultimate is also 
installed if that matters).
2. Download and unpack depot_tools to C:\depot_tools
3. cd to C:\depot_tools
4. gclient sync
5. fetch v8
6. cd C:\depot_tools\v8
7. python build/gyp_v8 -Dtarget_arch=ia32 -Dcomponent=shared_library 
-Dv8_enable_i18n_support=0

8. "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com" 
/build Debug build/all.sln


If you want the above to work with VS2013 you may need to run SET 
GYP_MSVS_VERSION=2013 


On Tuesday, October 27, 2015 at 11:27:45 AM UTC-7, Mike Moening wrote:
>
> Are you building & debugging with the Visual Studio IDE? 
> Using a Visual Studio solution (.sln) file?
> I'm still on VS2013 and would LOVE to be able to use the IDE over DOS 
> ninja commands.
>
> Can you point me to those instructions on how to make this happen?
>
> Thanks a lot!
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 on Mac OS X

[Ben Noordhuis]

On Fri, Sep 25, 2015 at 5:54 PM, Bradley Slavik  wrote:
> Dear V8 users group,
>
> I am looking for information about building V8 on Mac OS X.  A few months
> ago when I researched it, it appeared that GYP was necessary to build V8.
> GYP required old Python 2 instead of Python 3 to be installed. Should this
> bother me? Should I just be downloading V8 instead of building my own? Is
> there a build which does not require me to have outdated Python installed on
> my computer? I had read some posts which suggested that GN might be used for
> building V8 in the near future. Is any of this necessary to become an expert
> at using Node.js and NPM?
>
> I know that I seem to have a lot of questions, but google has failed me when
> I tried to research these issues.
>
> Thanks for helping me out.
>
> Bradley Slavik

If you follow the instructions from [0], depot_tools will check out
GYP and the other prerequisites to a local directory.  Don't bother if
you just want to play around with node.js and npm; V8 ships as part of
node.js, there is no need to build it yourself.

[0] https://code.google.com/p/v8-wiki/wiki/UsingGit

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Visual Studio 2012

[Purusothaman A]

Thank you so much for your reply.

- Purusothaman A

On Mon, Aug 10, 2015 at 3:17 PM, Ben Noordhuis i...@bnoordhuis.nl wrote:

 On Mon, Aug 10, 2015 at 8:34 AM, Purusothaman A
 purusothama...@gmail.com wrote:
  Hi All,
 
  I am new to this group and I like to integrate google v8 with my project.
 
  Tried many times to build source with VS 2012, but its giving so many
  compilation errors.
 
  Is there some step by step procedure to compile v8 source in Visual
 Studio
  2012 ?
 
  Thanks in advance.
 
  - Purusothaman A

 If you want to build any release newer than (IIRC) 3.28, you're going
 to need VS 2013.  2012 doesn't support C++11 well enough to build V8.

 --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 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/yF-yWDcnplc/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 v8-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 with Visual Studio 2012

[Ben Noordhuis]

On Mon, Aug 10, 2015 at 8:34 AM, Purusothaman A
purusothama...@gmail.com wrote:
 Hi All,

 I am new to this group and I like to integrate google v8 with my project.

 Tried many times to build source with VS 2012, but its giving so many
 compilation errors.

 Is there some step by step procedure to compile v8 source in Visual Studio
 2012 ?

 Thanks in advance.

 - Purusothaman A

If you want to build any release newer than (IIRC) 3.28, you're going
to need VS 2013.  2012 doesn't support C++11 well enough to build V8.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 using Visual Studio 2015

[Jochen Eisinger]

I landed some config changes to make v8 compile with MSVS 2015, however, I
haven't ran tests yet.

Since we don't have MSVS 2015 builders yet, that configuration might break,
however, eventually, we'll switch to MSVS 2015, just not yet now.

best
-jochen

On Thu, Jul 23, 2015 at 5:19 PM Michael Collins 
michael.coll...@imaginaryrealities.com wrote:

 I managed to get v8 to build under Visual Studio 2015 RTM. The issues that
 I ran into were with treating warnings as errors. Some things that were
 allowed under VS2013 now cause warnings with the VS2015 C++ compiler.
 There's a warning about a typedef enum without a name in dbghelp.h (line
 1544) that causes some of the warnings. Others appear to be
 reinterpret_castT warnings going from int to void *. I'm assuming since
 this was ok in VS2013 that they're also ok in VS2015, but I haven't done a
 significant amount of testing with the VS2015 build yet.

 To get this to work, follow the wiki instructions up until the point that
 you run python build\gyp_v8. Before doing that, you have to turn off the
 /WX compiler flag. The only way that I found to do this was to edit
 build/standalone.gypi and modify line 682 by setting 'WarnAsError' to
 'false'. After doing that, I ran the build\gyp_v8 script:

 python build\gyp_v8 -Dtarget_arch=x64 -Dcomponent=shared_library

 Finally, run MSBuild to build the project:

 msbuild /p:Configuration=Release build\All.sln

 I tried different options like passing in -Dwerror=no or trying to turn
 off /WX by passing properties to MSBuild, but nothing else seems to
 work.Editing standalone.gypi seems like the only option. If anyone has any
 other options for turning this off with Visual Studio, please let me know.

 --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 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 v8-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 with higher heap size

[Ben Noordhuis]

On Tue, Aug 12, 2014 at 9:02 PM, Sridhar sridha...@gmail.com wrote:
 Hi All,

 I am new to nodejs and V8, I am trying to build V8 with increased heap for
 server side usage of V8. In V8 source ( heap.cc) it is mentioned you can set
 this as build environment to build with higher heap.
 Can someone please point me how can I set or any example that will help.

 This blog also shows you can rebuild V8 with higher heap but the files
 mentoined in this blog might be old and there are changes in latest V8
 source
 http://blog.caustik.com/category/programming/

 Thanks much in advance. My goal is to increase heap to 8GB and build V8 and
 node.

Maybe I misunderstand what you mean but doesn't
--max_old_space_size=8192 do what you want?

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 for ARM64 in MSVC2012

[Sven Panne]

On Thu, Aug 7, 2014 at 11:50 PM, Prince Wall realprincew...@gmail.com
wrote:

 [...] However, from [v8]\src\arm64\constants-arm64.h, it says Assert that
 this is an LP64 system and uses type long a lot, assuming it is 64-bit.
 However, Windows x64 is LLP64 system and has long as 32-bit.  Does this
 mean that we cannot use target_arch=arm64 on Windows host?


I'm not sure if anybody has tried to build ARM64 stuff on WIndows yet, so
it's quite probable that there are bugs in this combination. Patches
accepted... ;-)

One more point: Support for VS 2012 is on death row, you'll need VS 2013
soon.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 for ARM64 in MSVC2012

[Rodolph Perfetta]

There is nothing fundamentally preventing an LLP64 system to build/run
arm64 but it was never tested hence not supported. Some re-factoring is
probably required (don't forget constants). As Sven said, patches welcome.



On 8 August 2014 07:21, Sven Panne svenpa...@chromium.org wrote:

 On Thu, Aug 7, 2014 at 11:50 PM, Prince Wall realprincew...@gmail.com
 wrote:

 [...] However, from [v8]\src\arm64\constants-arm64.h, it says Assert
 that this is an LP64 system and uses type long a lot, assuming it is
 64-bit. However, Windows x64 is LLP64 system and has long as 32-bit.
 Does this mean that we cannot use target_arch=arm64 on Windows host?


 I'm not sure if anybody has tried to build ARM64 stuff on WIndows yet, so
 it's quite probable that there are bugs in this combination. Patches
 accepted... ;-)

 One more point: Support for VS 2012 is on death row, you'll need VS 2013
 soon.

 --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 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 v8-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 for ARM64 in MSVC2012

[Prince Wall]

Thank Sven and Rodolph for the suggestions. Indeed, lots of constants
ending with UL or L need to be changed for Windows build which assumes
32-bit for long.

In fact, it would be better to use ULL and LL, which guarantees 64-bit
on both LP64 and LLP64 systems. The bitwidth for long is the only
difference between the two.


On Fri, Aug 8, 2014 at 3:04 AM, Rodolph Perfetta rodolph.perfe...@gmail.com
 wrote:

 There is nothing fundamentally preventing an LLP64 system to build/run
 arm64 but it was never tested hence not supported. Some re-factoring is
 probably required (don't forget constants). As Sven said, patches welcome.



 On 8 August 2014 07:21, Sven Panne svenpa...@chromium.org wrote:

 On Thu, Aug 7, 2014 at 11:50 PM, Prince Wall realprincew...@gmail.com
 wrote:

 [...] However, from [v8]\src\arm64\constants-arm64.h, it says Assert
 that this is an LP64 system and uses type long a lot, assuming it is
 64-bit. However, Windows x64 is LLP64 system and has long as 32-bit.
 Does this mean that we cannot use target_arch=arm64 on Windows host?


 I'm not sure if anybody has tried to build ARM64 stuff on WIndows yet, so
 it's quite probable that there are bugs in this combination. Patches
 accepted... ;-)

 One more point: Support for VS 2012 is on death row, you'll need VS 2013
 soon.

 --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 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 v8-users+unsubscr...@googlegroups.com.

 For more options, visit https://groups.google.com/d/optout.


  --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 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/1DZPKQlIW7A/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 v8-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

[Dirk Grabbert]

Thanks for help again. I didn't run into more problems until now.

It seems, that /proc/cpuinfo changed since kernel 3.9.3 for the ARM.

Am Dienstag, 22. Juli 2014 16:34:18 UTC+2 schrieb Rodolph Perfetta:

 I sounds like auto detection is failing again, override it: --noenable-mls 
 should do it.

 I can't push a patch right now so keep reporting any issues.

 Thanks,
 Rodolph.


 On 22 July 2014 15:08, Dirk Grabbert dirk.g...@gmail.com javascript: 
 wrote:

 Ok, I'm able to start the example shell right now. But I got the next 
 problem.

 Trying to run a js-script brings up an illegal instruction caused by 
 mls. I think it's generated by the JIT, right?

 The script I'm trying to run is a port of the dhrystone test (source: 
 http://jsperf.com/pystone-js):

 var LOOPS = 50;

 var Ident1 = 1,
 Ident2 = 2,
 Ident3 = 3,
 Ident4 = 4,
 Ident5 = 5;

 var TRUE = 1,
 FALSE = 0;

 var IntGlob = 0;
 var BoolGlob = FALSE;
 var Char1Glob = '\0';
 var Char2Glob = '\0';
 var Array1Glob = new Array(51);

 for (var i = 0; i  Array1Glob.length; ++i) {
   Array1Glob[i] = 0
 }

 var Array2Glob = Array1Glob.map(function(n) {
 return Array1Glob.slice();
 });

 var PtrGlb = null;
 var PtrGlbNext = null;

 var strings = {
 someString:DHRYSTONE PROGRAM, SOME STRING,
  fstString:DHRYSTONE PROGRAM, 1'ST STRING,
 sndString:DHRYSTONE PROGRAM, 2'ND STRING
 };

 function main(){
 Proc0();
 }

 function Record(PtrComp, Discr, EnumComp, IntComp, StringComp) {
   this.PtrComp = PtrComp || null;
   this.Discr = Discr || 0;
   this.EnumComp = EnumComp || 0;
   this.IntComp = IntComp || 0;
   this.StringComp = StringComp || 0;
 }

 function structassign(d,s){
 d.PtrComp = s.PtrComp;
 d.Discr = s.Discr;
 d.EnumComp = s.EnumComp;
  d.IntComp = s.IntComp;
 d.StringComp = s.StringComp;
 }

 function clock(){
 return new Date().valueOf() / 1000.0
 }

 function Proc0(){
 var CharIndex;
 var starttime, benchtime, nulltime;

  var starttime = clock();
 for(var i = 0; i  LOOPS; ++i);
 nulltime = clock() - starttime;

 PtrGlbNext = new Record();
 PtrGlb = new Record();
 PtrGlb.PtrComp = PtrGlbNext;
  PtrGlb.Discr = Ident1;
 PtrGlb.EnumComp = Ident3;
 PtrGlb.IntComp = 40;
  PtrGlb.StringComp = DHRYSTONE PROGRAM, SOME STRING; // im Original 
 wird hier ein strcpy angewandt
 var String1Loc = DHRYSTONE PROGRAM, 1'ST STRING; 

 Array2Glob[8][7] = 10;

 /* start timer */
 starttime = clock();
  for(var i = 0; i  LOOPS; ++i){
 Proc5();
 Proc4();
 IntLoc1 = 2;
  IntLoc2 = 3;
 var String2Loc = DHRYSTONE PROGRAM, 2'ND STRING;  // im Original wird 
 hier ein strcpy angewandt
  var EnumLoc = Ident2;
 BoolGlob = !Func2(String1Loc, String2Loc);

 while(IntLoc1  IntLoc2){
  IntLoc3 = 5 * IntLoc1 - IntLoc2;
 Proc7(IntLoc1, IntLoc2, IntLoc3);
 ++IntLoc1;
  }

 Proc8(Array1Glob, Array2Glob, IntLoc1, IntLoc3);
 Proc1(PtrGlb);

 for (CharIndex = 'A'; CharIndex = Char2Glob; CharIndex = 
 String.fromCharCode(CharIndex.charCodeAt(0) + 1)){ // string to int to 
 string convertion required by js
  if (EnumLoc == Func1(CharIndex, 'C'))
 EnumLoc = Proc6(Ident1);
 }

 IntLoc3 = IntLoc2 * IntLoc1;
 IntLoc2 = IntLoc3 / IntLoc1;
 IntLoc2 = 7 * (IntLoc3 - IntLoc2) - IntLoc1;
 IntLoc1 = Proc2(IntLoc1); // nicht by-reference ?
 }

 benchtime = clock() - starttime - nulltime;
  print(JsPystone() time for  + LOOPS +  passes =  + benchtime);
 print(This machine benchmarks at  +  (LOOPS / benchtime) +  
 pystones/second);
 // console.log(JsPystone() time for  + LOOPS +  passes =  + 
 benchtime);
 // console.log(This machine benchmarks at  +  (LOOPS / benchtime) +  
 pystones/second);
 }

 function Proc1(PtrParIn){
 var NextRecord = PtrParIn.PtrComp;

 structassign(NextRecord, PtrGlb);
  PtrParIn.IntComp = 5;
   NextRecord.IntComp = PtrParIn.IntComp;
   NextRecord.PtrComp = PtrParIn.PtrComp;
   Proc3(NextRecord.PtrComp);

   if(NextRecord.PtrComp == Ident1){
   NextRecord.IntComp = 6;
   NextRecord.EnumComp = Proc6(PtrParIn.EnumComp);
   NextRecord.PtrComp = PtrGlb.PtrComp;
   NextRecord.IntComp = Proc7(NextRecord.IntComp, 10);
   } else structassign(PtrParIn, NextRecord);
   
   NextRecord.PtrComp = null;
   
   return PtrParIn;
 }

 function Proc2(IntParIO){
 var IntLoc, EnumLoc;

 IntLoc = IntParIO + 10;
 for(;;){
 if (Char1Glob == 'A'){
  --IntLoc;
 IntParIO = IntLoc - IntGlob;
 EnumLoc = Ident1;
  }
 if (EnumLoc == Ident1)
 break;
 }
 }

 function Proc3(PtrParOut){
 if (PtrGlb !== null) {
 PtrParOut = PtrGlb.PtrComp;
   } else {
 IntGlob = 100;
   }
   PtrGlb.IntComp = Proc7(10, IntGlob);
   return PtrParOut;
 }

 function Proc4(){
 var BoolLoc = Char1Glob == 'A';
  BoolLoc |= BoolGlob;
 Char2Glob = 'B';
 }

 function Proc5(){
 Char1Glob = 'A';
  BoolGlob = FALSE;
 }

 function Proc6(EnumParIn, EnumParOut){
 var EnumParOut = EnumParIn;
  if(!Func3(EnumParIn))
 EnumParOut = Ident4;
 switch (EnumParIn){
  case Ident1:
 EnumParOut = Ident1;
 break;
 case Ident2:
  if (IntGlob  100){
 EnumParOut = Ident1;
 } else EnumParOut = Ident4;
  

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

[Dirk Grabbert]

Ok, I'm able to start the example shell right now. But I got the next 
problem.

Trying to run a js-script brings up an illegal instruction caused by mls. 
I think it's generated by the JIT, right?

The script I'm trying to run is a port of the dhrystone test (source: 
http://jsperf.com/pystone-js):

var LOOPS = 50;

var Ident1 = 1,
Ident2 = 2,
Ident3 = 3,
Ident4 = 4,
Ident5 = 5;

var TRUE = 1,
FALSE = 0;

var IntGlob = 0;
var BoolGlob = FALSE;
var Char1Glob = '\0';
var Char2Glob = '\0';
var Array1Glob = new Array(51);

for (var i = 0; i  Array1Glob.length; ++i) {
  Array1Glob[i] = 0
}

var Array2Glob = Array1Glob.map(function(n) {
return Array1Glob.slice();
});

var PtrGlb = null;
var PtrGlbNext = null;

var strings = {
someString:DHRYSTONE PROGRAM, SOME STRING,
fstString:DHRYSTONE PROGRAM, 1'ST STRING,
sndString:DHRYSTONE PROGRAM, 2'ND STRING
};

function main(){
Proc0();
}

function Record(PtrComp, Discr, EnumComp, IntComp, StringComp) {
  this.PtrComp = PtrComp || null;
  this.Discr = Discr || 0;
  this.EnumComp = EnumComp || 0;
  this.IntComp = IntComp || 0;
  this.StringComp = StringComp || 0;
}

function structassign(d,s){
d.PtrComp = s.PtrComp;
d.Discr = s.Discr;
d.EnumComp = s.EnumComp;
d.IntComp = s.IntComp;
d.StringComp = s.StringComp;
}

function clock(){
return new Date().valueOf() / 1000.0
}

function Proc0(){
var CharIndex;
var starttime, benchtime, nulltime;

var starttime = clock();
for(var i = 0; i  LOOPS; ++i);
nulltime = clock() - starttime;

PtrGlbNext = new Record();
PtrGlb = new Record();
PtrGlb.PtrComp = PtrGlbNext;
PtrGlb.Discr = Ident1;
PtrGlb.EnumComp = Ident3;
PtrGlb.IntComp = 40;
PtrGlb.StringComp = DHRYSTONE PROGRAM, SOME STRING; // im Original wird 
hier ein strcpy angewandt
var String1Loc = DHRYSTONE PROGRAM, 1'ST STRING; 

Array2Glob[8][7] = 10;

/* start timer */
starttime = clock();
for(var i = 0; i  LOOPS; ++i){
Proc5();
Proc4();
IntLoc1 = 2;
IntLoc2 = 3;
var String2Loc = DHRYSTONE PROGRAM, 2'ND STRING;  // im Original wird 
hier ein strcpy angewandt
var EnumLoc = Ident2;
BoolGlob = !Func2(String1Loc, String2Loc);

while(IntLoc1  IntLoc2){
IntLoc3 = 5 * IntLoc1 - IntLoc2;
Proc7(IntLoc1, IntLoc2, IntLoc3);
++IntLoc1;
}

Proc8(Array1Glob, Array2Glob, IntLoc1, IntLoc3);
Proc1(PtrGlb);

for (CharIndex = 'A'; CharIndex = Char2Glob; CharIndex = 
String.fromCharCode(CharIndex.charCodeAt(0) + 1)){ // string to int to 
string convertion required by js
if (EnumLoc == Func1(CharIndex, 'C'))
EnumLoc = Proc6(Ident1);
}

IntLoc3 = IntLoc2 * IntLoc1;
IntLoc2 = IntLoc3 / IntLoc1;
IntLoc2 = 7 * (IntLoc3 - IntLoc2) - IntLoc1;
IntLoc1 = Proc2(IntLoc1); // nicht by-reference ?
}

benchtime = clock() - starttime - nulltime;
print(JsPystone() time for  + LOOPS +  passes =  + benchtime);
print(This machine benchmarks at  +  (LOOPS / benchtime) +  
pystones/second);
// console.log(JsPystone() time for  + LOOPS +  passes =  + benchtime);
// console.log(This machine benchmarks at  +  (LOOPS / benchtime) +  
pystones/second);
}

function Proc1(PtrParIn){
var NextRecord = PtrParIn.PtrComp;

structassign(NextRecord, PtrGlb);
PtrParIn.IntComp = 5;
  NextRecord.IntComp = PtrParIn.IntComp;
  NextRecord.PtrComp = PtrParIn.PtrComp;
  Proc3(NextRecord.PtrComp);

  if(NextRecord.PtrComp == Ident1){
  NextRecord.IntComp = 6;
  NextRecord.EnumComp = Proc6(PtrParIn.EnumComp);
  NextRecord.PtrComp = PtrGlb.PtrComp;
  NextRecord.IntComp = Proc7(NextRecord.IntComp, 10);
  } else structassign(PtrParIn, NextRecord);
  
  NextRecord.PtrComp = null;
  
  return PtrParIn;
}

function Proc2(IntParIO){
var IntLoc, EnumLoc;

IntLoc = IntParIO + 10;
for(;;){
if (Char1Glob == 'A'){
--IntLoc;
IntParIO = IntLoc - IntGlob;
EnumLoc = Ident1;
}
if (EnumLoc == Ident1)
break;
}
}

function Proc3(PtrParOut){
if (PtrGlb !== null) {
PtrParOut = PtrGlb.PtrComp;
  } else {
IntGlob = 100;
  }
  PtrGlb.IntComp = Proc7(10, IntGlob);
  return PtrParOut;
}

function Proc4(){
var BoolLoc = Char1Glob == 'A';
BoolLoc |= BoolGlob;
Char2Glob = 'B';
}

function Proc5(){
Char1Glob = 'A';
BoolGlob = FALSE;
}

function Proc6(EnumParIn, EnumParOut){
var EnumParOut = EnumParIn;
if(!Func3(EnumParIn))
EnumParOut = Ident4;
switch (EnumParIn){
case Ident1:
EnumParOut = Ident1;
break;
case Ident2:
if (IntGlob  100){
EnumParOut = Ident1;
} else EnumParOut = Ident4;
break;
case Ident3:
EnumParOut = Ident2;
break;
case Ident4:
break;
case Ident5: 
EnumParOut = Ident3;
}
return EnumParOut;
}

function Proc7(IntParI1, IntParI2, IntParOut){
var IntLoc = IntParI1 + 2;
IntParOut = IntParI2 + IntLoc;

return IntParOut;
}

function Proc8(Array1Par, Array2Par, IntParI1, IntParI2) {
  var IntLoc = IntParI1 + 5;
  Array1Par[IntLoc] = IntParI2;
  Array1Par[IntLoc + 1] = Array1Par[IntLoc];
  Array1Par[IntLoc + 30] = IntLoc;
  // for IntIndex in range(IntLoc, IntLoc+2):
  for (var IntIndex = IntLoc; IntIndex  IntLoc + 2; ++IntIndex) {
Array2Par[IntLoc][IntIndex] = IntLoc;
  }
  Array2Par[IntLoc][IntLoc - 1] = 

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

[Rodolph Perfetta]

I sounds like auto detection is failing again, override it: --noenable-mls
should do it.

I can't push a patch right now so keep reporting any issues.

Thanks,
Rodolph.


On 22 July 2014 15:08, Dirk Grabbert dirk.grabb...@gmail.com wrote:

 Ok, I'm able to start the example shell right now. But I got the next
 problem.

 Trying to run a js-script brings up an illegal instruction caused by
 mls. I think it's generated by the JIT, right?

 The script I'm trying to run is a port of the dhrystone test (source:
 http://jsperf.com/pystone-js):

 var LOOPS = 50;

 var Ident1 = 1,
 Ident2 = 2,
 Ident3 = 3,
 Ident4 = 4,
 Ident5 = 5;

 var TRUE = 1,
 FALSE = 0;

 var IntGlob = 0;
 var BoolGlob = FALSE;
 var Char1Glob = '\0';
 var Char2Glob = '\0';
 var Array1Glob = new Array(51);

 for (var i = 0; i  Array1Glob.length; ++i) {
   Array1Glob[i] = 0
 }

 var Array2Glob = Array1Glob.map(function(n) {
 return Array1Glob.slice();
 });

 var PtrGlb = null;
 var PtrGlbNext = null;

 var strings = {
 someString:DHRYSTONE PROGRAM, SOME STRING,
 fstString:DHRYSTONE PROGRAM, 1'ST STRING,
 sndString:DHRYSTONE PROGRAM, 2'ND STRING
 };

 function main(){
 Proc0();
 }

 function Record(PtrComp, Discr, EnumComp, IntComp, StringComp) {
   this.PtrComp = PtrComp || null;
   this.Discr = Discr || 0;
   this.EnumComp = EnumComp || 0;
   this.IntComp = IntComp || 0;
   this.StringComp = StringComp || 0;
 }

 function structassign(d,s){
 d.PtrComp = s.PtrComp;
 d.Discr = s.Discr;
 d.EnumComp = s.EnumComp;
 d.IntComp = s.IntComp;
 d.StringComp = s.StringComp;
 }

 function clock(){
 return new Date().valueOf() / 1000.0
 }

 function Proc0(){
 var CharIndex;
 var starttime, benchtime, nulltime;

 var starttime = clock();
 for(var i = 0; i  LOOPS; ++i);
 nulltime = clock() - starttime;

 PtrGlbNext = new Record();
 PtrGlb = new Record();
 PtrGlb.PtrComp = PtrGlbNext;
 PtrGlb.Discr = Ident1;
 PtrGlb.EnumComp = Ident3;
 PtrGlb.IntComp = 40;
 PtrGlb.StringComp = DHRYSTONE PROGRAM, SOME STRING; // im Original wird
 hier ein strcpy angewandt
 var String1Loc = DHRYSTONE PROGRAM, 1'ST STRING;

 Array2Glob[8][7] = 10;

 /* start timer */
 starttime = clock();
 for(var i = 0; i  LOOPS; ++i){
 Proc5();
 Proc4();
 IntLoc1 = 2;
 IntLoc2 = 3;
 var String2Loc = DHRYSTONE PROGRAM, 2'ND STRING;  // im Original wird
 hier ein strcpy angewandt
 var EnumLoc = Ident2;
 BoolGlob = !Func2(String1Loc, String2Loc);

 while(IntLoc1  IntLoc2){
 IntLoc3 = 5 * IntLoc1 - IntLoc2;
 Proc7(IntLoc1, IntLoc2, IntLoc3);
 ++IntLoc1;
 }

 Proc8(Array1Glob, Array2Glob, IntLoc1, IntLoc3);
 Proc1(PtrGlb);

 for (CharIndex = 'A'; CharIndex = Char2Glob; CharIndex =
 String.fromCharCode(CharIndex.charCodeAt(0) + 1)){ // string to int to
 string convertion required by js
 if (EnumLoc == Func1(CharIndex, 'C'))
 EnumLoc = Proc6(Ident1);
 }

 IntLoc3 = IntLoc2 * IntLoc1;
 IntLoc2 = IntLoc3 / IntLoc1;
 IntLoc2 = 7 * (IntLoc3 - IntLoc2) - IntLoc1;
 IntLoc1 = Proc2(IntLoc1); // nicht by-reference ?
 }

 benchtime = clock() - starttime - nulltime;
 print(JsPystone() time for  + LOOPS +  passes =  + benchtime);
 print(This machine benchmarks at  +  (LOOPS / benchtime) + 
 pystones/second);
 // console.log(JsPystone() time for  + LOOPS +  passes =  +
 benchtime);
 // console.log(This machine benchmarks at  +  (LOOPS / benchtime) + 
 pystones/second);
 }

 function Proc1(PtrParIn){
 var NextRecord = PtrParIn.PtrComp;

 structassign(NextRecord, PtrGlb);
 PtrParIn.IntComp = 5;
   NextRecord.IntComp = PtrParIn.IntComp;
   NextRecord.PtrComp = PtrParIn.PtrComp;
   Proc3(NextRecord.PtrComp);

   if(NextRecord.PtrComp == Ident1){
   NextRecord.IntComp = 6;
   NextRecord.EnumComp = Proc6(PtrParIn.EnumComp);
   NextRecord.PtrComp = PtrGlb.PtrComp;
   NextRecord.IntComp = Proc7(NextRecord.IntComp, 10);
   } else structassign(PtrParIn, NextRecord);

   NextRecord.PtrComp = null;

   return PtrParIn;
 }

 function Proc2(IntParIO){
 var IntLoc, EnumLoc;

 IntLoc = IntParIO + 10;
 for(;;){
 if (Char1Glob == 'A'){
 --IntLoc;
 IntParIO = IntLoc - IntGlob;
 EnumLoc = Ident1;
 }
 if (EnumLoc == Ident1)
 break;
 }
 }

 function Proc3(PtrParOut){
 if (PtrGlb !== null) {
 PtrParOut = PtrGlb.PtrComp;
   } else {
 IntGlob = 100;
   }
   PtrGlb.IntComp = Proc7(10, IntGlob);
   return PtrParOut;
 }

 function Proc4(){
 var BoolLoc = Char1Glob == 'A';
 BoolLoc |= BoolGlob;
 Char2Glob = 'B';
 }

 function Proc5(){
 Char1Glob = 'A';
 BoolGlob = FALSE;
 }

 function Proc6(EnumParIn, EnumParOut){
 var EnumParOut = EnumParIn;
 if(!Func3(EnumParIn))
 EnumParOut = Ident4;
 switch (EnumParIn){
 case Ident1:
 EnumParOut = Ident1;
 break;
 case Ident2:
 if (IntGlob  100){
 EnumParOut = Ident1;
 } else EnumParOut = Ident4;
 break;
 case Ident3:
 EnumParOut = Ident2;
 break;
 case Ident4:
 break;
 case Ident5:
 EnumParOut = Ident3;
 }
 return EnumParOut;
 }

 function Proc7(IntParI1, IntParI2, IntParOut){
 var IntLoc = IntParI1 + 2;
 IntParOut = IntParI2 + IntLoc;

 return 

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

[Dirk Grabbert]

Here is a screenshot of gdb.

https://lh3.googleusercontent.com/-l4tjqgj9A7w/U8y9EFlur2I/AQs/iL4WdoCNdPc/s1600/V8_gdb_out_movw.png
Cheers,
Dirk.

Am Freitag, 18. Juli 2014 17:37:13 UTC+2 schrieb Ross McIlroy:

 I don't have an armv6 device to test on here, but I tried with a simulator 
 build with added asserts in Assembler::movw/movt to ensure that they aren't 
 emitted when targeting armv6 and these asserts didn't trigger, so I'm not 
 sure where the movw instruction is being emitted.

 Could you let me know the exact version / revision of V8 you are building 
 and the stack trace generated by gdb?

 Cheers,
 Ross
  

 On 17 July 2014 17:04, Dirk Grabbert dirk.g...@gmail.com javascript: 
 wrote:
 I'm trying to build V8 for the Raspberry Pi (toolchain from the 
 archlinuxarm website, nodejs works fine). Buildprocess works without any 
 errors, but trying to execute the shell or d8 brings up an illegal 
 instruction. GDB shows that it's movw.
 To build I've exported CC, CXX, LINK, AR and LD and then run make 
 snapshot=off i18nsupport=off armv7=false armfpu=vfp2 arm.release -j5 (or 
 armfpu=vfp, there is no change in the output).
 -- 
 -- 
 v8-users mailing list
 v8-u...@googlegroups.com
  javascript: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 v8-users+u...@googlegroups.com javascript:.
  For more options, visit https://groups.google.com/d/optout



-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

[Ross McIlroy]

Hi Dirk,

The stack trace looks like the movw is being emitted in generated code.
 Could you try again with a debug build of V8 which includes r22512 (
https://codereview.chromium.org/402923002/) - this should fail with an
ASSERT error if V8 tries to emit a movw instruction on an armv6 target.

If this doesn't throw an assert, then it looks like the runtime probing is
incorrectly concluding that the device is capable of running armv7 code
even although V8 was only compiled for armv6.  Could you send the output of
running the following commands in gdb at the point of the crash:
  p v8::internal::CpuFeatures::PrintFeatures()
and
  p v8::internal::CpuFeatures::PrintTarget()

Cheers,
Ross



On 21 July 2014 10:00, Dirk Grabbert dirk.grabb...@gmail.com wrote:

 This is the line I'm using to find any movw in the objdump of the shell:

 arm-unknown-linux-gnueabihf-objdump -d out/arm.release/shell | grep -i
 movw


 Got this output:

 0006e738 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv:
6eba4: eb09774c bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f060: eb09761d bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f1e4: eb0975bc bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f28c: eb097592 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f2cc: eb097582 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f39c: eb09754e bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f45c: eb09751e bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f7ec: eb09743a bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f82c: eb09742a bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
76854: eb095820 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
76868: ebffdfb2 bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
76874: ebffdfaf bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
76894: eb095810 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
768a8: ebffdfa2 bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
768b4: ebffdf9f bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
769dc: eb0957be bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
769ec: ebffdf51 bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
769f8: ebffdf4e bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
7724c: eb0955a2 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
77260: ebffdd34 bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
77274: ebffdd2f bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
77590: eb0954d1 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
775a8: ebffdc62 bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
775bc: ebffdc5d bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
   151b70: eb05eb59 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   151df4: eb05eab8 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   152c44: eb05e724 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   152c80: eb05e715 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   152dd4: eb05e6c0 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   152e10: eb05e6b1 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   152ef0: eb05e679 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153128: eb05e5eb bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153164: eb05e5dc bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1533b0: eb05e549 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1533ec: eb05e53a bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153750: eb05e461 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1537a8: eb05e44b bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   15385c: eb05e41e bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153898: eb05e40f bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1539d4: eb05e3c0 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153a10: eb05e3b1 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153b4c: eb05e362 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153b88: eb05e353 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153cb4: eb05e308 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153cf0: eb05e2f9 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1541c0: eb05e1c5 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1541fc: eb05e1b6 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1559f4: eb05dbb8 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   155a30: eb05dba9 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   155b10: eb05db71 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1587d8: eb05d03f bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   159a98: eb05cb8f bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   159ad4: eb05cb80 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   159c08: eb05cb33 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   159fc4: eb05ca44 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   15a000: eb05ca35 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   15a44c: eb05c922 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   15a488: eb05c913 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   15b91c: eb05c3ee bl 2cc8dc 

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

[Ross McIlroy]

Actually, Rodolph just pointed out that running: d8 --help | head -n 2 will
output the same information as
v8::internal::CpuFeatures::PrintFeatures/PrintTarget,
so you should be able to do this instead of the gdb commands I suggested in
the last message.

Cheers,
Ross



On 21 July 2014 17:30, Ross McIlroy rmcil...@chromium.org wrote:

 Hi Dirk,

 The stack trace looks like the movw is being emitted in generated code.
  Could you try again with a debug build of V8 which includes r22512 (
 https://codereview.chromium.org/402923002/) - this should fail with an
 ASSERT error if V8 tries to emit a movw instruction on an armv6 target.

 If this doesn't throw an assert, then it looks like the runtime probing is
 incorrectly concluding that the device is capable of running armv7 code
 even although V8 was only compiled for armv6.  Could you send the output of
 running the following commands in gdb at the point of the crash:
   p v8::internal::CpuFeatures::PrintFeatures()
 and
   p v8::internal::CpuFeatures::PrintTarget()

 Cheers,
 Ross



 On 21 July 2014 10:00, Dirk Grabbert dirk.grabb...@gmail.com wrote:

 This is the line I'm using to find any movw in the objdump of the shell:

 arm-unknown-linux-gnueabihf-objdump -d out/arm.release/shell | grep -i
 movw


 Got this output:

 0006e738 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv:
6eba4: eb09774c bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f060: eb09761d bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f1e4: eb0975bc bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f28c: eb097592 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f2cc: eb097582 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f39c: eb09754e bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f45c: eb09751e bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f7ec: eb09743a bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
6f82c: eb09742a bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
76854: eb095820 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
76868: ebffdfb2 bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
76874: ebffdfaf bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
76894: eb095810 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
768a8: ebffdfa2 bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
768b4: ebffdf9f bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
769dc: eb0957be bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
769ec: ebffdf51 bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
769f8: ebffdf4e bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
7724c: eb0955a2 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
77260: ebffdd34 bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
77274: ebffdd2f bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
77590: eb0954d1 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
775a8: ebffdc62 bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
775bc: ebffdc5d bl 6e738
 _ZNK2v88internal11Instruction18ImmedMovwMovtValueEv
   151b70: eb05eb59 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   151df4: eb05eab8 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   152c44: eb05e724 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   152c80: eb05e715 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   152dd4: eb05e6c0 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   152e10: eb05e6b1 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   152ef0: eb05e679 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153128: eb05e5eb bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153164: eb05e5dc bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1533b0: eb05e549 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1533ec: eb05e53a bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153750: eb05e461 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1537a8: eb05e44b bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   15385c: eb05e41e bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153898: eb05e40f bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1539d4: eb05e3c0 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153a10: eb05e3b1 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153b4c: eb05e362 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153b88: eb05e353 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153cb4: eb05e308 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   153cf0: eb05e2f9 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1541c0: eb05e1c5 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1541fc: eb05e1b6 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1559f4: eb05dbb8 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   155a30: eb05dba9 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   155b10: eb05db71 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   1587d8: eb05d03f bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   159a98: eb05cb8f bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   159ad4: eb05cb80 bl 2cc8dc _ZN2v88internal9Assembler6IsMovWEi
   159c08: eb05cb33 bl 

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

[Dirk Grabbert]

Great thx for your respond.

I'm using the version from git (currently 9ac5e7f), but I've also tried 
older versions. I've dumped the shell and all the other created object 
files, didn't find any movw instruction there. I don't know why it crashs 
caused by this instruction neither where it comes from. Maybe it is 
generated by some javascript code for the v8 example shell?

I'm not at home / work at the moment, so I'm going to post the stack trace 
tomorrow evening or monday morning.

Am Freitag, 18. Juli 2014 17:37:13 UTC+2 schrieb Ross McIlroy:

 I don't have an armv6 device to test on here, but I tried with a simulator 
 build with added asserts in Assembler::movw/movt to ensure that they aren't 
 emitted when targeting armv6 and these asserts didn't trigger, so I'm not 
 sure where the movw instruction is being emitted.

 Could you let me know the exact version / revision of V8 you are building 
 and the stack trace generated by gdb?

 Cheers,
 Ross
  

 On 17 July 2014 17:04, Dirk Grabbert dirk.g...@gmail.com javascript: 
 wrote:
 I'm trying to build V8 for the Raspberry Pi (toolchain from the 
 archlinuxarm website, nodejs works fine). Buildprocess works without any 
 errors, but trying to execute the shell or d8 brings up an illegal 
 instruction. GDB shows that it's movw.
 To build I've exported CC, CXX, LINK, AR and LD and then run make 
 snapshot=off i18nsupport=off armv7=false armfpu=vfp2 arm.release -j5 (or 
 armfpu=vfp, there is no change in the output).
 -- 
 -- 
 v8-users mailing list
 v8-u...@googlegroups.com
  javascript: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 v8-users+u...@googlegroups.com javascript:.
  For more options, visit https://groups.google.com/d/optout



-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building V8 for ARMv6 (Raspberry Pi), got illegal instruction (movw)

[Ross McIlroy]

I don't have an armv6 device to test on here, but I tried with a simulator
build with added asserts in Assembler::movw/movt to ensure that they aren't
emitted when targeting armv6 and these asserts didn't trigger, so I'm not
sure where the movw instruction is being emitted.

Could you let me know the exact version / revision of V8 you are building
and the stack trace generated by gdb?

Cheers,
Ross


 On 17 July 2014 17:04, Dirk Grabbert dirk.grabb...@gmail.com wrote:
 I'm trying to build V8 for the Raspberry Pi (toolchain from the
 archlinuxarm website, nodejs works fine). Buildprocess works without any
 errors, but trying to execute the shell or d8 brings up an illegal
 instruction. GDB shows that it's movw.
 To build I've exported CC, CXX, LINK, AR and LD and then run make
 snapshot=off i18nsupport=off armv7=false armfpu=vfp2 arm.release -j5 (or
 armfpu=vfp, there is no change in the output).
 --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 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 v8-users+unsubscr...@googlegroups.com.
  For more options, visit https://groups.google.com/d/optout

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Building v8 for Android, ARM binary sizes

[Ben Noordhuis]

On Wed, Oct 23, 2013 at 1:12 PM, Pris Matic prismatic.proj...@gmail.com wrote:
 Hi,

 I built v8 for Android three different ways and the file sizes for the
 resulting binaries seemed a little 'off' compared to a value I got from the
 site of a mobile development framework (Appcelerator)  that embeds v8 into
 their Android applications. They mentioned that the v8 binaries should be
 around 6mb. It's unclear whether that estimate was talking about static or
 shared libs or even what version of v8 it was referencing, but since my
 builds seem so different, I was hoping for some clarification.

 My builds:

 1. Default config using the wiki instructions (make android_arm.release)
 which builds:
 * libv8_base.a - 1.3mb
 * libv8_snapshot.a - 3.3kb
 * libv8_nosnapshot.arm.a - 3.3kb

 This doesn't seem right for some reason... the binaries seem too small,
 especially the snapshot ones. I need to move these libs to another machine
 for development... but it seems like I have run into the same 'thin archive'
 build issue as: https://groups.google.com/forum/#!topic/v8-users/cl2rPGbqsvQ
 (is this assumption correct?), so I modified /tools/gyp/v8.gyp and added
 'standalone_static_library': 1 to the static lib targets...

 2. After modifying v8.gyp and rebuilding I get:
 * libv8_base.a - 17.2mb
 * libv8_snapshot.a - 350kb
 * libv8_nosnapshot.arm.a - 1.0mb

 3. I also built v8 as a shared library. I passed snapshot=no when building.
 * libv8.so - 7.4mb


 Are these binary sizes right? If the latter two are correct, are there any
 build options I can pass to reduce the size of the binaries a bit?


 Preet

They look about right to me.  You can run the archives through
strip(1) or link with -Wl,--strip-all or -Wl,--strip-debug to remove
the (debug) symbol sections.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [v8-users] Building v8 for ARMv5

[Rodolph Perfetta]

V8 requires hardware floating point.

Regards,
Rodolph.



On 28 August 2013 14:53, mar...@nuuz.at wrote:

 I'm trying to use version 3.20.16 of v8 under an ARM926ej-s (ARMv5) board,
 where /proc/cpuinfo shows the following information:

 # cat /proc/cpuinfo
 Processor : ARM926EJ-S rev 5 (v5l)
 BogoMIPS : 226.09
 Features : swp half thumb fastmult edsp java
 CPU implementer : 0x41
 CPU architecture: 5TEJ
 CPU variant : 0x0
 CPU part : 0x926
 CPU revision : 5

 Hardware : Freescale i.MX28 (Device Tree)
 Revision : 
 Serial : 

 So apparently, I have to build without floating-point support, which I
 tried in the following way:

 # make arm.debug snapshot=false armv7=false armfpu= werror=no
 library=shared

 However, when using the resulting library on the target system, it ends up
 in an Illegal Instruction, which comes due to a vpush instruction from
 within v8:

 Program received signal SIGILL, Illegal instruction.
 0x2010a044 in ?? ()
 (gdb) bt
 #0  0x2010a044 in ?? ()
 #1  0xb697cf38 in ?? () from /lib/libv8.so
 Backtrace stopped: previous frame identical to this frame (corrupt stack?)
 (gdb) x/2i $pc-4
0x2010a040: push {r4, r5, r6, r7, r8, r9, r10, r11, lr}
 = 0x2010a044: vpush {d8-d15}

 Is there any possibility to use v8 under systems without floating-point
 support? And if so, which are the correct make-flags?

 The cross-compiler I'm using is gcc 4.6.1.

 Thanks,
 Marcus

  --
 --
 v8-users mailing list
 v8-users@googlegroups.com
 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 v8-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
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 v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [v8-users] Building v8

[Jakob Kummerow]

On Sat, Dec 1, 2012 at 6:25 PM, Maksim Lukyanchenko 
maksim.lukyanche...@gmail.com wrote:

 I'm trying to compile V8 on Win7 for VS2010:

 svn co http://gyp.googlecode.com/svn/trunk build/gyp

 svn co http://src.chromium.org/svn/trunk/tools/third_party/python_26 
 third_party/python_26

 svn co http://src.chromium.org/svn/trunk/deps/third_party/cygwin 
 third_party/cygwin


 1) And when I try:
 c:\v8 third_party/python_26/python.exe build\gyp_v8

 I get the message:
 [Errno2] No such file or directory


This should work, and last time I tried it, it did work for me. Please try
to figure out which file it is complaining about. When you use backslashes
instead of slashes, does that change anything? Can you manually verify that
third_party\python_26\python.exe and build\gyp_v8 exist?



 And it's I can understand.

 2) When I try:
 c:\v8 third_party/python_26/python.exe build\gyp


This can't work.


 I get the message:
 third_party/python_26/python.exe: can't find '__main__.py' in 'build\\gyp'

 3) When I try:
 c:\v8 third_party/python_26/python.exe build\gyp\gyp


This can't work either.


 I get the message:
 gyp: usage: gyp [options ...][build_file ...]
 gyp: error: no build_file

 What am I doing wrong and how do I compile V8?

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

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

Re: [v8-users] Building v8

[Maksim Lukyanchenko]

Yes, I lose gyp_v8. When I updated:

svn co http://gyp.googlecode.com/svn/trunk build/gyp.

I succesfully compiled v8. 

Thank you, Jakob.

On Sat, Dec 1, 2012 at 6:25 PM, Maksim Lukyanchenko 
maksim.lu...@gmail.comjavascript:
  wrote:

 I'm trying to compile V8 on Win7 for VS2010:

 svn co http://gyp.googlecode.com/svn/trunk build/gyp

 svn co http://src.chromium.org/svn/trunk/tools/third_party/python_26 
 third_party/python_26

 svn co http://src.chromium.org/svn/trunk/deps/third_party/cygwin 
 third_party/cygwin


 1) And when I try:
 c:\v8 third_party/python_26/python.exe build\gyp_v8

 I get the message:
 [Errno2] No such file or directory


 This should work, and last time I tried it, it did work for me. Please try 
 to figure out which file it is complaining about. When you use backslashes 
 instead of slashes, does that change anything? Can you manually verify that 
 third_party\python_26\python.exe and build\gyp_v8 exist?
  


 And it's I can understand.

 2) When I try:
 c:\v8 third_party/python_26/python.exe build\gyp


 This can't work.
  

 I get the message:
 third_party/python_26/python.exe: can't find '__main__.py' in 
 'build\\gyp'

 3) When I try:
 c:\v8 third_party/python_26/python.exe build\gyp\gyp


 This can't work either.
  

 I get the message:
 gyp: usage: gyp [options ...][build_file ...]
 gyp: error: no build_file

 What am I doing wrong and how do I compile V8?

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




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

Re: [v8-users] Building v8 as a static library (libv8.a) using GYP build?

[Jakob Kummerow]

(inline)

On Sat, Mar 3, 2012 at 07:21, Jeff Rogers jeffcrog...@gmail.com wrote:

 I was wondering if it is possible to build v8 as a static library
 (libv8.a) on Mac or Linux using the GYP build? Looking at the gyp files, it
 seems like the new build system will only build shell executables and
 smaller component libraries (libv8_base, libv8_nosnapshot,
 libpreprocessor_lib), or a shared library when component=shared_library.


Yep, that seems to be the case, and it is sufficient for all clients of V8
that I know of.


 Specifying component=static_library or library=static as was supported in
 the Scons build does not generate libv8.a.


There's no need to explicitly specify it as it's the default behavior
anyway.


 In particular the v8.gyp sets the type to none unless shared is specified
 so I'm guessing that has something to do with it. I cannot get it to work
 so far.


Why do you need libv8.a in the first place? Look at d8.gyp for an example
how you can statically link against V8. It just works. Generally
speaking, if you have a choice at all, you should opt for dynamic linking
(i.e. shared libraries).

If the current capabilities of the GYP build don't fit your needs, we'd be
happy to accept patches (as long as they don't break other build scenarios,
of course). If you help me understand your requirements, I might even look
into it myself eventually, but it this point I can't promise anything.

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

Re: [v8-users] Building v8 as a static library (libv8.a) using GYP build?

[Jakob Kummerow]

On Mon, Mar 5, 2012 at 14:23, Bryan White nickt...@gmail.com wrote:

  Yep, that seems to be the case, and it is sufficient for all clients of
 V8
  that I know of.

 I don't know what you definition of 'client' is in this context,


Projects depending on V8.


 but I
 for one use the static libv8 and would be very concerned if the option
 to build this was dropped.

  There's no need to explicitly specify it as it's the default behavior
  anyway.

 It sounds like you are saying the static lib is built by default.  Is
 that true?  It contradicts most everything else you say in this post.


What I meant is that component=static_library is the default setting, so
there's no need to explicitly specify this on the command line.

 Why do you need libv8.a in the first place? Look at d8.gyp for an example
  how you can statically link against V8. It just works. Generally
 speaking,
  if you have a choice at all, you should opt for dynamic linking (i.e.
 shared
  libraries).

 I am uncomfortable dynamically linking against projects in very active
 development.  We are a small company with v8 running on half a dozen
 different servers.  There is a high likely hood of breaking things by
 deploying an add but forgetting to deploy an updated shared lib.


 I am not aware that statically linking to a .so is possible.


Right, and I didn't say it was.
Also, I didn't ask why you would want to link against V8 statically -- my
question was, why you need precisely libv8.a (rather than libv8_base.a +
libv8_nosnapshot.a + libv8_snapshot.a) in order to do that.


  I scanned the d8.gyp file.  I don't speak gyp but I did not see anything
 about this.


The d8 target, which has type executable, specifies a dependency on the
v8 target, which has type none (but in turn depends on other targets
that produce .a files). That's enough to have the d8 binary statically link
in everything. Most of us developers do that all the time, and the standard
Chrome/Chromium build works similarly.

Things might not be quite as easy if you don't use GYP for your downstream
project, but in that case you're more or less on your own anyway. I'm happy
to help if I have time, and as I said before you can also submit a patch
yourself that adds functionality you need that might be missing.

In any case, it is the intention of the V8 team to stop supporting two
build systems, so the SCons build is slated to be dropped. That doesn't
mean that the option to link statically is going away, it just so happens
that the GYP build doesn't generate a libv8.a as the SCons build did, and
so far I haven't considered this a problem because both shared and static
linking is still possible. This also means that I haven't looked into how
much work it would be to get a libv8.a if one so desired.

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

Re: [v8-users] Building v8 as a static library (libv8.a) using GYP build?

[Jeff Rogers]

Thanks Jakob, that makes sense. I've confirmed that by linking to those 
libraries it works. I may have been thrown off initially by the fact that 
the .a files are buried so deep in the build output, basically had to grep. 
I did look at the d8 build before, but it of course just says v8.gyp is a 
dependency it *just works*, linking to it externally wasn't as clear.

Sorry for the confusion,
Jeff


On Monday, 5 March 2012 05:28:42 UTC-5, Jakob Kummerow wrote:

 (inline)

 On Sat, Mar 3, 2012 at 07:21, Jeff Rogers jeffcrog...@gmail.com wrote:

 I was wondering if it is possible to build v8 as a static library 
 (libv8.a) on Mac or Linux using the GYP build? Looking at the gyp files, it 
 seems like the new build system will only build shell executables and 
 smaller component libraries (libv8_base, libv8_nosnapshot, 
 libpreprocessor_lib), or a shared library when component=shared_library.


 Yep, that seems to be the case, and it is sufficient for all clients of V8 
 that I know of.
  

 Specifying component=static_library or library=static as was supported in 
 the Scons build does not generate libv8.a. 


 There's no need to explicitly specify it as it's the default behavior 
 anyway.
  

 In particular the v8.gyp sets the type to none unless shared is specified 
 so I'm guessing that has something to do with it. I cannot get it to work 
 so far.


 Why do you need libv8.a in the first place? Look at d8.gyp for an example 
 how you can statically link against V8. It just works. Generally 
 speaking, if you have a choice at all, you should opt for dynamic linking 
 (i.e. shared libraries).

 If the current capabilities of the GYP build don't fit your needs, we'd be 
 happy to accept patches (as long as they don't break other build scenarios, 
 of course). If you help me understand your requirements, I might even look 
 into it myself eventually, but it this point I can't promise anything.



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

Re: [v8-users] Building V8 under CentOS 5.5

[Jakob Kummerow]

Try the strictaliasing=off flag.

Out of interest, what does g++ --version print?

On Thu, Jan 26, 2012 at 17:24, Alex Paransky ap...@standardset.com wrote:

 I am trying to build lastest from Master with V8, but failing at the
 first step of building V8:
 cat /etc/redhat-release

 CentOS release 5.5 (Final)
 scons arch=x64

 scons: Reading SConscript files ...
 scons: done reading SConscript files.
 scons: Building targets ...
 g++ -o obj/release/accessors.o -c -fno-rtti -fno-exceptions -
 fvisibility=hidden -Wall -Werror -W -Wno-unused-parameter -Wnon-
 virtual-dtor -pedantic -m64 -O3 -fomit-frame-pointer -fdata-sections
 -
 ffunction-sections -ansi -DV8_TARGET_ARCH_X64 -
 DENABLE_DEBUGGER_SUPPORT -Isrc src/accessors.cc
 cc1plus: warnings being treated as errors
 src/heap.h: In member function 'v8::internal::byte**
 v8::internal::Heap::store_buffer_top_address()':
 src/heap.h:1173: warning: dereferencing type-punned pointer will
 break
 strict-aliasing rules
 scons: *** [obj/release/accessors.o] Error 1
 scons: building terminated because of errors.

 Has anyone done this and can offer some advice?
 Thanks.
 -AP_

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


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