[Xastir] compile failure?

[Tom Russo]

On Sat, Jan 27, 2007 at 10:51:49AM -0700, we recorded a bogon-computron collision of the <russo at bogodyn.org> flavor, containing:
> On Sat, Jan 27, 2007 at 12:43:47PM -0500, we recorded a bogon-computron collision of the <ke4lkq at doramefa.us> flavor, containing:
> > 
> > 
> > To whom it may concern......
> > 
> > CVS download this morning results in this:  see below the tail end of the compile process...
> > Maybe I need to change something, or should I just wait??
> > This just showed up today...
> 
> Hmmmm.
> 
> What linux system are you running on?
> 
> Just the other day I disabled configure's check for the X Printing Extension
> because it seemed that Xastir wasn't using it --- xastir doesn't make any
> Xp calls itself and on most systems it seems that leaving out Xp causes no
> problem.
> 
> Apparently your Motif library is using it and so xastir has an indirect 
> dependence on the Xp library that other systems do not have.  It's been that
> way for a few days and most folks have checked in to say that there has been
> no problem.
> 
> Please try looking at configure.ac at around line 113 for the following:
> # TVR: commented this out.  It appears that XpGetDocumentData is not used
> # *anywhere* in Xastir, and the fact that this is being probed for has 
> # confused at least one user into thinking he needed to install the X Printing
> # Extension library when it was completely unnecessary.
> # AC_CHECK_LIB([Xp], [XpGetDocumentData]) 
> 
> Remove the "# " from the last line of that and re-run bootstrap.  That should
> cause the Xp library to be linked in again when you re-configure and make.
> 
> Please let us know what system you're on and what motif library you're using.
> It's possible I need to re-enable that test, but it would be nice to do so 
> only on systems that have Motif libraries with this dependence (otherwise
> we're linking in stuff that isn't necessary).

What is odd, though, is that the Xm shared library should have its dependencies
resolved by the dynamic loader, not by requiring us to link in libXp directly.
On one of my systems libXm.so has a dependency on libXp.so, but xastir 
still builds without the explicit -lXp.

Perhaps your system is using static-linked libXm.a instead of shared libraries?
Please let me know what 
  ldd /usr/lib/libXm.so
says.

-- 
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