Tom, I have to thank you and all of the team that support Xastir. There are I believe a bunch of users that listen and try and learn from all the developers here. I am one.
Once again thanks. Stan Sent from my iPhone > On Aug 17, 2014, at 12:05 PM, Tom Russo <[email protected]> wrote: > > On Tue, Jun 17, 2014 at 10:11:50PM -0700, we recorded a bogon-computron > collision of the <[email protected]> flavor, containing: >> On 06/17/2014 05:35 PM, Ryan Stark wrote: >>> Yes, it would be: >>> ./configure CFLAGS="-fPIC" CPPFLAGS="-I/usr/include/geotiff" >>> >>> using -fPIC for the whole build is suboptimal, I'll try and figure out how >>> to fix it tonight. > > It's been a while since this question was asked, but I've only just upgraded > to 14.04 myself and found the real solution. > > Xastir's configure script was putting the cflags from GraphicsMagick-config > into CXXFLAGS (which we use for precisely nothing) and not into CFLAGS (which > we use for everything). > > The inconsistency in flags from putting the ldflags from Magick into LDFLAGS, > but not the cflags into CFLAGS is the source of this relocation error. > > I have just committed the fix. > > It would probably be good to do a stable release soon. Just sayin'. > > >>>> On June 17, 2014 2:50:52 PM MST, Lee Bengston <[email protected]> >>>> wrote: >>>> On Tue, Jun 17, 2014 at 4:01 AM, Ryan Stark <[email protected]> wrote: >>>> >>>> >>>>> --- >>>>> ??? snip---??? >>>>> >>>>> >>>>> As a broad work around I did what the compiler suggested and did: >>>>> make clean >>>>> ../configure CPPFLAGS="-fPIC -I/usr/include/geotiff" >>>>> make >>>>> >>>>> and as expected the error goes away but then all of the executables >>>> are >>>>> PIC enabled64 >>>>> AMD64 requires shared libraries to be compiled with -fPIC, ia32 does >>>> not >>>>> thus you don't see the error on your 32bit ATOM box. >>>>> >>>>> It looks like this topic came up on the list last June as well: >>>>> http://lists.xastir.org/pipermail/xastir/2013-June/thread.html#21654 >>>>> "[Xastir] More Kubuntu 13 map problems" >>>>> >>>>> >>>> ???yes, I forgot about that one. The user's solution in that case >>>> according >>>> to his message was... >>>> >>>> ./configure CPPFLAGS="-I/usr/include/geotiff" CFLAGS=-fPIC"??? >>>> >>>> ???Hmm, I copy/pasted the above from Jim's message from last year, but it >>>> looks like it could be missing a set of double quotes? >>>> >>>> ???Lee - K5DAT >> Looks like for debian based distros we grab the GraphicsMagick cflags >> and build with those to be compatile. >> On my amd64 ubuntu vm those look like: >> # GraphicsMagick-config --cflags >> -fopenmp -Wall -g -fno-strict-aliasing -fPIE -fstack-protector --param >> ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security >> -Werror=format-security -O2 -Wall -pthread >> >> I was able to build after using those flags: >> ./configure CFLAGS="-I/usr/include/geotiff $(GraphicsMagick-config >> --cflags)" >> >> -Ryan >> _______________________________________________ >> Xastir mailing list >> [email protected] >> http://xastir.org/mailman/listinfo/xastir > > -- > Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ > Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > > > > _______________________________________________ > Xastir mailing list > [email protected] > http://xastir.org/mailman/listinfo/xastir _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
