When I'm running ninja ninja -C <build_dir> v8_monolith I'm getting the following error:
[5/1560] ACTION //:generate_bytecode_builtins_list(//build/toolchain/linux/unbundle:default) FAILED: gen/builtins-generated/bytecodes-builtins-list.h python ../v8/v8/tools/run.py ./bytecode_builtins_list_generator gen/builtins-generated/bytecodes-builtins-list.h /bytecode_builtins_list_generator: error while loading shared libraries: libc++.so.1: cannot open shared object file: No such file or directory Return code is 127
If it's built with ./llvm/install/bin/clang --stdlib=libc++ then I expect it to link with ./llvm/install/libs/x86_64-unknwon-linux/libc++.so.1 but this is not the case.
Ben Noordhuis
unread,
May 25, 2021, 3:24:18 PM5/25/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to v8-users
You probably need to `export
LD_LIBRARY_PATH=$PWD//llvm/install/libs/x86_64-unknown-linux`
(DYLD_LIBRARY_PATH on macOS) in order for the dynamic linker to look
in the right location.
Vadim Plakhtinskiy
unread,
May 25, 2021, 5:07:53 PM5/25/21
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to v8-users
For example: if I added path for libcxx to ldconfig, it works. But I do not want to change ldconfig. I expect if I use custom_toolchain in gn args, bytecode_builtins_list_generator can use libcxx from my llvm build dir. Maybe I need to add some specific options