On Tue, Oct 27, 2015 at 12:54 PM, Bill Somerville <[email protected]> wrote:
> On 27/10/2015 17:38, Richard Shaw wrote: > > On Tue, Oct 27, 2015 at 11:34 AM, Bill Somerville < > <[email protected]>[email protected]> wrote: > >> On 27/10/2015 16:00, Richard Shaw wrote: >> Hi Richard, >> > I ran into an additional issue with hamlib not being built with -fPIC >> > which caused the wsjtx build to fail during linking but I fought >> > through that and now have good builds of wsjtx 1.5.1-rc2 for Fedora >> > 21, 22, and Rawhide. I forgot to add F23 to the COPR so that build is >> > happening now. >> > >> > https://copr.fedoraproject.org/coprs/hobbes1069/WSJT/ >> > >> You should be building wsjx-1.5.0 not -rc2. >> > > I could probably change it if no one has upgraded yet but is there a known > problem with 1.5.1-rc2 that is of concern? > > There is no tag wsjtx-1.5.1-rc2 so I assume you are using the > wsjtx-1.5.0-rc2 tag, that is basically OK on Linux since the man difference > between wsjtx-1.5.0-rc2 and the GA release wsjtx-1.5.0 is for OmniRig which > is MS Windows only. There is a small change to the UDP interface behaviour > but I doubt anyone would notice. > Ok, I guess I was going by the current checkout of the wsjtx-1.5 branch which does have the version set to 1.5.1-rc1... I guess I did mess up the rc #. I am surprised that PIC code was required, Hamlib is statically linked >> and therefore does not need to be PIC. I would be interested to see the >> errors from that. > > > I didn't get the error on Fedora 21, only 22+, I wonder if it's something > that newer versions of gcc have turned from a warning to an error? > > OK, I have an FC22 VM so I will investigate there. Was the issue was on > 64-bit builds? > Yes, I only tested on x86_64 before doing COPR builds. Thanks, Richard
------------------------------------------------------------------------------
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
