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.

Before I start the above, I should tell you that after configure runs it says the caching is enabled. Is that of any significance? I hope I can pull off the above as I have never delved in xastir that far.
Jim


_______________________________________________
Xastir mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

Reply via email to