...

...

...

...

"Andy" == Andy Stewart <kb1oiq@mval.net> writes:

Andy> On 07/16/2016 04:48 PM, John Stoffel wrote:

...

John> So what if you just putt the following into the src/Makefile.am file:

...

John> AM_LDFLAGS = \ John> -lm

...

John> I put it after the AM_CPPFLAGS definition up top. Seemed to do what I John> needed, but I haven't setup an Ubuntu 16.04 test VM yet to confirm.

...

So I spun up a droplet on Digital Oceon running Ubuntu 16.04 and with the above change, and the following steps, I got it to compile....

# apt-get update # apt-get install gcc libhamlib-dev make libgtk-dev libgtkextra-dev libglib2.0-dev libgtk2.0-dev # wget http://download.savannah.gnu.org/releases/xlog/xlog-2.0.14beta.tar.gz # tar xzf xlog-2.0.14beta.tar.gz # cd xlog-2.0.14beta/ # vi src/Makefile.am

- added in AM_LDFLAGS = -lm

# ./configure # make

and it did it. I'd like to say I'm really impressed at how there are NO compile warnings at all. Nice clean coding!

But if you could get more detailed error messages from those reporting problems compiling, that would be a big help as well.

Thanks, John

Andy> HI John, Andy> When I took over this code base, I attacked the compile Andy> warnings. I recall also passing a switch that says "warnings Andy> are errors", in order to keep the code clean. I like that standard! Andy> Regargind "AM_LDFLAGS -lm", I'd swear I did that and it didn't work for Andy> me, so I tried again. Andy> After adding AM_LDFLAGS to Makefile.am, I assume you ran Andy> automake or perhaps "automake -a". Umm... I think I just did that the first time, then I blew it all away (xlog that is) and re-extracted it, modified the src/Makefile.am file and did the build. Andy> I tried it on my Ubuntu 16.04 and it did not work. It seems Andy> like your solution is the right one. Let me try blowing away my Andy> Ubuntu 16.04 in Virtualbox, in case something was corrupted, and Andy> I'll repeat the steps you listed above on a pristine Ubuntu Andy> 16.04. Post the errors and/or compile log so we can look at this. I don't think you need to blow away your Ubuntu VM at all, just do a fresh from scratch extract and patch of xlog instead.