[Xastir] compile failure?

vic ke4lkq at doramefa.us
Sat Jan 27 22:41:14 EST 2007 


Sorry about that, now what is wrong with this???

vic at linuxvid:~> locate libXm.so
/usr/X11R6/lib/libXm.so
/usr/X11R6/lib/libXm.so.3
/usr/X11R6/lib/libXm.so.3.0.3

vic at linuxvid:~> ldd /usr/X11R6/lib/libXm.so
ldd: /usr/X11R6/lib/libXm.so: No such file or directory
vic at linuxvid:~>


Same answer...I know the problem with xastir has gone away since your code change today,
but this output from the ldd command buffalos me...

I don't want to beat this to death, but could you help me find this problem??

Thanks
Vic




On Sat, 27 Jan 2007 17:21:36 -0700
Tom Russo <russo at bogodyn.org> wrote:

> On Sat, Jan 27, 2007 at 05:26:09PM -0500, we recorded a bogon-computron collision of the <ke4lkq at doramefa.us> flavor, containing:
> > 
> > 
> > 3.I un #ed the line in configure.ac as you suggested
> >   ./bootstrap.sh
> >   ./configure
> >   make
> >   The executable works again....
> 
> I've undone the change in the repository, so you should not have to do this
> again.
> 
> > 4.  Now for libXm.so , I did a 
> >    
> >    linuxvid:/home/vic # ldd /usr/lib/libXm.so
> >    ldd: /usr/lib/libXm.so: No such file or directory
> >    linuxvid:/home/vic #
> > 
> >  Strange...??  So I did a 
> 
> Nah.  Just that Ubuntu (what I have) puts the X libraries in a different spot
> than your Suse system does. 
> 
> > linuxvid:/home/vic # locate libXm.so
> >    /usr/X11R6/lib/libXm.so
> >    /usr/X11R6/lib/libXm.so.3
> >    /usr/X11R6/lib/libXm.so.3.0.3
> >    linuxvid:/home/vic #
> >  
> >  Then...
> >   
> >    linuxvid:/home/vic # ldd /usr/X11R6/libXm.so
> >    ldd: /usr/X11R6/libXm.so: No such file or directory
> >    linuxvid:/home/vic #
> 
> Jeremy already pointed this out: You typed in "/usr/X11R6/libXm.so" and locate 
> said it was in /usr/X11R6/lib/libXm.so -- you missed a "lib" there the second 
> time.
> 
> I'm still curious what it'll say.
> 
> > 
> >   Do you know what's happening here.... I sure don't
> >  Whar blows me away is that ldd does not see libXm.so !
> > 
> >   But like I said above the compile works with that particular line in configure.ac
> >  uncommentd...
> >  
> >  Let me know what and how to give you any additional info that you may want for this...
> 
> Nah.  I'll just chalk it up to a mistake to have tried to get rid of the
> probe.  The probe's back and this problem won't surface for anyone else.
> 
> > On Sat, 27 Jan 2007 11:47:32 -0700
> > Tom Russo <russo at bogodyn.org> wrote:
> > 
> > 
> > > > > 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).
> > > 
> > > I have re-enabled the check for Xp in the configure script and committed the
> > > change, since it is necessary on at least one type of system.
> > > 
> > > You can cvs update and should be back up and running.
> > > 
> > > It would be nice if we didn't have to do this explicit link for all systems,
> > > but I can't think of any quick way to probe for whether it's necessary or
> > > not through autoconf --- I'm sure there's a way, but re-enabling the global
> > > test is quick and painless.
> > > 
> > > I had disabled it in the first place because it had misled a user into 
> > > downloading a package he didn't need (development headers in libxp-dev), but 
> > > libxp certainly is needed by motif.  Most systems seem satisfy this dependency
> > > without us explicitly linking -lXp, but there you have 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
> > > _______________________________________________
> > > Xastir mailing list
> > > Xastir at xastir.org
> > > http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
> 
> -- 
> 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
> _______________________________________________
> Xastir mailing list
> Xastir at xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

More information about the Xastir mailing list