[Xastir] CallPass possible issue on 64-bit machines?

David A Aitcheson david.aitcheson at gmail.com
Tue Dec 18 01:37:35 EST 2012


On 12/18/2012 12:35 AM, Tom Russo wrote:
> On Tue, Dec 18, 2012 at 12:09:35AM -0500, we recorded a bogon-computron collision of the <david.aitcheson at gmail.com> flavor, containing:
>> On 12/17/2012 11:41 PM, Tom Russo wrote:
>>
>>> But even then, callpass should not even depend on libXm.  There's something 
>>> really fishy going on with his set up.
>> Well... I did dump Unity and load Gnome...
> I also dumped Unity (ugh) and use Gnome.  I have the same System 76 Gazelle Pro 
> machine you do, running the same OS in 64-bit.  Xastir and callpass  run 
> fine.  There must be a problem with how your Xastir build was done.  Did you 
> follow the Ubuntu Installation Notes on the wiki?
>
> The fact that you're running Gnome should matter not one whit.  The binary
> of callpass wouldn't suddenly depend on libXm just because of that.  callpass
> isn't a graphical program, and should not depend on any X-related libraries.
>
> What does "ldd /usr/local/bin/callpass" show?

If I recall I did a CVS checkout for the initial install on this machine
and started everything from scratch.

"ldd /usr/local/bin/callpass" shows: 


> aitch100s76gazpro at aitch100-Gazelle-Professional:~$ ldd
> /usr/local/bin/callpass
>     linux-vdso.so.1 =>  (0x00007fff52bff000)
>     libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x00007f9688d6b000)
>     libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f96889ac000)
>     /lib64/ld-linux-x86-64.so.2 (0x00007f9688fcb000)
> aitch100s76gazpro at aitch100-Gazelle-Professional:~$

Which is making me think I need to back up things in a major way and do
a total wipe and reload of the entire OS.

-- 
David A Aitcheson david.aitcheson at gmail.com Go Green! Print this email
only when necessary.



More information about the Xastir mailing list