Re: [v8-users] V8 build error on the CentOS 7

2019-12-09 Thread Ivan Pizhenko
Yes, I've found them in some .gni and .gn files and commented out. Regenerated build files and now build is running. I am using clang 7 from some previous stable version of V8. On Monday, December 9, 2019 at 11:58:51 AM UTC+2, Jakob Kummerow wrote: > > On Fri, Dec 6, 2019 at 10:22 PM Ivan Pizhen

Re: [v8-users] V8 build error on the CentOS 7

2019-12-09 Thread Jakob Kummerow
On Fri, Dec 6, 2019 at 10:22 PM Ivan Pizhenko wrote: > Doesn't work. Seems like newer clang is required due to some options in > the command line. > > *error: unknown warning option '-Wno-implicit-int-float-conversion'; did > you mean '-Wno-float-overflow-conversion'? > [-Werror,-Wunknown-warning

Re: [v8-users] V8 build error on the CentOS 7

2019-12-06 Thread Ivan Pizhenko
w/o sysroot - gives errors, and I can't find how to get required packages, maybe GObject v2 is not on CentOS 7. Got one more idea - build clang 10.0.0 from sources on the centos7. $ gn gen out.gn.linux/x64.debug ERROR at //build/config/linux/pkg_config.gni:103:17: Script returned non-zero exit

Re: [v8-users] V8 build error on the CentOS 7

2019-12-06 Thread Ivan Pizhenko
Doesn't work. Seems like newer clang is required due to some options in the command line. ninja: Entering directory `out.gn.linux/x64.debug' [1/1302] ../../third_party/llvm-build/Release+Asserts/bin/clang++ -MMD -MF obj/torque_base/class-debug-reader-generator.o.d -DUSE_UDEV -DUSE_AURA=1 -DUSE_

Re: [v8-users] V8 build error on the CentOS 7

2019-12-06 Thread Jakob Kummerow
> > what about following idea: I am actually upgrading from 7.0.276.32, which > I could build a year ago on the CentOS 7 using version of clang supplied at > that moment, and I have my own archive of all that stuff. So, what if I > take that older version of clang? Are there any changes in V8 that

Re: [v8-users] V8 build error on the CentOS 7

2019-12-06 Thread Ivan P.
Thank you, I will try. But what about following idea: I am actually upgrading from 7.0.276.32, which I could build a year ago on the CentOS 7 using version of clang supplied at that moment, and I have my own archive of all that stuff. So, what if I take that older version of clang? Are there an

Re: [v8-users] V8 build error on the CentOS 7

2019-12-06 Thread Jakob Kummerow
You can try adding: is_clang = false use_sysroot = false to args.gn, but do note that this configuration is not officially supported. If it works, you're in luck; if it doesn't, then CentOS 7 is simply too old. (Side note: the recommended flow is to use "gn args " to edit the args, instead of ed

[v8-users] V8 build error on the CentOS 7

2019-12-06 Thread Ivan P.
Hi, I'm trying to build on the CentOS 7 current stable version of V8 7.8.279.23 (i.e. version picked from the current stable Chrome version 78.0.3904.108) and getting error. Here's what I've done: I've checked out sources and synchronized dependencies. I've prepared following gn config file

[v8-users] V8 Build error on Ubuntu 16.04.1 LTS

2016-11-01 Thread Pete Robie
The current version of V8 for the Ubuntu 16.04.1 LTS packages are as follows. libv8-3.14-dbg/xenial 3.14.5.8-5ubuntu2 amd64 libv8-3.14-dev/xenial 3.14.5.8-5ubuntu2 amd64 libv8-3.14.5/xenial,now 3.14.5.8-5ubuntu2 amd64 [residual-config] libv8-dev/xenial 3.14.5.8-5ubuntu2 amd64 The instructions t

Re: [v8-users] v8 build error

2016-02-08 Thread Joe Harrington
Installed to root of drive, reset all environment paths, and all problems went away. I think it was having problem with long pathname. :/ -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to th

Re: [v8-users] v8 build error

2016-02-08 Thread Jakob Kummerow
Well, please double-check for typos. If you look around File "C:\Users\JH\Documents\Libs\depot_tools\v8\build\vs_toolchain.py", > line 40, in SetEnvironmentAndGetRuntimeDllDirs you'll see that a few lines before it checks for that environment variable, and won't proceed to the code that later

Re: [v8-users] v8 build error

2016-02-08 Thread Joe Harrington
No. On Monday, February 8, 2016 at 7:15:10 AM UTC-8, Jakob Kummerow wrote: > > On Mon, Feb 8, 2016 at 3:23 PM, Joe Harrington > wrote: > >> >>> C:\Users\JH\Documents\Libs\depot_tools>python.exe v8\build\gyp_v8 >>> -Dtarget_arch=x64 -Dcomponent=shared_library >>> Please follow the instructions at

Re: [v8-users] v8 build error

2016-02-08 Thread Joe Harrington
No. On Mon, Feb 8, 2016 at 7:14 AM, Jakob Kummerow wrote: > On Mon, Feb 8, 2016 at 3:23 PM, Joe Harrington > wrote: > >> >>> C:\Users\JH\Documents\Libs\depot_tools>python.exe v8\build\gyp_v8 >>> -Dtarget_arch=x64 -Dcomponent=shared_library >>> Please follow the instructions at >>> http://www.ch

Re: [v8-users] v8 build error

2016-02-08 Thread Jakob Kummerow
On Mon, Feb 8, 2016 at 3:23 PM, Joe Harrington wrote: > >> C:\Users\JH\Documents\Libs\depot_tools>python.exe v8\build\gyp_v8 >> -Dtarget_arch=x64 -Dcomponent=shared_library >> Please follow the instructions at >> http://www.chromium.org/developers/how-tos/build-instructions-windows >> > That link

Re: [v8-users] v8 build error

2016-02-08 Thread Joe Harrington
> > > C:\Users\JH\Documents\Libs\depot_tools>python.exe v8\build\gyp_v8 > -Dtarget_arch=x64 -Dcomponent=shared_library > Please follow the instructions at > http://www.chromium.org/developers/how-tos/build-instructions-windows > Traceback (most recent call last): > File "v8\build\gyp_v8", line

Re: [v8-users] v8 build error

2016-02-08 Thread Jakob Kummerow
Are you looking for https://github.com/v8/v8/wiki/Building%20with%20Gyp#building-1? On Mon, Feb 8, 2016 at 10:18 AM, Joe Harrington wrote: > Followed the instructions on the page and have yet to get to where it > makes the build files. :( > > -- > -- > v8-users mailing list > v8-users@googlegrou

Re: [v8-users] v8 build error

2016-02-08 Thread Joe Harrington
Followed the instructions on the page and have yet to get to where it makes the build files. :( -- -- 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 unsu

Re: [v8-users] v8 build error

2016-02-08 Thread Jakob Kummerow
How did you check out V8? Did you follow the instructions at https://github.com/v8/v8/wiki/Using%20Git#how-to-start? (My guess would be that you simply "git clone"d the main repository. Doing so wouldn't run "gclient sync", so you'd end up missing all third-party dependencies, one of which is tool

[v8-users] v8 build error

2016-02-07 Thread Joe Harrington
I'm new to building v8 and i'm getting this error when I try build gyp_v8 (using win 10/visual c++ 2015 community): updating projects from gyp files python: can't open file '../tools/clang/scripts/update.py' : [Errno 2] no such file or directory gyp: call to 'python ../tools/clang/scripts/update.

Re: [v8-users] v8 build error: ar: illegal option -- T

2013-08-19 Thread Ben Noordhuis
On Mon, Aug 19, 2013 at 9:31 AM, dan wu wrote: > when I build v8 on RHEL5.4,Getting following error: ar: illegal option -- T > > I think this is beacuse my AR version is old ,it can not support "-T" > option,but I do not want to upgrade binutils. How can I remove "-T" option? > > I would appreciat

[v8-users] v8 build error: ar: illegal option -- T

2013-08-19 Thread dan wu
when I build v8 on RHEL5.4,Getting following error: ar: illegal option -- T I think this is beacuse my AR version is old ,it can not support "-T" option,but I do not want to upgrade binutils. How can I remove "-T" option? I would appreciate any help, thank you. -- -- v8-users mailing list v

[v8-users] v8 build error

2012-02-10 Thread Sivyer Lu
Hi, I'm runing from cmd cd D:\Program Files\Microsoft Visual Studio 10.0\VC vcvarsall.bat x86 cd d:\v8\ scons mode=debug library=shared env="PATH:%PATH%,LIB:%LIB %,INCLUDE:%INCLUDE%" but I get this error: 正在创建库 v8preparser_g.lib 和对象 v8preparser_g.exp conversions.obj