Re: [wsjt-devel] Build environment macOS 10.13.4

2018-05-16 Thread Megan Woods
One more thing Bill

I am using the latest cmake.

Megan



On Thu, 17 May 2018 at 6:52 am, Megan Woods 
wrote:

> Hi Bill,
>
>
> Here is the diff.
>
>
>
> Index: CMakeLists.txt
> ===
> --- CMakeLists.txt (revision 8662)
> +++ CMakeLists.txt (working copy)
> @@ -15,7 +15,7 @@
>
>  Earliest version we can support with Qt 5.8, C++11 & libc++ is 10.9.
>  Do not override this if you intend to build an official deployable
> installer.")
> -  set (CMAKE_OSX_SYSROOT
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk
> +  set (CMAKE_OSX_SYSROOT
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk
>  CACHE STRING "Mac OS X SDK to build with
>
>  Change this to the newest SDK available that you can install on your
> system (10.11 preferred).
> @@ -875,9 +875,11 @@
>  #
>
>  # Widgets finds its own dependencies.
> +find_package (Qt5Core 5 REQUIRED)
>  find_package (Qt5Widgets 5 REQUIRED)
>  find_package (Qt5Multimedia 5 REQUIRED)
>  find_package (Qt5PrintSupport 5 REQUIRED)
> +find_package (Qt5SerialPort 5 REQUIRED)
>
>  if (WIN32)
>add_definitions (-DQT_NEEDS_QTMAIN)
> @@ -1150,14 +1152,16 @@
>  # build a library for the QCustomPlot widget
>  add_library (qcp STATIC ${qcp_CXXSRCS})
>  target_include_directories (qcp PUBLIC
> $)
> -target_link_libraries (qcp Qt5::Widgets Qt5::PrintSupport)
> +target_link_libraries (qcp Qt5::Core Qt5::Widgets Qt5::PrintSupport)
>
>  # build a library of package Qt functionality
>  add_library (wsjt_qt STATIC ${wsjt_qt_CXXSRCS} ${wsjt_qt_GENUISRCS}
> ${GENAXSRCS})
> +
>  # set wsjtx_udp exports to static variants
>  target_compile_definitions (wsjt_qt PUBLIC UDP_STATIC_DEFINE)
> -target_link_libraries (wsjt_qt qcp Qt5::Widgets Qt5::Network)
> +target_link_libraries (wsjt_qt Qt5::SerialPort Qt5::Core  qcp
> Qt5::Widgets Qt5::Network)
>  target_include_directories (wsjt_qt BEFORE PRIVATE ${hamlib_INCLUDE_DIRS})
> +
>  if (WIN32)
>target_link_libraries (wsjt_qt Qt5::AxContainer Qt5::AxBase)
>  endif (WIN32)
> @@ -1343,11 +1347,18 @@
>)
>endif ()
>  endif ()
> -qt5_use_modules (wsjtx SerialPort) # not sure why the interface link
> library syntax above doesn't work
>
> +
> +target_link_libraries(wsjtx Qt5::SerialPort Qt5::Core)
> +
> +
> +#qt5_use_modules (wsjtx SerialPort) # not sure why the interface link
> library #syntax above doesn't work
> +
>  # make a library for WSJT-X UDP servers
>  # add_library (wsjtx_udp SHARED ${UDP_library_CXXSRCS})
>  add_library (wsjtx_udp-static STATIC ${UDP_library_CXXSRCS})
> +
> +
>  #target_include_directories (wsjtx_udp
>  #  INTERFACE
>  #  $
> @@ -1356,6 +1367,7 @@
>INTERFACE
>$
>)
> +
>  #set_target_properties (wsjtx_udp PROPERTIES
>  #  PUBLIC_HEADER "${UDP_library_HEADERS}"
>  #  )
> @@ -1362,9 +1374,14 @@
>  set_target_properties (wsjtx_udp-static PROPERTIES
>OUTPUT_NAME wsjtx_udp
>)
> +
>  target_compile_definitions (wsjtx_udp-static PUBLIC UDP_STATIC_DEFINE)
> +
>  #qt5_use_modules (wsjtx_udp Network)
> -qt5_use_modules (wsjtx_udp-static Network Gui)
> +#qt5_use_modules (wsjtx_udp-static Network Gui)
> +
> +target_link_libraries (wsjtx_udp-static Qt5::Core Qt5::Network Qt5::Gui)
> +
>  generate_export_header (wsjtx_udp-static BASE_NAME udp)
>
>  add_executable (udp_daemon UDPExamples/UDPDaemon.cpp
> UDPExamples/udp_daemon.rc ${WSJTX_ICON_FILE})
> @@ -1379,6 +1396,7 @@
>UDPExamples/message_aggregator.rc
>${message_aggregator_RESOURCES_RCC}
>)
> +target_link_libraries (message_aggregator Qt5::Core wsjtx_udp-static)
>  target_link_libraries (message_aggregator Qt5::Widgets wsjtx_udp-static)
>
>  if (WSJT_CREATE_WINMAIN)
>
>
> On Thu, May 17, 2018 at 6:31 AM, Bill Somerville 
> wrote:
>
>> On 16/05/2018 13:34, Megan Woods wrote:
>>
>> Just a follow up,  I got it to work with
>>
>> MacOSX SDK 10.13
>> Qt5-11-rc
>>
>> I had to update how the cmake file references the Qt modules.
>>
>> Hi Megan,
>>
>> what changes did you make to the CMake script?
>>
>> 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
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___

Re: [wsjt-devel] Build environment macOS 10.13.4

2018-05-16 Thread Megan Woods
Hi Bill,


Here is the diff.



Index: CMakeLists.txt
===
--- CMakeLists.txt (revision 8662)
+++ CMakeLists.txt (working copy)
@@ -15,7 +15,7 @@

 Earliest version we can support with Qt 5.8, C++11 & libc++ is 10.9.
 Do not override this if you intend to build an official deployable
installer.")
-  set (CMAKE_OSX_SYSROOT
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk
+  set (CMAKE_OSX_SYSROOT
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk
 CACHE STRING "Mac OS X SDK to build with

 Change this to the newest SDK available that you can install on your
system (10.11 preferred).
@@ -875,9 +875,11 @@
 #

 # Widgets finds its own dependencies.
+find_package (Qt5Core 5 REQUIRED)
 find_package (Qt5Widgets 5 REQUIRED)
 find_package (Qt5Multimedia 5 REQUIRED)
 find_package (Qt5PrintSupport 5 REQUIRED)
+find_package (Qt5SerialPort 5 REQUIRED)

 if (WIN32)
   add_definitions (-DQT_NEEDS_QTMAIN)
@@ -1150,14 +1152,16 @@
 # build a library for the QCustomPlot widget
 add_library (qcp STATIC ${qcp_CXXSRCS})
 target_include_directories (qcp PUBLIC
$)
-target_link_libraries (qcp Qt5::Widgets Qt5::PrintSupport)
+target_link_libraries (qcp Qt5::Core Qt5::Widgets Qt5::PrintSupport)

 # build a library of package Qt functionality
 add_library (wsjt_qt STATIC ${wsjt_qt_CXXSRCS} ${wsjt_qt_GENUISRCS}
${GENAXSRCS})
+
 # set wsjtx_udp exports to static variants
 target_compile_definitions (wsjt_qt PUBLIC UDP_STATIC_DEFINE)
-target_link_libraries (wsjt_qt qcp Qt5::Widgets Qt5::Network)
+target_link_libraries (wsjt_qt Qt5::SerialPort Qt5::Core  qcp Qt5::Widgets
Qt5::Network)
 target_include_directories (wsjt_qt BEFORE PRIVATE ${hamlib_INCLUDE_DIRS})
+
 if (WIN32)
   target_link_libraries (wsjt_qt Qt5::AxContainer Qt5::AxBase)
 endif (WIN32)
@@ -1343,11 +1347,18 @@
   )
   endif ()
 endif ()
-qt5_use_modules (wsjtx SerialPort) # not sure why the interface link
library syntax above doesn't work

+
+target_link_libraries(wsjtx Qt5::SerialPort Qt5::Core)
+
+
+#qt5_use_modules (wsjtx SerialPort) # not sure why the interface link
library #syntax above doesn't work
+
 # make a library for WSJT-X UDP servers
 # add_library (wsjtx_udp SHARED ${UDP_library_CXXSRCS})
 add_library (wsjtx_udp-static STATIC ${UDP_library_CXXSRCS})
+
+
 #target_include_directories (wsjtx_udp
 #  INTERFACE
 #  $
@@ -1356,6 +1367,7 @@
   INTERFACE
   $
   )
+
 #set_target_properties (wsjtx_udp PROPERTIES
 #  PUBLIC_HEADER "${UDP_library_HEADERS}"
 #  )
@@ -1362,9 +1374,14 @@
 set_target_properties (wsjtx_udp-static PROPERTIES
   OUTPUT_NAME wsjtx_udp
   )
+
 target_compile_definitions (wsjtx_udp-static PUBLIC UDP_STATIC_DEFINE)
+
 #qt5_use_modules (wsjtx_udp Network)
-qt5_use_modules (wsjtx_udp-static Network Gui)
+#qt5_use_modules (wsjtx_udp-static Network Gui)
+
+target_link_libraries (wsjtx_udp-static Qt5::Core Qt5::Network Qt5::Gui)
+
 generate_export_header (wsjtx_udp-static BASE_NAME udp)

 add_executable (udp_daemon UDPExamples/UDPDaemon.cpp
UDPExamples/udp_daemon.rc ${WSJTX_ICON_FILE})
@@ -1379,6 +1396,7 @@
   UDPExamples/message_aggregator.rc
   ${message_aggregator_RESOURCES_RCC}
   )
+target_link_libraries (message_aggregator Qt5::Core wsjtx_udp-static)
 target_link_libraries (message_aggregator Qt5::Widgets wsjtx_udp-static)

 if (WSJT_CREATE_WINMAIN)


On Thu, May 17, 2018 at 6:31 AM, Bill Somerville 
wrote:

> On 16/05/2018 13:34, Megan Woods wrote:
>
> Just a follow up,  I got it to work with
>
> MacOSX SDK 10.13
> Qt5-11-rc
>
> I had to update how the cmake file references the Qt modules.
>
> Hi Megan,
>
> what changes did you make to the CMake script?
>
> 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
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
--
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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Build environment macOS 10.13.4

2018-05-16 Thread Bill Somerville

On 16/05/2018 13:34, Megan Woods wrote:

Just a follow up,  I got it to work with

MacOSX SDK 10.13
Qt5-11-rc

I had to update how the cmake file references the Qt modules.


Hi Megan,

what changes did you make to the CMake script?

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
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Build environment macOS 10.13.4

2018-05-16 Thread Megan Woods
Just a follow up,  I got it to work with

MacOSX SDK 10.13
Qt5-11-rc

I had to update how the cmake file references the Qt modules.

Everything else apart from the hamradio api was provided by homebrew and is
more or less at the latest versions.

It makes tones and decodes when I visit a websdr site.

So far no segfaults :)

Thanks for pointing me to the correct repo.

Megan


On Wed, May 16, 2018 at 4:10 PM, Greg Beam <ki7m...@gmail.com> wrote:

> Hi Megan,
>
>
>
> I’m not sure I understand your meaning of switch to the appropriate
> branch. But in any case, WSJT (the original application) is Python based
> and resides in the Sourceforge trunk. WSJT-X resides in a branch of the
> trunk and is Qt5 based.
>
>
>
> If you are after a runnable-version for OSX, installers can be found in
> the files section on Sourceforge. Bill (G4WJS) compiles a version of OSX
> users as well (*.dmg file). I believe (though I’ve been out of the loop for
> a bit) 1.9.3.rc3 is the last prebuilt version posted for GA testing.
>
>
>
> https://sourceforge.net/projects/wsjt/files/wsjtx-1.9.0-rc3/
>
>
>
> Outside of that, I can’t really help much with setting up the build
> environment for OSX. There are instructions and Bill can no doubt get you
> sorted out with things if need be.
>
>
>
> More info for Compiling:
>
> https://sourceforge.net/p/wsjt/wsjt/HEAD/tree/branches/wsjtx/INSTALL
>
>
>
> 73’s
>
> Greg, KI7MT
>
>
>
>
>
> *From:* Megan Woods [mailto:megan.wo...@woods-gebler.com]
> *Sent:* Tuesday, May 15, 2018 11:00 PM
>
> *To:* WSJT software development <wsjt-devel@lists.sourceforge.net>
> *Subject:* Re: [wsjt-devel] Build environment macOS 10.13.4
>
>
>
> Ahh ok..
>
>
>
> I didn’t realise that it will switch to the appropriate branch and start
> over.,
>
>
>
> Megan
>
>
>
>
>
>
>
>
>
> On Wed, 16 May 2018 at 2:53 pm, Greg Beam <ki7m...@gmail.com> wrote:
>
> Hello All,
>
>
>
> First, there’s been little to know development effort on WSJT in a good
> while (2yrs or more maybe?). Another guess, but, I was probably the last
> one to update the autotools for WSJT, and can guarantee there was no
> testing done with GCC 8 
>
>
>
> WSJT-X is where the current development effort is.  Many are successfully
> building WSJT-X on OSX. Help should be plentiful in that regard. Not to
> mention, decoder performance and all the other improvements (far too many
> to list) have been made exclusively to the WSJT-X branch.
>
>
>
> 73’s
>
> Greg, KI7MT
>
>
>
> *From:* Georg Isenbürger [mailto:g...@av8r.de]
> *Sent:* Tuesday, May 15, 2018 10:23 PM
> *To:* WSJT software development <wsjt-devel@lists.sourceforge.net>
> *Subject:* Re: [wsjt-devel] Build environment macOS 10.13.4
>
>
>
> Hi Megan,
>
>
>
> I have tried multiple times to setup the OSX environment. I ran into
> similar issues and finally gave up. Hopefully in the not to far future
> there will be an installer package that builds the environment like under
> Windows…
>
>
>
> regards
>
>
>
> Georg
>
>
>
>
>
> Am 16.05.2018 um 03:44 schrieb Megan Woods <megan.wo...@woods-gebler.com>:
>
>
>
> Hi,
>
>
>
> I have been trying to build:
>
> Relative URL: ^/trunk
>
> Repository Root: https://svn.code.sf.net/p/wsjt/wsjt
>
> Repository UUID: ab8295b8-cf94-4d9e-aec4-7959e3be5d79
>
> Revision: 8658
>
>
>
> on
>
>
>
>   System Version: macOS 10.13.4 (17E202)
>
>   Kernel Version: Darwin 17.5.0
>
>
>
> I have had a succession of issues satisfying build tool chain especially
> concerning Fortran.
>
>
>
> Presently it is using:
>
>
>
> FC   = gfortran
>
> FCV= gnu95
>
>
>
> I have an issue with unresolved symbols for x86_64 which will definitely
> be an issue with my build environment.
>
>
>
> I was wondering someone who builds on OSX could give me some pointers as
> to how they set their environment up please.
>
>
>
> Megan
>
>
>
>
>
> Here is the failing output:
>
>
>
> RUN F2PY Audio.so
>
> -
>
> /usr/local/Cellar/numpy/1.14.3_1/bin/f2py3.6 -c --quiet --fcompiler=gnu95
> --f77exec=gfortran --f90exec=gfortran \
>
> --opt="-cpp -fbounds-check -O2"  -L/usr/local/lib
> -L/usr/local/Cellar/portaudio/19.6.0/lib 
> -L/usr/local/Cellar/portaudio/19.6.0/lib
> -L/usr/local/lib  -L -lfftw3f -lportaudio -lpthread -lsamplerate  libjt.a
> -m Audio f

Re: [wsjt-devel] Build environment macOS 10.13.4

2018-05-16 Thread Greg Beam
Hi Megan,

 

I’m not sure I understand your meaning of switch to the appropriate branch. But 
in any case, WSJT (the original application) is Python based and resides in the 
Sourceforge trunk. WSJT-X resides in a branch of the trunk and is Qt5 based.

 

If you are after a runnable-version for OSX, installers can be found in the 
files section on Sourceforge. Bill (G4WJS) compiles a version of OSX users as 
well (*.dmg file). I believe (though I’ve been out of the loop for a bit) 
1.9.3.rc3 is the last prebuilt version posted for GA testing.

 

https://sourceforge.net/projects/wsjt/files/wsjtx-1.9.0-rc3/

 

Outside of that, I can’t really help much with setting up the build environment 
for OSX. There are instructions and Bill can no doubt get you sorted out with 
things if need be.

 

More info for Compiling:

https://sourceforge.net/p/wsjt/wsjt/HEAD/tree/branches/wsjtx/INSTALL

 

73’s

Greg, KI7MT 

 

 

From: Megan Woods [mailto:megan.wo...@woods-gebler.com] 
Sent: Tuesday, May 15, 2018 11:00 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Build environment macOS 10.13.4

 

Ahh ok..

 

I didn’t realise that it will switch to the appropriate branch and start over.,

 

Megan 

 

 

 

 

On Wed, 16 May 2018 at 2:53 pm, Greg Beam <ki7m...@gmail.com 
<mailto:ki7m...@gmail.com> > wrote:

Hello All,

 

First, there’s been little to know development effort on WSJT in a good while 
(2yrs or more maybe?). Another guess, but, I was probably the last one to 
update the autotools for WSJT, and can guarantee there was no testing done with 
GCC 8 

 

WSJT-X is where the current development effort is.  Many are successfully 
building WSJT-X on OSX. Help should be plentiful in that regard. Not to 
mention, decoder performance and all the other improvements (far too many to 
list) have been made exclusively to the WSJT-X branch.

 

73’s

Greg, KI7MT

 

From: Georg Isenbürger [mailto:g...@av8r.de <mailto:g...@av8r.de> ] 
Sent: Tuesday, May 15, 2018 10:23 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net> >
Subject: Re: [wsjt-devel] Build environment macOS 10.13.4

 

Hi Megan, 

 

I have tried multiple times to setup the OSX environment. I ran into similar 
issues and finally gave up. Hopefully in the not to far future there will be an 
installer package that builds the environment like under Windows…

 

regards

 

Georg

 

 

Am 16.05.2018 um 03:44 schrieb Megan Woods <megan.wo...@woods-gebler.com 
<mailto:megan.wo...@woods-gebler.com> >:

 

Hi,

 

I have been trying to build:

Relative URL: ^/trunk

Repository Root: https://svn.code.sf.net/p/wsjt/wsjt

Repository UUID: ab8295b8-cf94-4d9e-aec4-7959e3be5d79

Revision: 8658

 

on 

 

  System Version: macOS 10.13.4 (17E202)

  Kernel Version: Darwin 17.5.0

 

I have had a succession of issues satisfying build tool chain especially 
concerning Fortran.

 

Presently it is using:

 

FC   = gfortran

FCV= gnu95

 

I have an issue with unresolved symbols for x86_64 which will definitely be an 
issue with my build environment.

 

I was wondering someone who builds on OSX could give me some pointers as to how 
they set their environment up please.

 

Megan

 

 

Here is the failing output:

 

RUN F2PY Audio.so

-

/usr/local/Cellar/numpy/1.14.3_1/bin/f2py3.6 -c --quiet --fcompiler=gnu95 
--f77exec=gfortran --f90exec=gfortran \

--opt="-cpp -fbounds-check -O2"  -L/usr/local/lib 
-L/usr/local/Cellar/portaudio/19.6.0/lib 
-L/usr/local/Cellar/portaudio/19.6.0/lib -L/usr/local/lib  -L -lfftw3f 
-lportaudio -lpthread -lsamplerate  libjt.a -m Audio ftn_init.f90 ftn_quit.f90 
audio_init.f90 spec.f90 getfile.f90 azdist0.f90 astro0.f90 chkt0.f90

rmbadname1: Replacing "len" with "len_bn".

{}

{}

{}

{}

{}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(in)']}

{'attrspec': ['intent(in)']}

{'attrspec': ['intent(in)']}

{'attrspec': ['intent(in)']}

{'attrspec': ['intent(in)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

{'attrspec': ['intent(out)']}

In file included from 
/var/folders/dk/dhmpt9ts4ylfqywy01_83whwgn/T/tmp0nf1vt18/src.macosx-10.13-x86_64-3.6/Audiomodule.c:16:

In file included from 
/var/folders/dk/dhmpt9ts4ylfqywy01_83whwgn/T/tmp0nf1vt18/src.macosx-10.13-x86_64-3.6/fortranobject.h:13:

In file included from 
/usr/local/lib/python3.6/site-packages/numpy/core/include/numpy/arrayobject.

Re: [wsjt-devel] Build environment macOS 10.13.4

2018-05-15 Thread Megan Woods
Ahh ok..

I didn’t realise that it will switch to the appropriate branch and start
over.,

Megan




On Wed, 16 May 2018 at 2:53 pm, Greg Beam <ki7m...@gmail.com> wrote:

> Hello All,
>
>
>
> First, there’s been little to know development effort on WSJT in a good
> while (2yrs or more maybe?). Another guess, but, I was probably the last
> one to update the autotools for WSJT, and can guarantee there was no
> testing done with GCC 8 
>
>
>
> WSJT-X is where the current development effort is.  Many are successfully
> building WSJT-X on OSX. Help should be plentiful in that regard. Not to
> mention, decoder performance and all the other improvements (far too many
> to list) have been made exclusively to the WSJT-X branch.
>
>
>
> 73’s
>
> Greg, KI7MT
>
>
>
> *From:* Georg Isenbürger [mailto:g...@av8r.de]
> *Sent:* Tuesday, May 15, 2018 10:23 PM
> *To:* WSJT software development <wsjt-devel@lists.sourceforge.net>
> *Subject:* Re: [wsjt-devel] Build environment macOS 10.13.4
>
>
>
> Hi Megan,
>
>
>
> I have tried multiple times to setup the OSX environment. I ran into
> similar issues and finally gave up. Hopefully in the not to far future
> there will be an installer package that builds the environment like under
> Windows…
>
>
>
> regards
>
>
>
> Georg
>
>
>
>
>
> Am 16.05.2018 um 03:44 schrieb Megan Woods <megan.wo...@woods-gebler.com>:
>
>
>
> Hi,
>
>
>
> I have been trying to build:
>
> Relative URL: ^/trunk
>
> Repository Root: https://svn.code.sf.net/p/wsjt/wsjt
>
> Repository UUID: ab8295b8-cf94-4d9e-aec4-7959e3be5d79
>
> Revision: 8658
>
>
>
> on
>
>
>
>   System Version: macOS 10.13.4 (17E202)
>
>   Kernel Version: Darwin 17.5.0
>
>
>
> I have had a succession of issues satisfying build tool chain especially
> concerning Fortran.
>
>
>
> Presently it is using:
>
>
>
> FC   = gfortran
>
> FCV= gnu95
>
>
>
> I have an issue with unresolved symbols for x86_64 which will definitely
> be an issue with my build environment.
>
>
>
> I was wondering someone who builds on OSX could give me some pointers as
> to how they set their environment up please.
>
>
>
> Megan
>
>
>
>
>
> Here is the failing output:
>
>
>
> RUN F2PY Audio.so
>
> -
>
> /usr/local/Cellar/numpy/1.14.3_1/bin/f2py3.6 -c --quiet --fcompiler=gnu95
> --f77exec=gfortran --f90exec=gfortran \
>
> --opt="-cpp -fbounds-check -O2"  -L/usr/local/lib
> -L/usr/local/Cellar/portaudio/19.6.0/lib
> -L/usr/local/Cellar/portaudio/19.6.0/lib -L/usr/local/lib  -L -lfftw3f
> -lportaudio -lpthread -lsamplerate  libjt.a -m Audio ftn_init.f90
> ftn_quit.f90 audio_init.f90 spec.f90 getfile.f90 azdist0.f90 astro0.f90
> chkt0.f90
>
> rmbadname1: Replacing "len" with "len_bn".
>
> {}
>
> {}
>
> {}
>
> {}
>
> {}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(in)']}
>
> {'attrspec': ['intent(in)']}
>
> {'attrspec': ['intent(in)']}
>
> {'attrspec': ['intent(in)']}
>
> {'attrspec': ['intent(in)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> {'attrspec': ['intent(out)']}
>
> In file included from
> /var/folders/dk/dhmpt9ts4ylfqywy01_83whwgn/T/tmp0nf1vt18/src.macosx-10.13-x86_64-3.6/Audiomodule.c:16:
>
> In file included from
> /var/folders/dk/dhmpt9ts4ylfqywy01_83whwgn/T/tmp0nf1vt18/src.macosx-10.13-x86_64-3.6/fortranobject.h:13:
>
> In file included from
> /usr/local/lib/python3.6/site-packages/numpy/core/include/numpy/arrayobject.h:4:
>
> In file included from
> /usr/local/lib/python3.6/site-packages/numpy/core/include/numpy/ndarrayobject.h:18:
>
> In file included from
> /usr/local/lib/python3.6/site-packages/numpy/core/include/numpy/ndarraytypes.h:1816:
>
> /usr/local/lib/python3.6/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2:
> warning: "Using deprecated NumPy API, disable it by "  "#defining
> NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-W#warnings]
>
> #war