On 02/03/2016 13:02, Michael Black wrote: > Can you provide the output of "nm wsjtx.exe" too please? That should > hopefully show the problem. Sounds like a name mangling issue. You > should have something like this: Hi Mike,
although a good idea it will not help in this case as the messages are not from the system library loader. The Qt signal slot mechanism is a run time lookup of its own meta data tables and the errors are from the Qt signal handling code saying that it cannot find the slot functions. This most likely to be a mismatch in the version of the shared library that has the Qt kernel in it and the version of Qt the application was built with. The files generated by the moc tool seem to incompatible with the calls being made to them by the Qt kernel. Perhaps a path issue at build time that has picked up a Qt4 moc tool rather than the Qt 5 one that should have been used. 73 Bill G4WJS. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
