On Sun, Dec 21, 2014 at 01:12:29AM -0700, ki7mt wrote: > Hello All, > > Following dianora's commits to upgrade WSPR for FreeBSD ( which was > badly needed !!), I had to make a few changes for Linux, some were > already in the pipeline, others were to fix some syntax issues that > caused configure to fail. Details of the changes will be in the commit > log, but wanted to touch on a couple items for discussion here. > > In several targets we have duplicate flag entries (CF, FF and now > LIB/INC dir's). The default rules call the flags, then, in the target > itself, we call them again. If I recall, some of this was to resolve > compiling issues on Mac, but exactly what, I don't recall. I don't think > the duplication is a problem, but it's look odd scrolling across the screen. > > I think the f2py and python3 --with-xxx=/../../ is finally sorted out. > I've not tested a locally built Python3, but I have built and moved > f2py3 all over two boxes, and it seems to be picking up the location > correctly now.
I noted some other silliness with some flags you and I can discuss offline. I'd like to see those also fixed. > > dianora's commit added facilities to stipulate an alternate location for > portaudio v19 headers and libs, as FreeBSD has both v19 plus an older > version. I'm not sure why we can't use --libdir=/../../. and > --includedir=/../../ in either the autogen.sh or configure statements, > but can discuss that further off-line. Packages on FreeBSD are built in a clean environment and would only pick up the /usr/local/portaudio2 files. However, there are still many apps that users run that use the older portaudio18 libs in /usr/local that I wanted to ensure that the proper portaudio19 is picked up on systems. I don't know how other systems handle this tbh. I keep hoping portaudio folks finally release portaudio v19 so v18 can go away. ;) > > In any case, the Update I'm about commit needs testing on FreeBSD for > sure. I've tested 4 different Linux Distros / Versions, and all seems ok I have both a centos and Ubuntu system that I can test on that I run under bhyve on my FreeBSD system here. https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html Unfortunately I did not get a chance to test under either. Apologies. I'll test ASAP today. > there. I've tried ( several times ) to build a FreeBSD VM, all failed > for one reason or another, So I can't really test it much. When I find time, today hopefully, I will set you and Joe up with a FreeBSD bhyve instance that can be used with prior warning. (It will be on one of my development machines so it goes up and down.) > > 73's > Greg, KI7MT 73 Diane VA3DB (AKA Dianora) -- - d...@freebsd.org d...@db.net http://www.db.net/~db ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
