Hmm, is the typeinfo something that gets generated in each library, then is meant to be resolved into a single instance at runtime using weak linking or something similar? If so, then I think those warnings might be ignored, as the last module loaded will "win" and control a single instance of that symbol.
Does anything bad happen when you run the program? If yes, then a small testcase showing the problem would be helpful. On Mon, Aug 24, 2015 at 3:58 AM, Bruce Mitchener <[email protected]> wrote: > Someone else can answer the parts about dynamic linking ... > > On Mon, Aug 24, 2015 at 5:26 PM, Dmitry Grechka <[email protected]> > wrote: > >> Could somebody advice how to "decode" the name _ZTS6tactic (e.g. how the >> name is formed)? What is compiled to it? >> > > That's C++ name mangling. You can use "c++filt" on a Unix box to demangle > it typically (sometimes you have to put an extra _ in front): > > $ c++filt __ZTS6tactic > typeinfo name for tactic > > So you can see that in this case, it is the typeinfo for your tactic class. > > - Bruce > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
