On Wed, 8 Apr 2009, Rick Green wrote:
> On Wed, 8 Apr 2009, Dale Seaburg wrote:
>
>> When I tried to recompile xastir 1.9.5, I ran into more "missing"
>> lib's,
>> tools, etc than you can shake a stick at. I spent my whole
>> evening trying to
>> chase each missing component. Often, a missing component needed
>> something
>> else for *it* to work. Sheesh! What a rat-race. That's when the
>> lightbulb
>> turned on and I remembered back to my earlier days of linux and
>> the developer
>> install option. I am backing up my effort on the Q1U as I write
>> this.
>> Tonight, I'll do the Xubunto 8.10 install *again* choosing the
>> custom path.
>> There may be an easier method, but it's not obvious to me at the
>> moment. I
>> finally got openMotif to compile - I couldn't find any of the Xm/
>> XM* stuff
>> needed by xastir. But, I still am getting an error when trying to
>> compile
>> pcre. lcms compiled OK. gdal installed OK by apt-get. And, on
>> it goes like
>> a cat chasing it's tail...
>>
> One of the beauties of the debian-based distros is the 'apt' system,
> which does a beautiful job of pulling in dependencies for you.
> If you are running the distros xastir package, and you want to roll
> your own from source, I don't believe you need to reinstall the
> entire OS,
> but just install the missing packages:
>
> sudo apt-get install build-essential cvs make automake
> ...will pull in the compiler and tools
These I had, but good info to know as I bring myself up to speed with
the latest linux distros.
>
> sudo apt-get build-dep xastir
> ...will pull in all the -dev header packages necessary to
> compile and
> link the version in the distro's repository. The libraries themselves
> should have been pulled in along with the distros xastir package.
This I did not know about. Very good Info, Rick! Thanks for
shedding light. That saved a LOT of opsys reload time. I do have a
DVD copy of openSUSE 11.1 that I was about to try next.
>
> At this point, you should be able to grab a source tree from a
> tarball
> or CVS, and configure and compile it. The output of configure will
> tell
> you about any libraries which are needed for new features not
> included in
> the distros version, but at this point you'll have all the latest
> bugfixes
> and tweaks, and probably only be lacking the latest 'experimental' map
> types.
And, the latest cvs I also had.
BUT... {there's always a but, ;-) } I still was getting errors
about missing Xm and X11 stuff in alerts.c, IIRC. Then, I remembered
that you could "help" configure by passing the X and motif include
paths. Dug around until I found where those were: /usr/include/X11
and /usr/include/Xm. Got rid of that problem. I never did find the
X11/xpm.h and Xm/XpmI.h files
But, then map_tif.c complained about not finding xtiffio.h and
geo_normalization.h. map_tif.c said that they should be local:
#include "*.h" syntax, but they were not on the cvs copy I received.
However, I had previously gotten geotiff with an apt-get. The
headers were in /usr/include/geotiff. But, no configure option to
point to that path - not sure how to adjust the building of configure
to add that option. I know it can be done.
My work-around was to change the two #include statements in map_tif.c
from #include "*.h" to #include <geotiff/*.h>. That did the trick
and I finally got a good make. After copying my static maps to the
new install path, I brought up xastir 1.9.5. Sweet!
A BIG thanks to Jerry for making the tnc-kiss configuration screen
compatible with my vertically-challenged PC. So Nice!
Thanks again for everyone's help. You guys are great.
73 - Dale. KG5LT