Re: [wsjt-devel] Errors running on arm (RPi2)
On 03/03/16 12:16, Bill Somerville wrote: > Hi Barry, > > you can make your own upstream tarball using the superbuild script, this > can be built from any tag or branch HEAD. Ok thanks - reading the CMakeText.txt I found that it defaults to HEAD if no tag is specified. > Although an arbitrary revision > snapshot is not currently supported I would have thought that using a > tag for stable released version or a branch HEAD for the latest & > greatest should cover most requirements. Yes that is probably adequate - I only moved to testing with 1.7 when I hit the errors on arm, plus of course kvasd is not available for arm AFAIK. I am thinking that this is most probably a qt5-5.6 issue, as I am almost sure it ran once on arm when I first built it locally a few months ago. That would have been when we were still at 5.5.x. > If that is not so I could > enhance the superbuild CMake script to build an upstream tarball from an > svn revision. Could be really useful for bisecting when chasing bugs. Another option is to use the patching capability of the > superbuild script, both for WSJT-X and Hamlib it can automatically apply > a patch set bundled in the upstream tarball it generates. Good to know, may I ask that you add 'asciidoc' to the search names for 'asciidoctor' to avoid us having to patch this? I was mistaken about the Qt5 update - it was a plasma5 update to 5.6 for KDE - read it too fast ;) - so we will need to wait to test until Qt5-5.6 is fully released. Cheers, Barry G4MKT > > 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 > -- 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
Re: [wsjt-devel] Errors running on arm (RPi2) OK 4 me (BPi)
Fixed.
WSJT 10.0 r6470
Fedora 23 on Bnanan Pi
Reinstall Pillow:
/usr/bin/pip3.4 install -I pillow
Using cached Pillow-3.1.1.tar.gz
Installing collected packages: pillow
Running setup.py install for pillow
Successfully installed pillow-3.0.0
Hi,
Fedora 23 on Banana Pi all is not OK yet...
WSJT Version 10.0 r6470 , by K1JT
Revision date ...: 2016-02-06 11:42:05 +1100 (Sat, 06 Feb 2016)
Run date : Thu Mar 3 12:02:09 2016 UTC
Traceback (most recent call last):
File "/usr/lib/python3.4/site-packages/PIL/ImageTk.py", line 176, in paste
tk.call("PyImagingPhoto", self.__photo, block.id)
_tkinter.TclError: invalid command name "PyImagingPhoto"
SNV code downloaded today, Ver: 6505
Alan VK2ZIW
On Thu, 3 Mar 2016 10:40:29 +, Barry Jackson wrote
> On 03/03/16 01:13, Bill Somerville wrote:
> > On 02/03/2016 20:54, Barry Jackson wrote:
> >> On a new clean build of rev6503 I do have the same as above with one
> >> exception, I don't have moc_OmniRigTransceiver.cpp but maybe that is
> >> from a different build.
> > Hi Barry,
> >
> > the file moc_OmniRigTransceiver.cpp is only generated on a Windows build
> > so you definitely had files in your build tree that generated during a
> > Windows build. That is not good, a build tree must be exclusively used
> > on the platform it is configured for.
> >
> > The clean build that you supplied log of looks good to me. The only
> > query I have is that it reports that the source tree has local
> > modifications so it is not exactly r6503. It would be interesting to see
> > what those local edits are. You can show that by changing your CWD to
> > the root of the source tree and typing:
> >
> > svn diff
> >
> > 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
> >
>
> I suspect that the only modification will be the patch that we apply
> right at the start of the build:
>
> #---
>
> diff -ur wsjtx-1.7.0.6180_o/doc/CMakeLists.txt
> wsjtx-1.7.0.6180/doc/CMakeLists.txt
> --- wsjtx-1.7.0.6180_o/doc/CMakeLists.txt 2015-11-25 19:56:41.0
> +
>
> +++ wsjtx-1.7.0.6180/doc/CMakeLists.txt 2015-11-25
> 21:01:18.214793183 + @@ -90,9 +90,9 @@
>
> )
>
> -find_program (ASCIIDOCTOR_EXECUTABLE NAMES asciidoctor)
> +find_program (ASCIIDOCTOR_EXECUTABLE NAMES asciidoc)
> if (NOT ASCIIDOCTOR_EXECUTABLE)
> - message (FATAL_ERROR "asciidoctor is required to build the documentation
> + message (FATAL_ERROR "asciidoc is required to build the documentation
>
> Building the documenation may optionally be turned off by setting
> the CMake option WSJT_GENERATE_DOCS to OFF.")
>
> #---
>
> I will double check though.
>
> Barry
> G4MKT
>
> --
> 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
Alan
Evil flourishes when good men do nothing.
Consider Jesus.
---
Alan Beard Unix Support Technician from 1984 to today
70 Wedmore Rd. Sun Solaris, AIX, HP/UX, Linux, SCO, MIPS
Emu Heights N.S.W. 2750 Routers, terminal servers, printers, terminals etc..
+61 2 47353013 (h) Support Programming, shell scripting, "C", assembler
0414 353013 (mobile) After uni, electronics tech
--
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
Re: [wsjt-devel] Errors running on arm (RPi2)
Hi,
Fedora 23 on Banana Pi all is not OK yet...
WSJT Version 10.0 r6470 , by K1JT
Revision date ...: 2016-02-06 11:42:05 +1100 (Sat, 06 Feb 2016)
Run date : Thu Mar 3 12:02:09 2016 UTC
Traceback (most recent call last):
File "/usr/lib/python3.4/site-packages/PIL/ImageTk.py", line 176, in paste
tk.call("PyImagingPhoto", self.__photo, block.id)
_tkinter.TclError: invalid command name "PyImagingPhoto"
SNV code downloaded today, Ver: 6505
Alan VK2ZIW
On Thu, 3 Mar 2016 10:40:29 +, Barry Jackson wrote
> On 03/03/16 01:13, Bill Somerville wrote:
> > On 02/03/2016 20:54, Barry Jackson wrote:
> >> On a new clean build of rev6503 I do have the same as above with one
> >> exception, I don't have moc_OmniRigTransceiver.cpp but maybe that is
> >> from a different build.
> > Hi Barry,
> >
> > the file moc_OmniRigTransceiver.cpp is only generated on a Windows build
> > so you definitely had files in your build tree that generated during a
> > Windows build. That is not good, a build tree must be exclusively used
> > on the platform it is configured for.
> >
> > The clean build that you supplied log of looks good to me. The only
> > query I have is that it reports that the source tree has local
> > modifications so it is not exactly r6503. It would be interesting to see
> > what those local edits are. You can show that by changing your CWD to
> > the root of the source tree and typing:
> >
> > svn diff
> >
> > 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
> >
>
> I suspect that the only modification will be the patch that we apply
> right at the start of the build:
>
> #---
>
> diff -ur wsjtx-1.7.0.6180_o/doc/CMakeLists.txt
> wsjtx-1.7.0.6180/doc/CMakeLists.txt
> --- wsjtx-1.7.0.6180_o/doc/CMakeLists.txt 2015-11-25 19:56:41.0
> +
>
> +++ wsjtx-1.7.0.6180/doc/CMakeLists.txt 2015-11-25
> 21:01:18.214793183 + @@ -90,9 +90,9 @@
>
> )
>
> -find_program (ASCIIDOCTOR_EXECUTABLE NAMES asciidoctor)
> +find_program (ASCIIDOCTOR_EXECUTABLE NAMES asciidoc)
> if (NOT ASCIIDOCTOR_EXECUTABLE)
> - message (FATAL_ERROR "asciidoctor is required to build the documentation
> + message (FATAL_ERROR "asciidoc is required to build the documentation
>
> Building the documenation may optionally be turned off by setting
> the CMake option WSJT_GENERATE_DOCS to OFF.")
>
> #---
>
> I will double check though.
>
> Barry
> G4MKT
>
> --
> 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
Alan
Evil flourishes when good men do nothing.
Consider Jesus.
---
Alan Beard Unix Support Technician from 1984 to today
70 Wedmore Rd. Sun Solaris, AIX, HP/UX, Linux, SCO, MIPS
Emu Heights N.S.W. 2750 Routers, terminal servers, printers, terminals etc..
+61 2 47353013 (h) Support Programming, shell scripting, "C", assembler
0414 353013 (mobile) After uni, electronics tech
--
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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 03/03/2016 12:08, Barry Jackson wrote: >> Once this issue is resolved there is another you need to address. For >> >correct functionality you need to use a build of Hamlib from my fork or >> >from the Hamlib 3.1 version (not yet released) as a minimum. This is not >> >the cause of the errors you are seeing. > Yes this is already catered for in our 1.6 build in the repos using the > superbuild script to create our tarball but IIRC this does not work for > snapshots. > Hi Barry, you can make your own upstream tarball using the superbuild script, this can be built from any tag or branch HEAD. Although an arbitrary revision snapshot is not currently supported I would have thought that using a tag for stable released version or a branch HEAD for the latest & greatest should cover most requirements. If that is not so I could enhance the superbuild CMake script to build an upstream tarball from an svn revision. Another option is to use the patching capability of the superbuild script, both for WSJT-X and Hamlib it can automatically apply a patch set bundled in the upstream tarball it generates. 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 03/03/16 11:42, Bill Somerville wrote: > On 03/03/2016 10:43, Barry Jackson wrote: >> I forgot to mention that the the top list of files was from Michael not >> me - no Windows here! > Hi Barry, > > ok I had missed that, sorry. > > One thing worth noting is that Qt 5.6 is still in beta so it may well > not have been tested on ARM very thoroughly. Is there a repo with 5.5.1 > or 5.4 available? > No, Mageia has only recently started building for arm and the current bootstrap repo is building in parallel with the current Mageia development branch. This is getting close to release, so is quite stable. I am using it (on x86_64) now. There is a Qt5 update in progress just now, so when that is complete I will rebuild again and test. > Once this issue is resolved there is another you need to address. For > correct functionality you need to use a build of Hamlib from my fork or > from the Hamlib 3.1 version (not yet released) as a minimum. This is not > the cause of the errors you are seeing. Yes this is already catered for in our 1.6 build in the repos using the superbuild script to create our tarball but IIRC this does not work for snapshots. > 73 > Bill > G4WJS. > Thanks for your help, Barry G4MKT -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 03/03/2016 10:43, Barry Jackson wrote: > I forgot to mention that the the top list of files was from Michael not > me - no Windows here! Hi Barry, ok I had missed that, sorry. One thing worth noting is that Qt 5.6 is still in beta so it may well not have been tested on ARM very thoroughly. Is there a repo with 5.5.1 or 5.4 available? Once this issue is resolved there is another you need to address. For correct functionality you need to use a build of Hamlib from my fork or from the Hamlib 3.1 version (not yet released) as a minimum. This is not the cause of the errors you are seeing. 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 03/03/16 01:13, Bill Somerville wrote: > On 02/03/2016 20:54, Barry Jackson wrote: >> On a new clean build of rev6503 I do have the same as above with one >> exception, I don't have moc_OmniRigTransceiver.cpp but maybe that is >> from a different build. > Hi Barry, > > the file moc_OmniRigTransceiver.cpp is only generated on a Windows build > so you definitely had files in your build tree that generated during a > Windows build. That is not good, a build tree must be exclusively used > on the platform it is configured for. Bill, I forgot to mention that the the top list of files was from Michael not me - no Windows here! Barry G4MKT -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 03/03/16 01:13, Bill Somerville wrote: > On 02/03/2016 20:54, Barry Jackson wrote: >> On a new clean build of rev6503 I do have the same as above with one >> exception, I don't have moc_OmniRigTransceiver.cpp but maybe that is >> from a different build. > Hi Barry, > > the file moc_OmniRigTransceiver.cpp is only generated on a Windows build > so you definitely had files in your build tree that generated during a > Windows build. That is not good, a build tree must be exclusively used > on the platform it is configured for. > > The clean build that you supplied log of looks good to me. The only > query I have is that it reports that the source tree has local > modifications so it is not exactly r6503. It would be interesting to see > what those local edits are. You can show that by changing your CWD to > the root of the source tree and typing: > > svn diff > > 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 > I suspect that the only modification will be the patch that we apply right at the start of the build: #--- diff -ur wsjtx-1.7.0.6180_o/doc/CMakeLists.txt wsjtx-1.7.0.6180/doc/CMakeLists.txt --- wsjtx-1.7.0.6180_o/doc/CMakeLists.txt 2015-11-25 19:56:41.0 + +++ wsjtx-1.7.0.6180/doc/CMakeLists.txt 2015-11-25 21:01:18.214793183 + @@ -90,9 +90,9 @@ ) -find_program (ASCIIDOCTOR_EXECUTABLE NAMES asciidoctor) +find_program (ASCIIDOCTOR_EXECUTABLE NAMES asciidoc) if (NOT ASCIIDOCTOR_EXECUTABLE) - message (FATAL_ERROR "asciidoctor is required to build the documentation + message (FATAL_ERROR "asciidoc is required to build the documentation Building the documenation may optionally be turned off by setting the CMake option WSJT_GENERATE_DOCS to OFF.") #--- I will double check though. Barry G4MKT -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 02/03/2016 20:54, Barry Jackson wrote: > On a new clean build of rev6503 I do have the same as above with one > exception, I don't have moc_OmniRigTransceiver.cpp but maybe that is > from a different build. Hi Barry, the file moc_OmniRigTransceiver.cpp is only generated on a Windows build so you definitely had files in your build tree that generated during a Windows build. That is not good, a build tree must be exclusively used on the platform it is configured for. The clean build that you supplied log of looks good to me. The only query I have is that it reports that the source tree has local modifications so it is not exactly r6503. It would be interesting to see what those local edits are. You can show that by changing your CWD to the root of the source tree and typing: svn diff 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 02/03/16 16:13, Michael Black wrote: > Yeah...you're missing the moc for Configuration and a bunch of others. > Are you out of disk space perhaps? > RRR > Mike W9MDB > > moc_about.cpp > moc_astro.cpp > moc_BWFFile.cpp > moc_Configuration.cpp > moc_Detector.cpp > moc_Directory.cpp > moc_displaytext.cpp > moc_DXLabSuiteCommanderTransceiver.cpp > moc_echograph.cpp > moc_echoplot.cpp > moc_fastgraph.cpp > moc_fastplot.cpp > moc_FrequencyLineEdit.cpp > moc_FrequencyList.cpp > moc_HamlibTransceiver.cpp > moc_LettersSpinBox.cpp > moc_LiveFrequencyValidator.cpp > moc_logqso.cpp > moc_mainwindow.cpp > moc_messageaveraging.cpp > moc_MessageClient.cpp > moc_MessageServer.cpp > moc_meterwidget.cpp > moc_Modes.cpp > moc_Modulator.cpp > moc_OmniRigTransceiver.cpp > moc_plotter.cpp > moc_PollingTransceiver.cpp > moc_psk_reporter.cpp > moc_RemoteFile.cpp > moc_SampleDownloader.cpp > moc_signalmeter.cpp > moc_soundin.cpp > moc_soundout.cpp > moc_Transceiver.cpp > moc_TransceiverBase.cpp > moc_TransceiverFactory.cpp > moc_widegraph.cpp > moc_WSPRBandHopping.cpp > moc_wsprnet.cpp On a new clean build of rev6503 I do have the same as above with one exception, I don't have moc_OmniRigTransceiver.cpp but maybe that is from a different build. Still get the same 'No matching signal' errors on running it and greps for the following fail: [baz@mageia-pi build]$ for f in moc*; do cat $f |grep "on_font_button" ; done [baz@mageia-pi build]$ for f in moc*; do cat $f |grep "connectSlotsByName" ; done [baz@mageia-pi build]$ Here is the full build log in case anything jumps out at you: https://paste.kde.org/pqs0fwip8 And out of interest I searched the build directory: https://goo.gl/qrDVmr It may show something. Barry G4MKT > -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 02/03/16 16:10, Barry Jackson wrote: > These are the files: > moc_Directory.cpp > moc_DXLabSuiteCommanderTransceiver.cpp > moc_FrequencyLineEdit.cpp > moc_FrequencyList.cpp > moc_HamlibTransceiver.cpp > moc_LettersSpinBox.cpp > moc_LiveFrequencyValidator.cpp > moc_MessageClient.cpp > moc_MessageServer.cpp > moc_Modes.cpp > moc_PollingTransceiver.cpp > moc_RemoteFile.cpp > moc_SampleDownloader.cpp > moc_TransceiverBase.cpp > moc_Transceiver.cpp > moc_TransceiverFactory.cpp > > Maybe something is missing? > > Barry > G4MKT > Ah! - no this is a red herring. I just realized that I attempted another build after updating the Pi2 earlier which failed due to a broken dep on the mirror, the old build dir got overwritten, with the partial build, hence the missing files. I will check everything again once we have things sorted. Thanks for your help Barry G4MKT -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
These are the files: moc_Directory.cpp moc_DXLabSuiteCommanderTransceiver.cpp moc_FrequencyLineEdit.cpp moc_FrequencyList.cpp moc_HamlibTransceiver.cpp moc_LettersSpinBox.cpp moc_LiveFrequencyValidator.cpp moc_MessageClient.cpp moc_MessageServer.cpp moc_Modes.cpp moc_PollingTransceiver.cpp moc_RemoteFile.cpp moc_SampleDownloader.cpp moc_TransceiverBase.cpp moc_Transceiver.cpp moc_TransceiverFactory.cpp Maybe something is missing? Barry G4MKT -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 02/03/16 15:49, Michael Black wrote: > No grep for the function name of that missing signal in the moc for > Configuration. > I just realized and did: [baz@mageia-pi build]$ for f in moc*; do cat $f |grep "on_font_button" ; done [baz@mageia-pi build]$ for f in moc*; do cat $f |grep "connectSlots" ; done [baz@mageia-pi build]$ Neither found anything. I think that was what you meant. Barry -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
No grep for the function name of that missing signal in the moc for Configuration. RRR Mike W9MDB On Wed, Mar 2, 2016 at 9:37 AM, Barry Jackson wrote: > On 02/03/16 15:22, Bill Somerville wrote: >> On 02/03/2016 14:49, Barry Jackson wrote: >>> Where would I find "the moc file"? >> Hi Barry, >> >> the generated files are at the root of the build tree with names like >> moc_mainwindow.cpp, they contain the meta-data for the Qt objects and >> the stubs that implement the signals and slots. The only bit that really >> matters is the header comment that should look something like: >> >> / >> ** Meta object code from reading C++ file 'mainwindow.h' >> ** >> ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.5.1) >> ** >> ** WARNING! All changes made in this file will be lost! >> */ >> >> Note the version of moc is shown. >> >> 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 >> > Thanks Bill, > [baz@mageia-pi build]$ for f in moc*; do cat $f |grep "Created by" ; done > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) > > So that looks OK > > Barry > > -- > 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 -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 02/03/16 15:22, Bill Somerville wrote: > On 02/03/2016 14:49, Barry Jackson wrote: >> Where would I find "the moc file"? > Hi Barry, > > the generated files are at the root of the build tree with names like > moc_mainwindow.cpp, they contain the meta-data for the Qt objects and > the stubs that implement the signals and slots. The only bit that really > matters is the header comment that should look something like: > > / > ** Meta object code from reading C++ file 'mainwindow.h' > ** > ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.5.1) > ** > ** WARNING! All changes made in this file will be lost! > */ > > Note the version of moc is shown. > > 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 > Thanks Bill, [baz@mageia-pi build]$ for f in moc*; do cat $f |grep "Created by" ; done ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.6.0) So that looks OK Barry -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 02/03/2016 14:49, Barry Jackson wrote: > Where would I find "the moc file"? Hi Barry, the generated files are at the root of the build tree with names like moc_mainwindow.cpp, they contain the meta-data for the Qt objects and the stubs that implement the signals and slots. The only bit that really matters is the header comment that should look something like: / ** Meta object code from reading C++ file 'mainwindow.h' ** ** Created by: The Qt Meta Object Compiler version 67 (Qt 5.5.1) ** ** WARNING! All changes made in this file will be lost! */ Note the version of moc is shown. 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 02/03/16 14:07, Michael Black wrote: > The nm output at least confirms some version of the function is in the > executable. > Your idea sounds like a really good possibility. The qt4 moc was available in the local build on the Pi2, but it would not have been in the Mageia BS build as this is done in a clean base-system chroot with only BuildRequires installed on top. I have removed the qt4 devel package containing the qt4 moc from the Pi2 and am rebuilding again. > > perhaps grepping for the function in the moc file might be illuminating? Where would I find "the moc file"? Barry -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
The nm output at least confirms some version of the function is in the executable. Your idea sounds like a really good possibility. perhaps grepping for the function in the moc file might be illuminating? RRR Mike W9MDB On Wed, Mar 2, 2016 at 7:57 AM, Bill Somerville wrote: > 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 -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 02/03/16 13:02, Michael Black wrote: > nm wsjtx.exe I guess you were thinking Win ;) https://paste.kde.org/p6ccgtyto -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
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: 004d9b60 T __ZN13Configuration4impl27on_font_push_button_clickedEv C++ does horrid name mangling which can make tracing link problems like this a PITA. Fortunately there should be only one function with this name in here. The hex number in ldd is the load address of the library..it may vary from run to run. I think you should be able to see the mapping in "cat /proc//maps" -- it's not very useful or relevant since wsjtx is statically linked with its own functions. RRR Mike W9MDB On Wed, Mar 2, 2016 at 6:38 AM, Barry Jackson wrote: > On 02/03/16 00:56, Bill Somerville wrote: >> On 02/03/2016 00:26, Barry Jackson wrote: >>> I am attempting to run 1.7 (or 1.6) on a RPi2. >>> There is no problem with the package build either on the Mageia build >>> system (1.6) or locally on the Pi2 (1.7), however attempting to run >>> either, the errors are the same: >>> >>> [baz@mageia-pi ~]$ wsjtx >>> QMetaObject::connectSlotsByName: No matching signal for >>> on_font_push_button_clicked() >> Hi Barry, >> >> I've not seen errors like that before. It looks like there may be a >> problem with the build. Did you attempt to build in the source >> directory, that is not supported. >> >> Can you post your CMakeCache.txt file somewhere so I can check it, it is >> located in the root directory of your build tree. >> >> Another possibility is some sort of version mismatch, maybe built with >> one version of Qt and run with shared libraries from another. A listing >> of the output of: >> >> ldd `which wsjtx` >> >> and to compare: >> >> ldd /wsjtx >> >> 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 >> > > Hi Bill, > The build is 'out of tree' in both cases. > The Version 1.6 build was done on the Mageia build system in a chroot > whereas the 1.7 was done locally on a RPi2 using the same rpm spec file, > except that the local RPi one was non-parallel. > > The builds for x86_64 done either on a local machine, in a chroot here > or on the Mageia BS all work fine and use the same spec file with the > same dependencies. > I have checked that all the 'Requires' are installed on the Pi, however > rpm deals with requires and rarely fails to get them right. > > Here is the CMakeCache.txt: https://paste.kde.org/pfpyqepdt > > The outputs of > [baz@mageia-pi build]$ ldd ./wsjtx > and > [baz@mageia-pi build]$ ldd $(which wsjtx) > > are merged together and sorted here: https://paste.kde.org/pzqwyhpji > I am hot sure what the hex #s in brackets are? > > Cheers, > Barry > G4MKT > > > -- > 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 -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 02/03/16 00:56, Bill Somerville wrote: > On 02/03/2016 00:26, Barry Jackson wrote: >> I am attempting to run 1.7 (or 1.6) on a RPi2. >> There is no problem with the package build either on the Mageia build >> system (1.6) or locally on the Pi2 (1.7), however attempting to run >> either, the errors are the same: >> >> [baz@mageia-pi ~]$ wsjtx >> QMetaObject::connectSlotsByName: No matching signal for >> on_font_push_button_clicked() > Hi Barry, > > I've not seen errors like that before. It looks like there may be a > problem with the build. Did you attempt to build in the source > directory, that is not supported. > > Can you post your CMakeCache.txt file somewhere so I can check it, it is > located in the root directory of your build tree. > > Another possibility is some sort of version mismatch, maybe built with > one version of Qt and run with shared libraries from another. A listing > of the output of: > > ldd `which wsjtx` > > and to compare: > > ldd /wsjtx > > 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 > Hi Bill, The build is 'out of tree' in both cases. The Version 1.6 build was done on the Mageia build system in a chroot whereas the 1.7 was done locally on a RPi2 using the same rpm spec file, except that the local RPi one was non-parallel. The builds for x86_64 done either on a local machine, in a chroot here or on the Mageia BS all work fine and use the same spec file with the same dependencies. I have checked that all the 'Requires' are installed on the Pi, however rpm deals with requires and rarely fails to get them right. Here is the CMakeCache.txt: https://paste.kde.org/pfpyqepdt The outputs of [baz@mageia-pi build]$ ldd ./wsjtx and [baz@mageia-pi build]$ ldd $(which wsjtx) are merged together and sorted here: https://paste.kde.org/pzqwyhpji I am hot sure what the hex #s in brackets are? Cheers, Barry G4MKT -- 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
Re: [wsjt-devel] Errors running on arm (RPi2)
On 02/03/2016 00:26, Barry Jackson wrote: > I am attempting to run 1.7 (or 1.6) on a RPi2. > There is no problem with the package build either on the Mageia build > system (1.6) or locally on the Pi2 (1.7), however attempting to run > either, the errors are the same: > > [baz@mageia-pi ~]$ wsjtx > QMetaObject::connectSlotsByName: No matching signal for > on_font_push_button_clicked() Hi Barry, I've not seen errors like that before. It looks like there may be a problem with the build. Did you attempt to build in the source directory, that is not supported. Can you post your CMakeCache.txt file somewhere so I can check it, it is located in the root directory of your build tree. Another possibility is some sort of version mismatch, maybe built with one version of Qt and run with shared libraries from another. A listing of the output of: ldd `which wsjtx` and to compare: ldd /wsjtx 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
[wsjt-devel] Errors running on arm (RPi2)
Hi, I am attempting to run 1.7 (or 1.6) on a RPi2. There is no problem with the package build either on the Mageia build system (1.6) or locally on the Pi2 (1.7), however attempting to run either, the errors are the same: [baz@mageia-pi ~]$ wsjtx QMetaObject::connectSlotsByName: No matching signal for on_font_push_button_clicked() QMetaObject::connectSlotsByName: No matching signal for on_decoded_text_font_push_button_clicked() QMetaObject::connectSlotsByName: No matching signal for on_PTT_port_combo_box_activated(int) QMetaObject::connectSlotsByName: No matching signal for on_CAT_port_combo_box_activated(int) QMetaObject::connectSlotsByName: No matching signal for on_CAT_serial_baud_combo_box_currentIndexChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_CAT_data_bits_button_group_buttonClicked(int) QMetaObject::connectSlotsByName: No matching signal for on_CAT_stop_bits_button_group_buttonClicked(int) QMetaObject::connectSlotsByName: No matching signal for on_CAT_handshake_button_group_buttonClicked(int) QMetaObject::connectSlotsByName: No matching signal for on_CAT_poll_interval_spin_box_valueChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_split_mode_button_group_buttonClicked(int) QMetaObject::connectSlotsByName: No matching signal for on_test_CAT_push_button_clicked() QMetaObject::connectSlotsByName: No matching signal for on_test_PTT_push_button_clicked(bool) QMetaObject::connectSlotsByName: No matching signal for on_force_DTR_combo_box_currentIndexChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_force_RTS_combo_box_currentIndexChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_rig_combo_box_currentIndexChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_sound_input_combo_box_currentTextChanged(QString) QMetaObject::connectSlotsByName: No matching signal for on_sound_output_combo_box_currentTextChanged(QString) QMetaObject::connectSlotsByName: No matching signal for on_add_macro_push_button_clicked(bool) QMetaObject::connectSlotsByName: No matching signal for on_delete_macro_push_button_clicked(bool) QMetaObject::connectSlotsByName: No matching signal for on_PTT_method_button_group_buttonClicked(int) QMetaObject::connectSlotsByName: No matching signal for on_callsign_line_edit_editingFinished() QMetaObject::connectSlotsByName: No matching signal for on_grid_line_edit_editingFinished() QMetaObject::connectSlotsByName: No matching signal for on_add_macro_line_edit_editingFinished() QMetaObject::connectSlotsByName: No matching signal for on_save_path_select_push_button_clicked(bool) QMetaObject::connectSlotsByName: No matching signal for on_azel_path_select_push_button_clicked(bool) QMetaObject::connectSlotsByName: No matching signal for on_reset_frequencies_push_button_clicked(bool) QMetaObject::connectSlotsByName: No matching signal for on_pbCQmsg_clicked() QMetaObject::connectSlotsByName: No matching signal for on_pbMyCall_clicked() QMetaObject::connectSlotsByName: No matching signal for on_pbTxMsg_clicked() QMetaObject::connectSlotsByName: No matching signal for on_pbNewDXCC_clicked() QMetaObject::connectSlotsByName: No matching signal for on_pbNewCall_clicked() PulseAudioService: pa_context_connect() failed QMetaObject::connectSlotsByName: No matching signal for on_waterfallAvgSpinBox_valueChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_bppSpinBox_valueChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_spec2dComboBox_currentIndexChanged(QString) QMetaObject::connectSlotsByName: No matching signal for on_fSplitSpinBox_valueChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_fStartSpinBox_valueChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_paletteComboBox_activated(QString) QMetaObject::connectSlotsByName: No matching signal for on_cbFlatten_toggled(bool) QMetaObject::connectSlotsByName: No matching signal for on_adjust_palette_push_button_clicked(bool) QMetaObject::connectSlotsByName: No matching signal for on_gainSlider_valueChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_zeroSlider_valueChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_gain2dSlider_valueChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_zero2dSlider_valueChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_smoSpinBox_valueChanged(int) QMetaObject::connectSlotsByName: No matching signal for on_sbPercent2dPlot_valueChanged(int) The output then hangs with no GUI in evidence, and one core maxed out. Any ideas? Barry -- 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 Troubleshoo
