Re: [wsjt-devel] OpenBSD build problem

[Larry Gadallah]

On Sun, 10 Nov 2019 at 04:14, Bill Somerville  wrote:

> Message: 3
> Date: Sun, 10 Nov 2019 00:22:42 +
> From: Bill Somerville 
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] OpenBSD build problem
> Message-ID: <32c76b4f-02d7-8f43-ab42-8b51e6048...@classdesign.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> On 10/11/2019 00:02, Larry Gadallah wrote:
> > Modifying CMakeCache.txt to point at gcc 8.3.0 and egfortan over in
> > /usr/local/bin, and adding the global option -fopenmp to the compilers
>
> Hi Larry,
>
> don't do this, CMake will figure out how to build WSJT-X itself, just
> set the compiler(s) by defining CMAKE__COMPILER to the
> compiler driver path where  are the compiler names (C, CXX,
> Fortran), or simply put the compiler on the path.
>
> Having said that the compiler driver you are using (egcc) is configured
> without the OpenMP suppprt (--disable-libgomp). Are you sure that is a
> general desktop system compiler, egcc sounds like some embedded compiler
> designed to make minimal size executables for embedded systems.
>
> 73
> Bill
> G4WJS.
>

Bill:

As near as I can tell, the OpenBSD people have become so militantly
anti-Gnu, that the egcc port is a version of GCC et al from 2007, before
the GPL v3 license was applied. Unfortunately this might mean that features
from newer versions of GCC (like OpenMP) may not be present. I'll follow
your advice regarding CMAKE_*_COMPILER and see how much further I can get.

Thanks,



-- 
Larry Gadallah, lgadallah AT gmail DOT com
PGP Sig: AE93 1785 6874 7111 48AD  63A6 2136 3651 981C F87B
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] OpenBSD build problem

[Bill Somerville]

On 10/11/2019 00:02, Larry Gadallah wrote:
Modifying CMakeCache.txt to point at gcc 8.3.0 and egfortan over in 
/usr/local/bin, and adding the global option -fopenmp to the compilers


Hi Larry,

don't do this, CMake will figure out how to build WSJT-X itself, just 
set the compiler(s) by defining CMAKE__COMPILER to the 
compiler driver path where  are the compiler names (C, CXX, 
Fortran), or simply put the compiler on the path.


Having said that the compiler driver you are using (egcc) is configured 
without the OpenMP suppprt (--disable-libgomp). Are you sure that is a 
general desktop system compiler, egcc sounds like some embedded compiler 
designed to make minimal size executables for embedded systems.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] OpenBSD build problem

[Larry Gadallah]

On 18/01/2019 01:12. Bill Somerville wrote:

> On 17/01/2019 22:27, Jon Tabor wrote:
> > Target: x86_64-unknown-openbsd6.4
> > Configured with: /usr/obj/ports/gcc-4.9.4/gcc-4.9.4/configure
> > --enable-libgcj --without-jar --verbose
> > --program-transform-name='s,^,e,' --disable-nls --with-system-zlib
> > --disable-libmudflap *--disable-libgomp* --disable-tls --with-gnu-ld
> > --with-gnu-as --enable-threads=posix --enable-wchar_t
> > --with-gmp=/usr/local --enable-languages=c,c++,fortran,objc,java,ada
> > --disable-libstdcxx-pch --enable-cpp --prefix=/usr/local
> > --sysconfdir=/etc --mandir=/usr/local/man --infodir=/usr/local/info
> > --localstatedir=/var --disable-silent-rules --disable-gtk-doc
> > Thread model: posix
> > gcc version 4.9.4 (GCC)
>
>
> Hi Jon,
>
> and there is the issue, for some reason the author of the OpenBSD recipe
> to build gcc/g++/gfortran has elected to disable OpenMP, or at lest the
> support library for it.
>
> 73
> Bill
> G4WJS.

I've picked this up again with OpenBSD 6.6 amd64, and after installing Gnu
CC 8.3.0 et al:

openbsd66$ egcc -v
Using built-in specs.
COLLECT_GCC=egcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-unknown-openbsd6.6/8.3.0/lto-wrapper
Target: x86_64-unknown-openbsd6.6
Configured with: /usr/obj/ports/gcc-8.3.0/gcc-8.3.0/configure
--with-stage1-ldflags=-L/usr/obj/ports/gcc-8.3.0/bootstrap/lib --verbose
--program-transform-name='s,^,e,' --disable-nls --with-system-zlib
--disable-libmudflap --disable-libgomp --disable-libssp --disable-tls
--with-gnu-ld --with-gnu-as --enable-threads=posix --enable-wchar_t
--with-gmp=/usr/local --enable-languages=c,c++,fortran,objc,ada
--disable-libstdcxx-pch --enable-default-ssp --enable-default-pie
--without-isl --enable-cpp --prefix=/usr/local --sysconfdir=/etc
--mandir=/usr/local/man --infodir=/usr/local/info --localstatedir=/var
--disable-silent-rules --disable-gtk-doc
Thread model: posix
gcc version 8.3.0 (GCC)

Modifying CMakeCache.txt to point at gcc 8.3.0 and egfortan over in
/usr/local/bin, and adding the global option -fopenmp to the compilers, we
get this result:

openbsd66$ cmake ../src
-- The C compiler identification is GNU 8.3.0
-- The CXX compiler identification is Clang 8.0.1
-- The Fortran compiler identification is GNU 8.3.0
-- Check for working C compiler: /usr/local/bin/egcc
-- Check for working C compiler: /usr/local/bin/egcc -- broken
CMake Error at /usr/local/share/cmake/Modules/CMakeTestCCompiler.cmake:60
(message):
  The C compiler

"/usr/local/bin/egcc"

  is not able to compile a simple test program.

  It fails with the following output:

Change Dir: /home/larry/projects/wsjt-wsjtx/build/CMakeFiles/CMakeTmp

Run Build Command(s):/usr/bin/make cmTC_9fdaf/fast && /usr/bin/make -f
CMakeFiles/cmTC_9fdaf.dir/build.make CMakeFiles/cmTC_9fdaf.dir/build
Building C object CMakeFiles/cmTC_9fdaf.dir/testCCompiler.c.o
/usr/local/bin/egcc   -fopenmp-o
CMakeFiles/cmTC_9fdaf.dir/testCCompiler.c.o   -c
/home/larry/projects/wsjt-wsjtx/build/CMakeFiles/CMakeTmp/testCCompiler.c
Linking C executable cmTC_9fdaf
/usr/local/bin/cmake -E cmake_link_script
CMakeFiles/cmTC_9fdaf.dir/link.txt --verbose=1
/usr/local/bin/egcc -fopenmp
CMakeFiles/cmTC_9fdaf.dir/testCCompiler.c.o  -o cmTC_9fdaf
-Wl,-rpath-link,/usr/X11R6/lib:/usr/local/lib
egcc: error: libgomp.spec: No such file or directory
*** Error 1 in . (CMakeFiles/cmTC_9fdaf.dir/build.make:87 'cmTC_9fdaf')
*** Error 1 in
/home/larry/projects/wsjt-wsjtx/build/CMakeFiles/CMakeTmp (Makefile:121
'cmTC_9fdaf/fast')





  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:25 (project)


-- Configuring incomplete, errors occurred!
See also "/home/larry/projects/wsjt-wsjtx/build/CMakeFiles/CMakeOutput.log".
See also "/home/larry/projects/wsjt-wsjtx/build/CMakeFiles/CMakeError.log".

I grepped about for a bit for information about where the missing
libgomp.spec file should live, and I couldn't find anything. Searching the
system for .spec files yields the following:

openbsd66# find / -depth -name "*.spec"
/home/larry/projects/wsjt-wsjtx/src/boost/tools/build/src/engine/boost-jam.spec
/usr/local/lib/libitm.spec
/usr/local/lib/libgfortran.spec
/usr/local/share/libxml2/docbook.spec
/usr/local/share/libxml2/docbook-xsl.spec

Makes it look like maybe OpenMP support is only partially present?

--
Larry Gadallah, lgadallah AT gmail DOT com
PGP Sig: AE93 1785 6874 7111 48AD  63A6 2136 3651 981C F87B
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] OpenBSD build problem

[Jon Tabor]

Good catch!  Okay, I'll investigate, and possibly reach out to the OpenBSD
team. Generally they disable things for security reasons.

73!
Jon
KI7JYE

On Thu, Jan 17, 2019, 17:15 Bill Somerville  On 17/01/2019 22:27, Jon Tabor wrote:
>
> Target: x86_64-unknown-openbsd6.4
> Configured with: /usr/obj/ports/gcc-4.9.4/gcc-4.9.4/configure
> --enable-libgcj --without-jar --verbose --program-transform-name='s,^,e,'
> --disable-nls --with-system-zlib --disable-libmudflap *--disable-libgomp*
> --disable-tls --with-gnu-ld --with-gnu-as --enable-threads=posix
> --enable-wchar_t --with-gmp=/usr/local
> --enable-languages=c,c++,fortran,objc,java,ada --disable-libstdcxx-pch
> --enable-cpp --prefix=/usr/local --sysconfdir=/etc --mandir=/usr/local/man
> --infodir=/usr/local/info --localstatedir=/var --disable-silent-rules
> --disable-gtk-doc
> Thread model: posix
> gcc version 4.9.4 (GCC)
>
> Hi Jon,
>
> and there is the issue, for some reason the author of the OpenBSD recipe
> to build gcc/g++/gfortran has elected to disable OpenMP, or at lest the
> support library for it.
>
> 73
> Bill
> G4WJS.
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] OpenBSD build problem

[Bill Somerville]

On 17/01/2019 22:27, Jon Tabor wrote:

Target: x86_64-unknown-openbsd6.4
Configured with: /usr/obj/ports/gcc-4.9.4/gcc-4.9.4/configure 
--enable-libgcj --without-jar --verbose 
--program-transform-name='s,^,e,' --disable-nls --with-system-zlib 
--disable-libmudflap *--disable-libgomp* --disable-tls --with-gnu-ld 
--with-gnu-as --enable-threads=posix --enable-wchar_t 
--with-gmp=/usr/local --enable-languages=c,c++,fortran,objc,java,ada 
--disable-libstdcxx-pch --enable-cpp --prefix=/usr/local 
--sysconfdir=/etc --mandir=/usr/local/man --infodir=/usr/local/info 
--localstatedir=/var --disable-silent-rules --disable-gtk-doc

Thread model: posix
gcc version 4.9.4 (GCC)


Hi Jon,

and there is the issue, for some reason the author of the OpenBSD recipe 
to build gcc/g++/gfortran has elected to disable OpenMP, or at lest the 
support library for it.


73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] OpenBSD build problem

[Jon Tabor]

Hey Bill, apologies.  Attached is the CMakeCache.txt file.

I updated gcc to 4.9.4, and here's the output of `gcc -v`:

Using built-in specs.
Using built-in specs.
COLLECT_GCC=egcc
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-unknown-openbsd6.4/4.9.4/lto-wrapper
Target: x86_64-unknown-openbsd6.4
Configured with: /usr/obj/ports/gcc-4.9.4/gcc-4.9.4/configure
--enable-libgcj --without-jar --verbose --program-transform-name='s,^,e,'
--disable-nls --with-system-zlib --disable-libmudflap --disable-libgomp
--disable-tls --with-gnu-ld --with-gnu-as --enable-threads=posix
--enable-wchar_t --with-gmp=/usr/local
--enable-languages=c,c++,fortran,objc,java,ada --disable-libstdcxx-pch
--enable-cpp --prefix=/usr/local --sysconfdir=/etc --mandir=/usr/local/man
--infodir=/usr/local/info --localstatedir=/var --disable-silent-rules
--disable-gtk-doc
Thread model: posix
gcc version 4.9.4 (GCC)



Jon
KI7JYE

On Thu, Jan 17, 2019 at 8:01 AM Bill Somerville 
wrote:

> 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 
> 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 >
>>> 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
>
# This is the CMakeCache file.
# For build in directory: /home/taborj/build/wsjtx-2.0.0/build
# It was generated by CMake: /usr/local/bin/cmake
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.


# EXTERNAL cache entries


//Path to a program.
CMAKE_AR:FILEPATH=/usr/bin/ar

//Choose the type of build, options are: None(CMAKE_CXX_FLAGS or
// CMAKE_C_FLAGS used) Debug Release RelWithDebInfo MinSizeRel.
CMAKE_BUILD_TYPE:STRING=

//Enable/Disable color output during build.
CMAKE_COLOR_MAKEFILE:BOOL=ON

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=/usr/local/bin/eg++

//A wrapper around 'ar' adding the appropriate '--plugin' option
// for the GCC compiler
CMAKE_CXX_COMPILER_AR:FILEPATH=CMAKE_CXX_COMPILER_AR-NOTFOUND

//A wrapper around 'ranlib' adding the appropriate '--plugin' option
// for the GCC compiler
CMAKE_CXX_COMPILER_RANLIB:FILEPATH=CMAKE_CXX_COMPILER_RANLIB-NOTFOUND

//Flags used by the compiler during all build types.
CMAKE_CXX_FLAGS:STRING=

//Flags used by the compiler during debug builds.
CMAKE_CXX_FLAGS_DEBUG:STRING=-g

//Flags used by the compiler during release builds for minimum
// size.
CMAKE_CXX_FLAGS_MINSIZEREL:STRING=-DNDEBUG

//Flags used by the compiler during release builds.
CMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG

//Flags used by the compiler during release builds with debug info.
CMAKE_CXX_FLAGS_RELWITHDEBINFO:STRING=-g -DNDEBUG

//C compiler
CMAKE_C_COMPILER:FILEPATH=/usr/local/bin/egcc

//A wrapper around 'ar' adding the appropriate '--plugin' option
// for the GCC compiler
CMAKE_C_COMPILER_AR:FILEPATH=CMAKE_C_COMPILER_AR-NOTFOUND

//A wrapper around 

Re: [wsjt-devel] OpenBSD build problem

[Bill Somerville]

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 > 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
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

Re: [wsjt-devel] OpenBSD build problem

[Jon Tabor]

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 
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 
>> 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?
>>
>> 73
>> Bill
>> G4WJS.
>>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
cmake_minimum_required (VERSION 2.8.10 FATAL_ERROR)

if (APPLE)
  #
  # The following variables define the portability and compatability attributes 
of the Mac OS X build
  # they are choosen with care and should not be changed without good cause.
  #
  # Among other things these options are chosen to match the portability and 
compatability options of the
  # Qt framework dylibs which can be checked as follows:
  #
  # otool -l  | grep -A3 LC_VERSION_MIN_MACOSX
  #
  set (CMAKE_OSX_DEPLOYMENT_TARGET 10.9
CACHE STRING "Earliest version of OS X supported

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
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).
Do not override this if you intend to build an official deployable installer.")
endif (APPLE)

project (wsjtx C CXX Fortran)

#
# CMake policies
#
if (POLICY CMP0020)
  cmake_policy (SET CMP0020 NEW) # link to Qt winmain on Windows
endif (POLICY CMP0020)

if (POLICY CMP0043)
  cmake_policy (SET CMP0043 NEW) # ignore COMPILE_DEFINITIONS_
endif (POLICY CMP0043)

if (POLICY CMP0063)
  cmake_policy (SET CMP0063 NEW) # honour visibility properties for all library 
types
endif (POLICY CMP0063)

include (${PROJECT_SOURCE_DIR}/CMake/VersionCompute.cmake)
message (STATUS "Building ${CMAKE_PROJECT_NAME}-${wsjtx_VERSION}")

#
# project information
#
set (PROJECT_NAME "WSJT-X")
set (PROJECT_VENDOR "Joe Taylor, K1JT")
set (PROJECT_CONTACT "Joe Taylor ")
set (PROJECT_COPYRIGHT "Copyright (C) 2001-2018 by Joe Taylor, K1JT")
set (PROJECT_HOMEPAGE http://www.physics.princeton.edu/pulsar/K1JT/wsjtx.html)
set (PROJECT_MANUAL wsjtx-main)
set (PROJECT_MANUAL_DIRECTORY_URL 
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/)
set (PROJECT_SAMPLES_URL http://downloads.sourceforge.net/project/wsjt/)
set (PROJECT_SAMPLES_UPLOAD_DEST frs.sourceforge.net:/home/frs/project/wsjt/)
set (PROJECT_SUMMARY_DESCRIPTION "${PROJECT_NAME} - Digital Modes for Weak 
Signal Communicaitons in Amateur Radio.")
set (PROJECT_DESCRIPTION "${PROJECT_SUMMARY_DESCRIPTION}
 ${PROJECT_NAME} is a computer program designed to facilitate basic amateur
 radio communication using very weak signals. The first four letters in
 the program name stand for `(W)eak (S)ignal communication by
 K1(JT),` while the suffix `-X` indicates that ${PROJECT_NAME} started as
 an extended and experimental branch of the program
 WSJT.
 .
 ${PROJECT_NAME} Version 1.8 offers nine different protocols or modes: FT8,
 JT4, JT9, JT65, QRA64, ISCAT, MSK144, WSPR, and Echo.
 The first five are designed for making reliable QSOs under extreme
 weak-signal conditions. They use nearly identical message structure
 and source encoding.  JT65 and QRA64 were designed for EME
 (`moonbounce`) on the VHF/UHF bands and have also proven very
 effective for worldwide QRP communication on the HF bands.  QRA64 has
 a number of advantages over JT65, including better performance on the
 very weakest signals.  We imagine that over time it may replace JT65
 for EME use.  JT9 was originally designed for the LF, MF, and lower HF
 bands.  Its submode JT9A is 2 dB more sensitive than JT65 while using
 less than 10% of the bandwidth.  JT4 offers a wide variety of tone
 spacings and has proven highly effective for EME on microwave bands up
 to 24 GHz.  These four `slow` modes use one-minute timed sequences
 of alternating transmission and reception, so a minimal 

Re: [wsjt-devel] OpenBSD build problem

[Bill Somerville]

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  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?

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] OpenBSD build problem

[Jon Tabor]

gcc 4.9.4 built from the OpenBSD ports system.

Jon


On Wed, Jan 16, 2019, 16:08 Bill Somerville  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?
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] OpenBSD build problem

[Bill Somerville]

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?

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] OpenBSD build problem

[Jon Tabor]

Replying to myself, as I've made some progress.  After allowing work to
distract me all day, I came back to this with fresh eyes and realized that,
duh, CMake obviously didn't find that my compiler supported OpenMP.  I
couldn't figure out a good way to make it detect it...so I just forced it.
Modified CMakeLists.txt in this way: (at line 834)

Replace this:
 find_package (OpenMP)

With this:
set (OPENMP_FOUND TRUE)

Okay, I know.  It's a workaround, not a solution, but it allowed the
program to build.

Now to work through all these relink errors that result in a core dump.

Jon Tabor
KI7JYE

On Wed, Jan 16, 2019 at 8:41 AM Jon Tabor  wrote:

> Hey folks, I've searched the archives but haven't found anything similar.
>
> Building on OpenBSD 6.4-current, everything goes swimmingly (aside from
> warnings about unused variables) until here:
>
> [ 93%] Building CXX object
> CMakeFiles/wsjtx.dir/widgets/ExportCabrillo.cpp.o
> [ 93%] Building CXX object CMakeFiles/wsjtx.dir/qrc_wsjtx.cpp.o
> [ 93%] Building CXX object
> CMakeFiles/wsjtx.dir/wsjtx_autogen/mocs_compilation.cpp.o
> [ 93%] Linking CXX executable wsjtx
> /usr/bin/ld: error: unable to find library -lwsjt_fort_omp
> collect2: error: ld returned 1 exit status
> *** Error 1 in . (CMakeFiles/wsjtx.dir/build.make:1003 'wsjtx')
> *** Error 1 in . (CMakeFiles/Makefile2:802 'CMakeFiles/wsjtx.dir/all')
> *** Error 1 in
> /home/taborj/build/wsjtx-2.0.0/build/wsjtx-prefix/src/wsjtx/CMake
> (Makefile:152 'all')
>
> Any ideas?  I've had no problems building on Linux, so I'm fairly
> convinced this is either something specific to OpenBSD or this particular
> system.
>
> Thanks!
> Jon Tabor
> KI7JYE
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] OpenBSD build problem

[Jon Tabor]

Hey folks, I've searched the archives but haven't found anything similar.

Building on OpenBSD 6.4-current, everything goes swimmingly (aside from
warnings about unused variables) until here:

[ 93%] Building CXX object CMakeFiles/wsjtx.dir/widgets/ExportCabrillo.cpp.o
[ 93%] Building CXX object CMakeFiles/wsjtx.dir/qrc_wsjtx.cpp.o
[ 93%] Building CXX object
CMakeFiles/wsjtx.dir/wsjtx_autogen/mocs_compilation.cpp.o
[ 93%] Linking CXX executable wsjtx
/usr/bin/ld: error: unable to find library -lwsjt_fort_omp
collect2: error: ld returned 1 exit status
*** Error 1 in . (CMakeFiles/wsjtx.dir/build.make:1003 'wsjtx')
*** Error 1 in . (CMakeFiles/Makefile2:802 'CMakeFiles/wsjtx.dir/all')
*** Error 1 in
/home/taborj/build/wsjtx-2.0.0/build/wsjtx-prefix/src/wsjtx/CMake
(Makefile:152 'all')

Any ideas?  I've had no problems building on Linux, so I'm fairly convinced
this is either something specific to OpenBSD or this particular system.

Thanks!
Jon Tabor
KI7JYE
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel