V8 build failed on Redhat

Shuai Yuan

unread,

Nov 20, 2015, 7:07:35 PM11/20/15

to v8-users

Version: <4.6.88>
OS: <Red Hat Enterprise Linux 6.x >
Architecture: <x64>

Hi,

I tried the following to build 4.6.88 of v8 on this rhel6 machine.

The gcc version on this machine was upgraded to 4.8.2:
$gcc --version
gcc (GCC) 4.8.2 20131212 (Red Hat 4.8.2-8)

The make version on this machine was 3.8.1, which should be fine according to other posts. 
$ make --version
GNU Make 3.8.1
(I later updated it to 4.1 and it didn't work either. )

The following command was able to build successfully at first.
$make -j8 GYPFLAGS="-Dv8_use_external_startup_data=0 -Dcomponent=shared_library" werror=no x64.release

I got the .so libraries in v8/out/x64.release/lib.target, but when I tried to build x64.debug after this, it gave seg fault. And from here I could not even re-make x64.release, even after make clean.

I tried to re-fetch v8 and build from a clean start, it didn't help either. I cannot repeat what I got before.
Now the error message after the above command is as below:

PYTHONPATH="/space/v8/tools/generate_shim_headers:/space/v8/build::/space/v8/build/gyp/pylib:" \
GYP_GENERATORS=make \
build/gyp/gyp --generator-output="out" build/all.gyp \
              -Ibuild/standalone.gypi --depth=. \
              -Dv8_target_arch=x64 \
               -Dtarget_arch=x64 \
               \
              -S.x64.release -Dv8_use_external_startup_data=0 -Dcomponent=shared_library
Makefile:434: recipe for target 'out/Makefile.x64.release' failed
make: *** [out/Makefile.x64.release] Segmentation fault (core dumped)

Please help! Thank you so much!

Best,
Shuai

Shuai Yuan

unread,

Nov 21, 2015, 2:14:29 AM11/21/15

to v8-users

Follow up on this issue, it turns out to be something about python:

I obtained core dump file of the seg fault and figured it happened during executing gyp_main.py as shown below:

python build/gyp/gyp_main.py --generator-output=out build/all.gyp -Ibuild/stand --depth .

Then I debugged and it turns out the Load() in v8/build/gyp/pylib/gyp/__init__.py is causing the problem specifically, stack shown below:

> /space/upgrade/v8/build/gyp/pylib/gyp/__init__.py(132)Load()

-> result = gyp.input.Load(build_files, default_variables, includes[:],

(Pdb) d

*** Newest frame

(Pdb) u

> /space/upgrade/v8/build/gyp/pylib/gyp/__init__.py(520)gyp_main()

-> options.duplicate_basename_check)

(Pdb) u

> /space/upgrade/v8/build/gyp/pylib/gyp/__init__.py(544)main()

-> return gyp_main(args)

(Pdb) u

> /space/upgrade/v8/build/gyp/pylib/gyp/__init__.py(551)script_main()

-> return main(sys.argv[1:])

(Pdb) u

> /space/upgrade/v8/build/gyp/gyp_main.py(19)<module>()

-> sys.exit(gyp.script_main())

(Pdb) u

*** Oldest frame

I installed python 2.7 and make sure it is the version being used, along with the libraries. What could go wrong here? Can anyone familiar with this give me some ideas? Thank you!

Shuai

Jakob Kummerow

unread,

Nov 21, 2015, 6:15:26 AM11/21/15

to v8-users

Apparently your Python is incapable of running GYP. I have no idea why that might be happening. Can this Python installation run other Python programs?

--
--
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.

Shuai Yuan

unread,

Nov 21, 2015, 1:41:38 PM11/21/15

to v8-users

Yes, for example fetch v8 with depot_tools works.

Shuai Yuan

unread,

Nov 23, 2015, 7:36:08 PM11/23/15

to v8-users

I installed different versions of Python>2.7 and it did not work... Any brain storms? Really appreciated it!