Re: [Xastir] -Lrtree -ltree ... may have found where...
On Sun, 1 Jul 2007, Richard Polivka, N6NKO wrote: > IIRC, my laptop version of xastir had me compile separately GDAL. BigBox > got GDAL from the repo. > > All I can say is "AIIIEEE" as he runs into the darkness, holding his > head, and thinking of Muench. Very few Xastir users have a need for the GDAL library. I'd suggest configuring Xastir with the --without-gdal option if you can do without it. About the only thing I've done somewhat regularly with GDAL was use the TIGER/Line vector map files directly for testing, but it's so slow to do this that I try to avoid it. A few other obtuse vector map formats are gotten to with the GDAL library in Xastir, but 99% of the users out there will never need them. ./configure --without-gdal make && sudo make install -- Curt, WE7U. APRS Client Comparisons: http://www.eskimo.com/~archer "Lotto:A tax on people who are bad at math." -- unknown "Windows: Microsoft's tax on computer illiterates." -- WE7U "The world DOES revolve around me: I picked the coordinate system!" ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] -Lrtree -ltree ... may have found where...
Tom, IIRC, my laptop version of xastir had me compile separately GDAL. BigBox got GDAL from the repo. All I can say is "AIIIEEE" as he runs into the darkness, holding his head, and thinking of Muench. 73 from 807, Richard, N6NKO Tom Russo wrote: On Sun, Jul 01, 2007 at 07:35:33AM -0700, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: Apparently, Fedora 7 on my system loaded parts of GRASS. The ldd search of 1.9.1 that worked showed libgrass_rtree.so.6.2 being linked in. Changing the variable names, I believe that what was done, that was done in the CVS , avoided the linker bringing in libgrass_rtree because it could not find the symbols. What I find interesting is that nm can't find any labels in libgrass_rtree. Maybe I did not pick the right option. But that can be for another time. Have to tackle the outside honeydo list. AH HAH! I bet your GDAL was built with GRASS support, and that's how it's getting in. Try doing an ldd on the GDAL shared library, and you'll probably find that that is where the libgrass_rtree is being dragged in. Since you're not explicitly linking against grass libraries, and the only other GIS-related library that you're using is GDAL, that is the most likely suspect. GDAL should almost never need to be built with GRASS support, because that results in a circular dependency (GRASS needs GDAL to build, GDAL needs GRASS to read GRASS data), so there's a "GRASS plugin" that can be used to add GRASS support to GDAL without rebuilding it. That's the preferred method. The GDAL package you installed was probably not built according to that preferred method. The easiest fix, then, is to build GDAL from source instead of using a package. No, that's not true. The easiest fix is to de-install GDAL unless you're using it for some other GIS package, and then rebuild xastir without it --- Xastir barely uses GDAL except for some very specific vector data types, and unless you're using those you need not even bother with GDAL support in xastir. If you *are* using GDAL for some other GIS-related package, you could always rebuild xastir with "--without-gdal" in the configure options, too. ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] -Lrtree -ltree ... may have found where...
On Sun, Jul 01, 2007 at 07:35:33AM -0700, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > Apparently, Fedora 7 on my system loaded parts of GRASS. The ldd search of > 1.9.1 that worked showed libgrass_rtree.so.6.2 being linked in. Changing the > variable names, I believe that what was done, that was done in the CVS , > avoided the linker bringing in libgrass_rtree because it could not find the > symbols. What I find interesting is that nm can't find any labels in > libgrass_rtree. Maybe I did not pick the right option. But that can be for > another time. Have to tackle the outside honeydo list. AH HAH! I bet your GDAL was built with GRASS support, and that's how it's getting in. Try doing an ldd on the GDAL shared library, and you'll probably find that that is where the libgrass_rtree is being dragged in. Since you're not explicitly linking against grass libraries, and the only other GIS-related library that you're using is GDAL, that is the most likely suspect. GDAL should almost never need to be built with GRASS support, because that results in a circular dependency (GRASS needs GDAL to build, GDAL needs GRASS to read GRASS data), so there's a "GRASS plugin" that can be used to add GRASS support to GDAL without rebuilding it. That's the preferred method. The GDAL package you installed was probably not built according to that preferred method. The easiest fix, then, is to build GDAL from source instead of using a package. No, that's not true. The easiest fix is to de-install GDAL unless you're using it for some other GIS package, and then rebuild xastir without it --- Xastir barely uses GDAL except for some very specific vector data types, and unless you're using those you need not even bother with GDAL support in xastir. If you *are* using GDAL for some other GIS-related package, you could always rebuild xastir with "--without-gdal" in the configure options, too. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM "And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit!" --- The Tick ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
[Xastir] -Lrtree -ltree ... may have found where...
Apparently, Fedora 7 on my system loaded parts of GRASS. The ldd search of 1.9.1 that worked showed libgrass_rtree.so.6.2 being linked in. Changing the variable names, I believe that what was done, that was done in the CVS , avoided the linker bringing in libgrass_rtree because it could not find the symbols. What I find interesting is that nm can't find any labels in libgrass_rtree. Maybe I did not pick the right option. But that can be for another time. Have to tackle the outside honeydo list. 73 from 807, Richard, N6NKO ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
