Hello Bill,
Any updates on a possible fix here? Since WSJT used to compile and run
just fine fine on Centos, this seems like a Fortran code change that
could be simplified to be compatible with the older gcc-gfortran-4.4.7
version. If that's really not possible, there seems like there is an
alternative but might not be "allowed" in official EPEL/COPR packaging
rules. Specifically, the COPR/EPEL rules in with using SCL update
packs.. specifically for GCC:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-6/
As always, there is never a free lunch and there are some specific
pros/cons:
https://www.hogarthuk.com/?q=node/15
https://ius.io/IUSvsSCL/
Bill: Thoughts on some fortran code changes?
Richard: If the code change isn't possible, is publishing binary
packages built by SCL addons acceptable?
--David
KI6ZHD
On 07/14/2017 11:30 AM, Bill Somerville wrote:
On 14/07/2017 18:53, Richard Shaw wrote:
procedure(timer_callback), pointer :: timer => null_timer
1
Error: Pointer initialization requires a NULL() at (1)
Hi Richard and David,
this one is this gfortran bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45290
which looks like it was not fixed until after gfortran 4.6. I need to
think about this one a bit, the only fix I can immediately think of is
very messy.
The others I have a fix for but I suspect there may be similar issues
elsewhere. We are fairly committed to a C++11 C++ compiler now despite
what I said about Qt v5.2 support.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
