On 30/03/2017 00:12, Bill Somerville wrote:
> BTW the error message actually gives a better solution than any you
> have offered which is to use -fpermissive for the file which allows
> the code without the C++11 mandated error message for this undefined
> behaviour producing construct. Even
On 29/03/2017 23:47, Black Michael wrote:
Boost has been a PITA for yearscomplex+complicated code. There
were versions that weren't very portable for many years and broke
across compiler upgrades and such like we're seeing now.
Our philosophy was to simply get it to work for our app and
Boost has been a PITA for yearscomplex+complicated code. There were
versions that weren't very portable for many years and broke across compiler
upgrades and such like we're seeing now.Our philosophy was to simply get it to
work for our app and then leave it alone.
You can change that
On 29/03/2017 22:18, Black Michael wrote:
This fixes the compile problem. Had the same problem on Ubuntu 16.10
with gcc 6.2.0
The ~ returns an int, not an unsigned int. I think the older
compilers just let this slide and presumably shifted the sign bit out.
Hi Mike,
yes, it is one of the
This fixes the compile problem. Had the same problem on Ubuntu 16.10 with gcc
6.2.0
The ~ returns an int, not an unsigned int. I think the older compilers just
let this slide and presumably shifted the sign bit out.
https://www.dropbox.com/s/epumxiqrsufji7k/crc.diff?dl=1
de Mike W9MDB
GCC on Fedora Core 25
On Wed, Mar 29, 2017, 11:09
wrote:
> Send wsjt-devel mailing list submissions to
> wsjt-devel@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
On 29/03/2017 03:14, Josh Rovero wrote:
> /home/josh/Downloads/wsjtx_src/lib/crc12.cpp:14:57: required from here
> /home/josh/Downloads/wsjtx_src/boost/boost/crc.hpp:350:69: warning:
> left shift of negative value [-Wshift-negative-value]
> BOOST_STATIC_CONSTANT( least, sig_bits = (~(