[Xastir] Xastir for MacOSX "Unresolved inheritance operation" solved?

[George Moltz]

All interested,

Sorry for creating a new thread.  Also pardon if this was already posted.
 (I get the digest version of the list).

This was a fun one.  I think I've figured it out.  This worked for me, YMMV,
proceed at your own risk, etc.

I was getting this "Unresolved inheritance operation" as well. I use
Macports for the Xastir prerequisites and compile Xastir on my own.  First,
I updated my version of Xquartz (
http://xquartz.macosforge.org/trac/wiki/X112.3.2.1) but this didn't help.  I
mention it here in case this did actually end up being part of the problem.
 Furthermore, I found out that there was an update to the lesstif portfile
for the Macports project recently; this is documented here: (
http://trac.macports.org/changeset/45603/trunk/dports/x11/lesstif/Portfile).
 It looks like the Macports folks, in order to resolve some ongoing problems
with X11 dependencies, have stopped linking against the X11 libraries given
to us in /usr/X11/lib.  Instead, they are starting to link against their own
libraries in /opt/local/lib.  The Macports lesstif install has dependencies
which use several of these libraries; what was happening most likely was
that they were built against the libraries in /opt/local/lib, and Xastir was
getting linked against /usr/X11/lib.


****************
Here's how I fixed it.

We can force the lesstif dependencies to link against the system's X11
libraries using the "system_x11" variant.  There isn't actually a
"system_x11" variant for lesstif, but from what I understand about Macports,
this flag is passed down to the dependencies.  To do this, you should
probably uninstall the lesstif port and all its dependencies.

# You should probably uninstall lesstif and all its dependencies.
# I just uninstalled everything with: sudo port -p uninstall
--follow-dependents installed
# Then do:
sudo port install lesstif +system_x11
# configure, make, and make install xastir.

*****************

I haven't tried adding in other libraries (gdal, ImageMagick, etc).  I don't
expect any problems with those packages as I don't think they have changed
for me.

The above is likely not the most elegant solution if you are using Macports
for other things.  I don't know enough about building Xastir to know if this
can be worked around from that end.  I also tried running configure with
"--x-includes=/opt/local/include/X11 --x-libraries=/opt/local/lib/X11
--prefix=/opt/local" and still got the error.  Maybe I am missing something
here and haven't set something quite right to have it work this way.



Feel free to correct me.  I hope this helps.


Regards,
George
K4ET