Well, like picking a scab I just couldn't leave it alone, so I dug into the
Python3 package and figured out how to bootstrap it.
There are now more python packages in my COPR repository than wsjt related
packages, and I've still got a few more to go...
Thanks,
Richard
On Thursday, September 18, 2014 05:50:19 PM Joe Taylor wrote:
> On 9/18/2014 5:20 PM, Michael Black wrote:
> > If you enter a macro like "QRM PSE AGN?" WSJT-X still brings up the Log
> > window even though it's not a 73 (when you have the "Prompt me to log
> > QSO" option checked)
> >
> > Not actu
On 18/09/2014 20:25, Joe Taylor wrote:
> Hi all,
Hi Joe,
>
> In preparation for the public beta release of WSJT-X v1.4 planned for
> October 1, we need to agree on a revision number for the code and
> supporting files that will be tagged in the repository, made into a
> *.tar.gz file, etc., for the
On 9/18/2014 5:20 PM, Michael Black wrote:
> If you enter a macro like "QRM PSE AGN?" WSJT-X still brings up the Log
> window even though it's not a 73 (when you have the "Prompt me to log QSO"
> option checked)
>
> Not actually a bug per se but an unintended behavior I think.
The behavior you des
Hi Joe,
On 09/18/2014 01:25 PM, Joe Taylor wrote:
Hi all,
In preparation for the public beta release of WSJT-X v1.4 planned for
October 1, we need to agree on a revision number for the code and
supporting files that will be tagged in the repository, made into a
*.tar.gz file, etc., for the rele
If you enter a macro like "QRM PSE AGN?" WSJT-X still brings up the Log
window even though it's not a 73 (when you have the "Prompt me to log QSO"
option checked)
Not actually a bug per se but an unintended behavior I think.
Mike W9MDB
---
Hi Joe,
Sep 26 suits me fine - I leave for three weeks on Sep 29. I also wanted a tag
revision which I will use. Because of the disparate nature of the group Sep
26 is a bit vague since it is 24 hours long. It would helpful if you would
specify a start time as well.12:00 UTC 26 Sep?
Hi all,
In preparation for the public beta release of WSJT-X v1.4 planned for
October 1, we need to agree on a revision number for the code and
supporting files that will be tagged in the repository, made into a
*.tar.gz file, etc., for the release.
At present we're at revision 4337. As a str
Interesting seems like *any* (not exhaustively tested) Bold font
works... hadn't really tried any bold styling previously as I generally
don't care for all bold text. Using Monospace 8 Bold now; I'll continue
to use it until a more universal fix is coded for all styling.
73 Eric NO3M
On 09/
I can't promise they're 100% functional but I have built hamlib 3 (latest
git as of today) packages for Fedora 19, 20, & 21 and EPEL 7.
I tried EPEL 6 but autoconf is too old.
I renamed pretty much everything to be parallel installable with hamlib
1.2.X.X
Most of which was done through patching
I'm trying to build wsjtx for both EL 6 and 7. The EL 7 build succeeds but
the EL 6 build fails:
Building C object CMakeFiles/wsjt.dir/lib/gran.c.o
/builddir/build/BUILD/wsjtx-1.4.svn4524/lib/options.f90:301.4:
class(option), intent(in) :: opt
1
Error: Unclassifiable statement at (1)
/buil
On Wed, Sep 17, 2014 at 3:54 PM, KI7MT wrote:
> Hi Richard,
>
> I'm not well versed in EPEL, but, is EPEL ( RHEL, CentOS etc )? Does
> package inclusion or exclusion in EPEL mean Python3 based apps are a
> no-go for Fedora as well or are they managed separately?
>
Basically, Fedora EPEL are pack
Probably a bit pedantic on my part but the handling is inconsistent across
OS's.
The Windows null device is NUL:
#ifdef WIN32
iret=system('""'//trim(exe_dir)//'/kvasd" -q >NUL:"')
! iret=system('""'//trim(exe_dir)//'/kvasd" kvasd.dat >dev_null"')
#else
iret=system('"'//trim(exe_dir)//'/kvasd
13 matches
Mail list logo
