Build issue

[Jonathan Doster]

Ubuntu 18.04.3 LTS

x64

Hey everyone! 

So I am following this link to build v8 using the convenience workflow.

I set the path to the gm.py and my local repo looks like:

/

depot_tools/**/**

v8/**/**

I am not sure how to connect the file the subprocess.py is trying to include. Here is the stack trace when I run the command "gm x64.release" in the v8/ directory:

# gn gen out/x64.release
ERROR at //build/config/linux/pkg_config.gni:103:17: Script returned non-zero exit code.
    pkgresult = exec_script(pkg_config_script, args, "value")
                ^----------
Current dir: /home/dev/Documents/v8/depot_tools/v8/out/x64.release/
Command: python /home/dev/Documents/v8/depot_tools/v8/build/config/linux/pkg-config.py -s /home/dev/Documents/v8/depot_tools/v8/build/linux/debian_sid_amd64-sysroot -a x64 glib-2.0 gmodule-2.0 gobject-2.0 gthread-2.0
Returned 1.
stderr:


Traceback (most recent call last):
  File "/home/dev/Documents/v8/depot_tools/v8/build/config/linux/pkg-config.py", line 248, in <module>
    sys.exit(main())
  File "/home/dev/Documents/v8/depot_tools/v8/build/config/linux/pkg-config.py", line 143, in main
    prefix = GetPkgConfigPrefixToStrip(options, args)
  File "/home/dev/Documents/v8/depot_tools/v8/build/config/linux/pkg-config.py", line 82, in GetPkgConfigPrefixToStrip
    "--variable=prefix"] + args, env=os.environ)
  File "/usr/lib/python2.7/subprocess.py", line 216, in check_output
    process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 394, in __init__
    errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1047, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory


See //build/config/linux/BUILD.gn:89:3: whence it was called.
  pkg_config("glib") {
  ^-------------------
See //build/config/compiler/BUILD.gn:244:18: which caused the file to be included.
    configs += [ "//build/config/linux:compiler" ]

[Jakob Kummerow]

Not sure what might be causing this. One thing that pops out is that .../v8/depot_tools/v8/... is a weird path. The v8 checkout is not supposed to be a subdirectory of depot_tools. I don't know whether this actually hurts though.

Maybe the issue is that pkg_config can't find glib? Try "sudo apt-get install build-essential libglib2.0-dev".

[Jonathan Doster]

Jakob,

Thank you so much for your immediate response!! I will do this when I get home and report back to you.

--
--
v8-dev mailing list
v8-...@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/CAKSzg3RMMnecsVMgx8oWOEKJFeonVX6iy_B138c4B-Vr4HEj2g%40mail.gmail.com.

--

Jonathan Doster 909.839.3432 Jbdo...@gmail.com Please disregard any spelling errors, this message was sent via mobile.

[Jonathan Doster]

Jakob,

Success! The answer was

sudo apt-get install build-essential libglib2.0-dev

As always, thank you. 

Let me know if you ever need anything

[Jakob Kummerow]

For the record / future readers: v8.dev/docs/build actually mentions the official answer:

4. This step is only needed on Linux. Install additional build dependencies:
./build/install-build-deps.sh

 

That script works on apt-get based distros, i.e. Debian/Ubuntu/Mint/etc.; for other distros you'll have to determine the respective package names yourself.

It also installs quite a bit more than V8 needs, because it's geared towards Chromium -- but it's the easiest way to make sure your system has everything it needs.

--

[Jonathan Doster]

Oops! My bad, yes I missed that step. Thank you

--

--
v8-dev mailing list
v8-...@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to v8-dev+un...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/CAKSzg3Q70NuBCd-8h6WEsF4iLfn5O1hO-MnL1_PEGROUjjRf-w%40mail.gmail.com.

[Jean-François Dagenais]

Hey guys, digging up this old issue... I am trying to understand the point of build/linux/debian_sid_amd64-sysroot if you end up doing `apt install libglib2.0-dev`.

It seems to me like your pkg-config is going to use that library from /usr/lib/... instead of debian_sid_amd64-sysroot, which makes me wonder why debian_sid_amd64-sysroot is there and mentioned in the first place. Am I missing something crucial here?