[Fwd: [Xastir] No xastir executable]

[Tom Russo]

On Sun, Feb 24, 2008 at 01:59:59PM -0600, we recorded a bogon-computron collision of the <jjolin at itol.com> flavor, containing:
> Tom Russo wrote:
>> On Sat, Feb 23, 2008 at 03:33:21PM -0600, we recorded a bogon-computron collision of the <jjolin at itol.com> flavor, containing:
>>   
>>> Tom Russo wrote:
>>>     
>>>> On Fri, Feb 22, 2008 at 06:54:57PM -0800, we recorded a bogon-computron collision of the <davidf4 at mindspring.com> flavor, containing:
>>> missing dev file.  Everything went fine until I ran xastir.  It told me 
>>> the berkeley db header and the library file do not match...disabling map 
>>> caching.  The header file is 4.4.20 and the library file is 4.5.20. Does 
>>> it matter which version I use as long as they are the same?
>>>     
>> 
>> the latest version, too.  You probably have libbdb4.4, libbdb4.4-dev, and 
>> libbdb4.5.  Get rid
>> of the middle one and install libbdb4.5-dev.
>> 
>>   
> Well I tried your suggestion and I am stuck.  First installed libdb 
> 4.5.20-dev and that went ok.  My next step was to uninstall 4.4 but I tried 
> to uninstall the library and that I could see was not a good idea...too 
> many programs would get broken.  

Yeah, you wouldn't need to remove the 4.4 libraries, only the dev headers.

> I read your post again and saw I should 
> get rid of 4.4 dev, but that is not installed to start with.  After all 
> this xastir still complains about the mis-match.  I am using xastir 1.9.3 
> development.

Well, that's puzzling.  For Xastir to have found 4.4 header files, they have
to be around from somewhere.  Try doing

  find / -name 'db*.h'

and see what it comes up with.  It's possible that Xastir's config file is
finding some errant file that isn't part of a package.  Figuring out what
file it's actually using will take some investigating.  You might be able
to figure out what it's found by looking at config.log --- perhaps there are
clues there to how it's located a db.h file and where it lives.

You can force the issue by giving configure the 
--with-bdb-incdir=/path/to/db/headers option: make sure you know where the
good Berkeley DB headers live and then give that path, it won't go searching
and find the wrong one.  But before you do that, you should try to find where
the errant one is coming from and remove whatever package installed it.

-- 
Tom Russo    KM5VY   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