I tried to fix this here but concluded it's "not supported": https://codereview.chromium.org/22382003/
On Tue, Oct 18, 2016 at 9:33 AM Zac Hansen <xax...@gmail.com> wrote: > "component build" = dylib? > > It's always worked fine - but this error is new. > > Linking against the static version takes forever, so dylibs are the only > way to go. > > On Tue, Oct 18, 2016 at 12:31 AM, Jochen Eisinger <joc...@chromium.org> > wrote: > > I'm surprised that the component build with gyp on mac ever worked for > you, it never did for me :-/ > > On Tue, Oct 18, 2016 at 5:32 AM Zac Hansen <xax...@gmail.com> wrote: > > manually copying the file into /usr/local/lib works. Someone said it > might have to do with the "install_name" being /usr/local/lib, but I don't > really understand what this means. > > Also, it seems broken that copying a file into /usr/local is required for > part of the build. > > --Zac > > > On Monday, October 17, 2016 at 8:02:34 PM UTC-7, Zac Hansen wrote: > > I've been successfully building v8 for quite a while and recently pulled a > new version and am getting the following error on os x el capitan: > > make library=shared snapshot=off x64.debug -j2 > > ACTION src_v8_gyp_v8_base_target_run_mkpeephole > /Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc > > dyld: Library not loaded: /usr/local/lib/libv8_libbase.dylib > > Referenced from: /Users/xaxxon/v8/out/x64.debug/mkpeephole > > Reason: image not found > > /bin/sh: line 1: 18072 > <https://maps.google.com/?q=18072&entry=gmail&source=g> Trace/BPT trap: 5 > "/Users/xaxxon/v8/out/x64.debug/mkpeephole" > "/Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc" > > make[1]: *** > [/Users/xaxxon/v8/out/x64.debug/obj.target/v8_base/geni/bytecode-peephole-table.cc] > Error 133 > > make: *** [x64.debug] Error 2 > > I try setting my DYLD_LIBRARY_PATH to the recently build dylib but that > doesn't seem to help and it still complains about it not being in > /usr/local/lib... > > Any suggestions? > > -- > -- > 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/4aBZYlnpYiM/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. > -- -- 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.
