On 01/18/2018 09:06 PM, Bill Somerville wrote:
Hi Bill, Jaroslav, Richard & all,
> that issue that Mike posted suddenly makes things clear to me. It would
> appear that Fedora is somehow enforcing that stack should not be
> executable. This is not compatible with WSJT-X's use of Fortran function
Hi, how I can ask ti mailing list?
Thabks
--
Inviato da myMail per Android--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot__
I have FT950, but it is the same..How you key PTT? Do you have any interface or
trying direct connect?
There can be issue with impedance on audio output. Try to put abt. 100nF
capacitor in series between output (I have also input) and data in (out) pin..
I have fit them inside the jack connector
Hi Ed
Just a guess as I don't have a FTdx-1200, how are you doing PTT? Older
Yaesu transceivers required you to ground the PTT pin in the data jack to
transmit audio. IE if you are are using some other method to switch the
xceiver to Xmit, it will not work. You have to ground the PTT pin in the
OK - this all gives me some ideas to run with.
rpmlint is warning about the executable stack, but I don't think
anything is enforcing it. Also, I expect a general protection fault
rather than a segmentation violation if the stack is not executable.
I'll check binaries here, and see if I can get
I wonder if anyone can give me some advice on using FT8 with an FTdx1200
connected through the data jack.
I’ve been trying to sort this out but am not getting anywhere.
If I plug a headset into the Mac’s audio out I hear the correct modulation
sound coming from FT8.
But when I route the audi
Here's my output:
$ readelf -lW `which jt9` | grep GNU_STACK
GNU_STACK 0x00 0x 0x 0x00
0x00 RWE 0x10
Thanks,
Richard
--
Check out the vibrant tech community on one of the
On 18/01/2018 17:38, Jaroslav Skarvada wrote:
- Original Message -
Out of curiosity I ran rpmlint on wsjtx and most of the output was pretty
much what I expected but one line in particular caught my eye.
wsjtx.x86_64: W: executable-stack /usr/bin/jt9
$ rpmlint -I executable-stack
execu
Does it do the same if you optimize?
Seehttps://gcc.gnu.org/bugzilla/show_bug.cgi?id=71729
de Mike W9MDB
On Thursday, January 18, 2018, 11:41:01 AM CST, Jaroslav Skarvada
wrote:
- Original Message -
> Out of curiosity I ran rpmlint on wsjtx and most of the output was pret
- Original Message -
> Out of curiosity I ran rpmlint on wsjtx and most of the output was pretty
> much what I expected but one line in particular caught my eye.
>
> wsjtx.x86_64: W: executable-stack /usr/bin/jt9
>
> $ rpmlint -I executable-stack
> executable-stack:
> The binary declare
I have not seen this crash but I get a crash when I try to enable
calibration mode but haven't had time to troubleshoot. FT8 has been rock
solid for me (Fedora 27 x86_64 w/ 1.8. from my COPR[1])
RIchard
KF5OIM
[1] https://copr.fedorainfracloud.org/coprs/hobbes1069/WSJT/
--
- Original Message -
> On 18/01/2018 12:40, Michael Pittaro wrote:
> > I'm seeing a fairly consistent failure where jt9 crashes when it's
> > started by wsjt-x on Fedora 27.
> >
> > The crash happens right after decode starts. It's somewhat
> > intermittent - it seems to always happen in
On 18/01/2018 12:40, Michael Pittaro wrote:
I'm seeing a fairly consistent failure where jt9 crashes when it's
started by wsjt-x on Fedora 27.
The crash happens right after decode starts. It's somewhat
intermittent - it seems to always happen in ft8 mode, but also
sometimes in jt9 and jt65+jt
I'm seeing a fairly consistent failure where jt9 crashes when it's
started by wsjt-x on Fedora 27.
The crash happens right after decode starts. It's somewhat
intermittent - it seems to always happen in ft8 mode, but also
sometimes in jt9 and jt65+jt9 mode.In general, it crashes on the
first
14 matches
Mail list logo
