Hi Jon,
you misread my question, I was asking for the CMakeCache.txt file which
you will find at the top level of the build directory tree after running
the CMake configuration command.
GNU gcc 4.2 does have OpenMP support for C/C++/Fortran so it should
have been detected by the CMake configuration, although that was fairly
early days for GNU gcc OpenMP support as I think it only started at 4.2.0.
The output you gave for `gcc -v` doesn't look complete, what I was most
interested in was the record of the configure command used to build the
compiler suite.
73
Bill
G4WJS.
On 17/01/2019 15:47, Jon Tabor wrote:
Attached is the clean CMakeLists.txt.
Interestingly, it appears that my gcc build from ports didn't install
properly (which is impressive; OpenBSD ports are nearly foolproof --
guess I showed them!), so gcc -v actually shows 4.2.1:
Reading specs from /usr/lib/gcc-lib/amd64-unknown-openbsd6.4/4.2.1/specs
Target: amd64-unknown-openbsd6.4
Configured with: OpenBSD/amd64 system compiler
Thread model: posix
gcc version 4.2.1 20070719
I'm going to rebuild gcc 4.9.4 from ports and rebuild WSJT-X with a
clean CMakeLists.txt and see where that lands me.
Thanks,
Jon
KI7JYE
On Wed, Jan 16, 2019 at 5:39 PM Bill Somerville <g4...@classdesign.com
<mailto:g4...@classdesign.com>> wrote:
Hi Jon,
can you send me a CMakeCache.txt file from a clean CMake configure
without your patch please? Also what does this print:
gcc -v
73
Bill
G4WJS.
On 17/01/2019 01:19, Jon Tabor wrote:
gcc 4.9.4 built from the OpenBSD ports system.
Jon
On Wed, Jan 16, 2019, 16:08 Bill Somerville
<g4...@classdesign.com <mailto:g4...@classdesign.com> wrote:
On 16/01/2019 23:28, Jon Tabor wrote:
> CMake obviously didn't find that my compiler supported OpenMP.
Hi Jon,
what is your compiler?
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
