[v8-users] Re: Static library depends on self-built libc++, no longer compatible with libstdc++?
I don't have an answer for your specific question, but I highly recommend dynamically linking to V8. if nothing else it speeds up link times by quite a bit, from what I remember from a while ago when I switched over. On Friday, September 8, 2017 at 8:52:17 AM UTC-7, Kenton Varda wrote: > > Hi v8-users, > > My C++ server app statically links against v8. > > My build broke when updating from 6.0 to 6.1. It looks like V8 now pulls > in and builds libc++ as part of its own build. However, no libc++.a is > generated, nor are the libc++ objects included in the regular static > library outputs. So, naturally, I get link errors. > > I tried manually linking in the libc++ object files, but this reveals a > second problem: I also link against the system-installed libprotobuf, which > uses libstdc++. As libprotobuf uses std types in its ABI (my bad), this > means my app needs to be linked against libstdc++ as well. I can't > statically link against both C++ libs as this produces duplicate symbols. > > Is there a recommended approach to take here? Can I tell v8 to use > libstdc++? Or do I need to vendor in libprotobuf so that I can build > everything against libc++ from here on out? > > Thanks, > -Kenton > -- -- 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.
Re: [v8-users] Re: Building v8 5.9 on Centos 6
GCC 4.8.4 definitely works, so 4.8.2 is probably fine too. On Fri, Sep 8, 2017 at 2:57 AM, Chris Hillerywrote: > Thanks for the reply, Jakob. As I mentioned, I do have gcc 4.8.2 already > running on Centos 6, which should be new enough to build v8 5.9, correct? > > -- > -- > 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.
Re: [v8-users] Intent to Ship: Intl.PluralRules
What's the stability state of the spec? I don't see it on https://github.com/tc39/proposals On Fri, Sep 8, 2017 at 9:41 AM, Josh Wolfewrote: > # Contact emails > > jwo...@igalia.com > little...@chromium.org > > # Spec > > https://rawgit.com/caridy/intl-plural-rules-spec/master/index.html > > # Summary > > Intl.PluralRules is a new API which exposes language-dependent data on > pluralization forms of numbers. Given a locale and a number, > Intl.PluralRules outputs a category, which can then be used for > selection of the pluralization form of surrounding text. > > # Motivation > > In English, 101st ends with "st" while 111th ends with "th". The algorithm > for > determining the proper ordinal suffix is non-trivial and locale specific. A > proper international solution is implemented in ICU, and Intl.PluralRules > exposes this solution to JavaScript developers. > > # Interoperability risk > > * Firefox: In development > * Edge: No public signals > * Safari: No public signals > * Web developers: Positive > > # Compatibility risk > > Low compatibility risk, as this feature is exposed through a new field > `Intl.PluralRules`. > > # Ongoing technical constraints > > None > > # Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)? > > Yes > > # OWP launch tracking bug > > https://bugs.chromium.org/p/v8/issues/detail?id=5601 > > # Link to entry on the Chrome Platform Status > > https://www.chromestatus.com/features/5653874773852160 > > -- > -- > 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.
[v8-users] Intent to Ship: Intl.PluralRules
# Contact emails jwo...@igalia.com little...@chromium.org # Spec https://rawgit.com/caridy/intl-plural-rules-spec/master/index.html # Summary Intl.PluralRules is a new API which exposes language-dependent data on pluralization forms of numbers. Given a locale and a number, Intl.PluralRules outputs a category, which can then be used for selection of the pluralization form of surrounding text. # Motivation In English, 101st ends with "st" while 111th ends with "th". The algorithm for determining the proper ordinal suffix is non-trivial and locale specific. A proper international solution is implemented in ICU, and Intl.PluralRules exposes this solution to JavaScript developers. # Interoperability risk * Firefox: In development * Edge: No public signals * Safari: No public signals * Web developers: Positive # Compatibility risk Low compatibility risk, as this feature is exposed through a new field `Intl.PluralRules`. # Ongoing technical constraints None # Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes # OWP launch tracking bug https://bugs.chromium.org/p/v8/issues/detail?id=5601 # Link to entry on the Chrome Platform Status https://www.chromestatus.com/features/5653874773852160 -- -- 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] Static library depends on self-built libc++, no longer compatible with libstdc++?
Hi v8-users, My C++ server app statically links against v8. My build broke when updating from 6.0 to 6.1. It looks like V8 now pulls in and builds libc++ as part of its own build. However, no libc++.a is generated, nor are the libc++ objects included in the regular static library outputs. So, naturally, I get link errors. I tried manually linking in the libc++ object files, but this reveals a second problem: I also link against the system-installed libprotobuf, which uses libstdc++. As libprotobuf uses std types in its ABI (my bad), this means my app needs to be linked against libstdc++ as well. I can't statically link against both C++ libs as this produces duplicate symbols. Is there a recommended approach to take here? Can I tell v8 to use libstdc++? Or do I need to vendor in libprotobuf so that I can build everything against libc++ from here on out? Thanks, -Kenton -- -- 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.
Re: [v8-users] Re: Building v8 5.9 on Centos 6
Thanks for the reply, Jakob. As I mentioned, I do have gcc 4.8.2 already running on Centos 6, which should be new enough to build v8 5.9, correct? -- -- 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.