Re: [Xastir] CallPass possible issue on 64-bit machines?
I thought I'd chime in here: I *highly* encourage all LInux users running a x64 system to *NOT* install the 32bit libraries for their respective distribution. Installing them only increases the bloat on the hard disk, doubles the sizes of your downloaded patches (gets both the 32 and 64bit versions), etc. Sure, this might mean that you will need to compile some packages to be native 64bit but when only the 32bit binary versions of a given package are posted but if you stick to 64bit only, you'll have a cleaner, leaner system in the long term. Just my $1.50 --David KI6ZHD ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] CallPass possible issue on 64-bit machines?
On Tue, 18 Dec 2012 19:48:11 -0800 Mark Cohen ma...@binaryfaith.com wrote: Try something other than Ubuntu (Linux Mint for example) ... Ubuntu sucks. :) -Mark let's be precise Ubuntu makes changes to the Debian libraries so that you are stuck with no upgrade path and have to do a reinstall. I've been involved with 2 distros over the last 7 years which both flirted with Ubuntu base and then returned to using Debian as a base (Mepis, Crunchbang) ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] CallPass possible issue on 64-bit machines?
Been dealing with Debian for near 20 years. I wouldn't go elsewhere but I do wish they'd relax their strict free software policy. That's where Linux Mint LMDE shines, in most ways. Ray vk2tv On 19/12/12 20:20, Liz wrote: On Tue, 18 Dec 2012 19:48:11 -0800 Mark Cohen ma...@binaryfaith.com wrote: Try something other than Ubuntu (Linux Mint for example) ... Ubuntu sucks. :) -Mark let's be precise Ubuntu makes changes to the Debian libraries so that you are stuck with no upgrade path and have to do a reinstall. I've been involved with 2 distros over the last 7 years which both flirted with Ubuntu base and then returned to using Debian as a base (Mepis, Crunchbang) ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] CallPass possible issue on 64-bit machines?
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.aitche...@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@aitch100-Gazelle-Professional:~$ ldd /usr/local/bin/callpass linux-vdso.so.1 = (0x7fff52bff000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f9688d6b000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f96889ac000) /lib64/ld-linux-x86-64.so.2 (0x7f9688fcb000) aitch100s76gazpro@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.aitche...@gmail.com Go Green! Print this email only when necessary. ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] CallPass possible issue on 64-bit machines?
On Tue, 18 Dec 2012, David A Aitcheson wrote: ldd /usr/local/bin/callpass shows: aitch100s76gazpro@aitch100-Gazelle-Professional:~$ ldd /usr/local/bin/callpass linux-vdso.so.1 = (0x7fff52bff000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f9688d6b000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f96889ac000) /lib64/ld-linux-x86-64.so.2 (0x7f9688fcb000) aitch100s76gazpro@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. Here's an eye-opener... The same command as you list above, but run on this 64-bit OpenSUSE-12.1 machine: $ ldd /usr/local/bin/callpass linux-vdso.so.1 = (0x7fff53fff000) libXm.so.4 = /usr/lib64/libXm.so.4 (0x7fb2a7211000) libXt.so.6 = /usr/lib64/libXt.so.6 (0x7fb2a6faa000) libX11.so.6 = /usr/lib64/libX11.so.6 (0x7fb2a6c69000) libGraphicsMagick.so.3 = /usr/lib64/libGraphicsMagick.so.3 (0x7fb2a68ae000) liblcms.so.1 = /usr/lib64/liblcms.so.1 (0x7fb2a6674000) libfreetype.so.6 = /usr/lib64/libfreetype.so.6 (0x7fb2a63e8000) libXext.so.6 = /usr/lib64/libXext.so.6 (0x7fb2a61d5000) libSM.so.6 = /usr/lib64/libSM.so.6 (0x7fb2a5fcc000) libICE.so.6 = /usr/lib64/libICE.so.6 (0x7fb2a5db) libbz2.so.1 = /lib64/libbz2.so.1 (0x7fb2a5ba1000) libz.so.1 = /lib64/libz.so.1 (0x7fb2a5989000) libm.so.6 = /lib64/libm.so.6 (0x7fb2a5732000) libgomp.so.1 = /usr/lib64/libgomp.so.1 (0x7fb2a5524000) libpthread.so.0 = /lib64/libpthread.so.0 (0x7fb2a5307000) libltdl.so.7 = /usr/lib64/libltdl.so.7 (0x7fb2a50fd000) libdb-4.8.so = /usr/lib64/libdb-4.8.so (0x7fb2a4d81000) libXpm.so.4 = /usr/lib64/libXpm.so.4 (0x7fb2a4b6f000) librt.so.1 = /lib64/librt.so.1 (0x7fb2a4967000) libXp.so.6 = /usr/lib64/libXp.so.6 (0x7fb2a475d000) libcurl.so.4 = /usr/lib64/libcurl.so.4 (0x7fb2a44fd000) libproj.so.0 = /usr/lib64/libproj.so.0 (0x7fb2a42b8000) libshp.so.1 = /usr/lib64/libshp.so.1 (0x7fb2a40af000) libpcre.so.0 = /lib64/libpcre.so.0 (0x7fb2a3e71000) libtiff.so.3 = /usr/lib64/libtiff.so.3 (0x7fb2a3c0c000) libgeotiff.so.2 = /usr/lib64/libgeotiff.so.2 (0x7fb2a39da000) libax25.so.0 = /usr/lib64/libax25.so.0 (0x7fb2a37d) libc.so.6 = /lib64/libc.so.6 (0x7fb2a344) libXmu.so.6 = /usr/lib64/libXmu.so.6 (0x7fb2a3226000) libXft.so.2 = /usr/lib64/libXft.so.2 (0x7fb2a3011000) libjpeg.so.62 = /usr/lib64/libjpeg.so.62 (0x7fb2a2dc5000) libpng14.so.14 = /usr/lib64/libpng14.so.14 (0x7fb2a2b9c000) libxcb.so.1 = /usr/lib64/libxcb.so.1 (0x7fb2a297f000) libdl.so.2 = /lib64/libdl.so.2 (0x7fb2a277b000) libuuid.so.1 = /lib64/libuuid.so.1 (0x7fb2a2576000) /lib64/ld-linux-x86-64.so.2 (0x7fb2a76dd000) libXau.so.6 = /usr/lib64/libXau.so.6 (0x7fb2a2372000) libcares.so.2 = /usr/lib64/libcares.so.2 (0x7fb2a2162000) libidn.so.11 = /usr/lib64/libidn.so.11 (0x7fb2a1f2f000) liblber-2.4.so.2 = /usr/lib64/liblber-2.4.so.2 (0x7fb2a1d2) libldap-2.4.so.2 = /usr/lib64/libldap-2.4.so.2 (0x7fb2a1ad7000) libgssapi_krb5.so.2 = /usr/lib64/libgssapi_krb5.so.2 (0x7fb2a189a000) libssl.so.1.0.0 = /lib64/libssl.so.1.0.0 (0x7fb2a163e000) libcrypto.so.1.0.0 = /lib64/libcrypto.so.1.0.0 (0x7fb2a128d000) libssh2.so.1 = /usr/lib64/libssh2.so.1 (0x7fb2a1065000) libfontconfig.so.1 = /usr/lib64/libfontconfig.so.1 (0x7fb2a0e2f000) libXrender.so.1 = /usr/lib64/libXrender.so.1 (0x7fb2a0c24000) libresolv.so.2 = /lib64/libresolv.so.2 (0x7fb2a0a0d000) libsasl2.so.2 = /usr/lib64/libsasl2.so.2 (0x7fb2a07f2000) libkrb5.so.3 = /usr/lib64/libkrb5.so.3 (0x7fb2a0524000) libk5crypto.so.3 = /usr/lib64/libk5crypto.so.3 (0x7fb2a02fb000) libcom_err.so.2 = /lib64/libcom_err.so.2 (0x7fb2a00f7000) libkrb5support.so.0 = /usr/lib64/libkrb5support.so.0 (0x7fb29feed000) libexpat.so.1 = /lib64/libexpat.so.1 (0x7fb29fcc2000) libkeyutils.so.1 = /lib64/libkeyutils.so.1 (0x7fb29fabe000) libselinux.so.1 = /lib64/libselinux.so.1 (0x7fb29f8a) That's just crazy! Somebody isn't paying a lot of attention to which prerequisites libraries actually need. Note: callpass works fine on this machine. -- Curt, WE7U.http://wetnet.net/~we7u APRS Usage Pages: http://wetnet.net/~we7u/usage.html ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] CallPass possible issue on 64-bit machines?
Good grief and I thought I had it bad, I guess i might want to consider loading an older version of Ubuntu on an older machine and taking my chances. eh? On 12/18/2012 05:37 PM, Curt, WE7U wrote: On Tue, 18 Dec 2012, David A Aitcheson wrote: ldd /usr/local/bin/callpass shows: aitch100s76gazpro@aitch100-Gazelle-Professional:~$ ldd /usr/local/bin/callpass linux-vdso.so.1 = (0x7fff52bff000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f9688d6b000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f96889ac000) /lib64/ld-linux-x86-64.so.2 (0x7f9688fcb000) aitch100s76gazpro@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. Here's an eye-opener... The same command as you list above, but run on this 64-bit OpenSUSE-12.1 machine: $ ldd /usr/local/bin/callpass linux-vdso.so.1 = (0x7fff53fff000) libXm.so.4 = /usr/lib64/libXm.so.4 (0x7fb2a7211000) libXt.so.6 = /usr/lib64/libXt.so.6 (0x7fb2a6faa000) libX11.so.6 = /usr/lib64/libX11.so.6 (0x7fb2a6c69000) libGraphicsMagick.so.3 = /usr/lib64/libGraphicsMagick.so.3 (0x7fb2a68ae000) liblcms.so.1 = /usr/lib64/liblcms.so.1 (0x7fb2a6674000) libfreetype.so.6 = /usr/lib64/libfreetype.so.6 (0x7fb2a63e8000) libXext.so.6 = /usr/lib64/libXext.so.6 (0x7fb2a61d5000) libSM.so.6 = /usr/lib64/libSM.so.6 (0x7fb2a5fcc000) libICE.so.6 = /usr/lib64/libICE.so.6 (0x7fb2a5db) libbz2.so.1 = /lib64/libbz2.so.1 (0x7fb2a5ba1000) libz.so.1 = /lib64/libz.so.1 (0x7fb2a5989000) libm.so.6 = /lib64/libm.so.6 (0x7fb2a5732000) libgomp.so.1 = /usr/lib64/libgomp.so.1 (0x7fb2a5524000) libpthread.so.0 = /lib64/libpthread.so.0 (0x7fb2a5307000) libltdl.so.7 = /usr/lib64/libltdl.so.7 (0x7fb2a50fd000) libdb-4.8.so = /usr/lib64/libdb-4.8.so (0x7fb2a4d81000) libXpm.so.4 = /usr/lib64/libXpm.so.4 (0x7fb2a4b6f000) librt.so.1 = /lib64/librt.so.1 (0x7fb2a4967000) libXp.so.6 = /usr/lib64/libXp.so.6 (0x7fb2a475d000) libcurl.so.4 = /usr/lib64/libcurl.so.4 (0x7fb2a44fd000) libproj.so.0 = /usr/lib64/libproj.so.0 (0x7fb2a42b8000) libshp.so.1 = /usr/lib64/libshp.so.1 (0x7fb2a40af000) libpcre.so.0 = /lib64/libpcre.so.0 (0x7fb2a3e71000) libtiff.so.3 = /usr/lib64/libtiff.so.3 (0x7fb2a3c0c000) libgeotiff.so.2 = /usr/lib64/libgeotiff.so.2 (0x7fb2a39da000) libax25.so.0 = /usr/lib64/libax25.so.0 (0x7fb2a37d) libc.so.6 = /lib64/libc.so.6 (0x7fb2a344) libXmu.so.6 = /usr/lib64/libXmu.so.6 (0x7fb2a3226000) libXft.so.2 = /usr/lib64/libXft.so.2 (0x7fb2a3011000) libjpeg.so.62 = /usr/lib64/libjpeg.so.62 (0x7fb2a2dc5000) libpng14.so.14 = /usr/lib64/libpng14.so.14 (0x7fb2a2b9c000) libxcb.so.1 = /usr/lib64/libxcb.so.1 (0x7fb2a297f000) libdl.so.2 = /lib64/libdl.so.2 (0x7fb2a277b000) libuuid.so.1 = /lib64/libuuid.so.1 (0x7fb2a2576000) /lib64/ld-linux-x86-64.so.2 (0x7fb2a76dd000) libXau.so.6 = /usr/lib64/libXau.so.6 (0x7fb2a2372000) libcares.so.2 = /usr/lib64/libcares.so.2 (0x7fb2a2162000) libidn.so.11 = /usr/lib64/libidn.so.11 (0x7fb2a1f2f000) liblber-2.4.so.2 = /usr/lib64/liblber-2.4.so.2 (0x7fb2a1d2) libldap-2.4.so.2 = /usr/lib64/libldap-2.4.so.2 (0x7fb2a1ad7000) libgssapi_krb5.so.2 = /usr/lib64/libgssapi_krb5.so.2 (0x7fb2a189a000) libssl.so.1.0.0 = /lib64/libssl.so.1.0.0 (0x7fb2a163e000) libcrypto.so.1.0.0 = /lib64/libcrypto.so.1.0.0 (0x7fb2a128d000) libssh2.so.1 = /usr/lib64/libssh2.so.1 (0x7fb2a1065000) libfontconfig.so.1 = /usr/lib64/libfontconfig.so.1 (0x7fb2a0e2f000) libXrender.so.1 = /usr/lib64/libXrender.so.1 (0x7fb2a0c24000) libresolv.so.2 = /lib64/libresolv.so.2 (0x7fb2a0a0d000) libsasl2.so.2 = /usr/lib64/libsasl2.so.2 (0x7fb2a07f2000) libkrb5.so.3 = /usr/lib64/libkrb5.so.3 (0x7fb2a0524000) libk5crypto.so.3 = /usr/lib64/libk5crypto.so.3 (0x7fb2a02fb000) libcom_err.so.2 = /lib64/libcom_err.so.2 (0x7fb2a00f7000) libkrb5support.so.0 = /usr/lib64/libkrb5support.so.0 (0x7fb29feed000) libexpat.so.1 = /lib64/libexpat.so.1 (0x7fb29fcc2000) libkeyutils.so.1 = /lib64/libkeyutils.so.1 (0x7fb29fabe000) libselinux.so.1 = /lib64/libselinux.so.1 (0x7fb29f8a) That's just crazy! Somebody isn't paying a lot of attention to which prerequisites libraries actually need. Note: callpass works fine on this machine. -- David A Aitcheson
Re: [Xastir] CallPass possible issue on 64-bit machines?
Try something other than Ubuntu (Linux Mint for example) ... Ubuntu sucks. :) -Mark On Dec 18, 2012, at 4:28 PM, David A Aitcheson david.aitche...@gmail.com wrote: Good grief and I thought I had it bad, I guess i might want to consider loading an older version of Ubuntu on an older machine and taking my chances. eh? On 12/18/2012 05:37 PM, Curt, WE7U wrote: On Tue, 18 Dec 2012, David A Aitcheson wrote: ldd /usr/local/bin/callpass shows: aitch100s76gazpro@aitch100-Gazelle-Professional:~$ ldd /usr/local/bin/callpass linux-vdso.so.1 = (0x7fff52bff000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f9688d6b000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f96889ac000) /lib64/ld-linux-x86-64.so.2 (0x7f9688fcb000) aitch100s76gazpro@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. Here's an eye-opener... The same command as you list above, but run on this 64-bit OpenSUSE-12.1 machine: $ ldd /usr/local/bin/callpass linux-vdso.so.1 = (0x7fff53fff000) libXm.so.4 = /usr/lib64/libXm.so.4 (0x7fb2a7211000) libXt.so.6 = /usr/lib64/libXt.so.6 (0x7fb2a6faa000) libX11.so.6 = /usr/lib64/libX11.so.6 (0x7fb2a6c69000) libGraphicsMagick.so.3 = /usr/lib64/libGraphicsMagick.so.3 (0x7fb2a68ae000) liblcms.so.1 = /usr/lib64/liblcms.so.1 (0x7fb2a6674000) libfreetype.so.6 = /usr/lib64/libfreetype.so.6 (0x7fb2a63e8000) libXext.so.6 = /usr/lib64/libXext.so.6 (0x7fb2a61d5000) libSM.so.6 = /usr/lib64/libSM.so.6 (0x7fb2a5fcc000) libICE.so.6 = /usr/lib64/libICE.so.6 (0x7fb2a5db) libbz2.so.1 = /lib64/libbz2.so.1 (0x7fb2a5ba1000) libz.so.1 = /lib64/libz.so.1 (0x7fb2a5989000) libm.so.6 = /lib64/libm.so.6 (0x7fb2a5732000) libgomp.so.1 = /usr/lib64/libgomp.so.1 (0x7fb2a5524000) libpthread.so.0 = /lib64/libpthread.so.0 (0x7fb2a5307000) libltdl.so.7 = /usr/lib64/libltdl.so.7 (0x7fb2a50fd000) libdb-4.8.so = /usr/lib64/libdb-4.8.so (0x7fb2a4d81000) libXpm.so.4 = /usr/lib64/libXpm.so.4 (0x7fb2a4b6f000) librt.so.1 = /lib64/librt.so.1 (0x7fb2a4967000) libXp.so.6 = /usr/lib64/libXp.so.6 (0x7fb2a475d000) libcurl.so.4 = /usr/lib64/libcurl.so.4 (0x7fb2a44fd000) libproj.so.0 = /usr/lib64/libproj.so.0 (0x7fb2a42b8000) libshp.so.1 = /usr/lib64/libshp.so.1 (0x7fb2a40af000) libpcre.so.0 = /lib64/libpcre.so.0 (0x7fb2a3e71000) libtiff.so.3 = /usr/lib64/libtiff.so.3 (0x7fb2a3c0c000) libgeotiff.so.2 = /usr/lib64/libgeotiff.so.2 (0x7fb2a39da000) libax25.so.0 = /usr/lib64/libax25.so.0 (0x7fb2a37d) libc.so.6 = /lib64/libc.so.6 (0x7fb2a344) libXmu.so.6 = /usr/lib64/libXmu.so.6 (0x7fb2a3226000) libXft.so.2 = /usr/lib64/libXft.so.2 (0x7fb2a3011000) libjpeg.so.62 = /usr/lib64/libjpeg.so.62 (0x7fb2a2dc5000) libpng14.so.14 = /usr/lib64/libpng14.so.14 (0x7fb2a2b9c000) libxcb.so.1 = /usr/lib64/libxcb.so.1 (0x7fb2a297f000) libdl.so.2 = /lib64/libdl.so.2 (0x7fb2a277b000) libuuid.so.1 = /lib64/libuuid.so.1 (0x7fb2a2576000) /lib64/ld-linux-x86-64.so.2 (0x7fb2a76dd000) libXau.so.6 = /usr/lib64/libXau.so.6 (0x7fb2a2372000) libcares.so.2 = /usr/lib64/libcares.so.2 (0x7fb2a2162000) libidn.so.11 = /usr/lib64/libidn.so.11 (0x7fb2a1f2f000) liblber-2.4.so.2 = /usr/lib64/liblber-2.4.so.2 (0x7fb2a1d2) libldap-2.4.so.2 = /usr/lib64/libldap-2.4.so.2 (0x7fb2a1ad7000) libgssapi_krb5.so.2 = /usr/lib64/libgssapi_krb5.so.2 (0x7fb2a189a000) libssl.so.1.0.0 = /lib64/libssl.so.1.0.0 (0x7fb2a163e000) libcrypto.so.1.0.0 = /lib64/libcrypto.so.1.0.0 (0x7fb2a128d000) libssh2.so.1 = /usr/lib64/libssh2.so.1 (0x7fb2a1065000) libfontconfig.so.1 = /usr/lib64/libfontconfig.so.1 (0x7fb2a0e2f000) libXrender.so.1 = /usr/lib64/libXrender.so.1 (0x7fb2a0c24000) libresolv.so.2 = /lib64/libresolv.so.2 (0x7fb2a0a0d000) libsasl2.so.2 = /usr/lib64/libsasl2.so.2 (0x7fb2a07f2000) libkrb5.so.3 = /usr/lib64/libkrb5.so.3 (0x7fb2a0524000) libk5crypto.so.3 = /usr/lib64/libk5crypto.so.3 (0x7fb2a02fb000) libcom_err.so.2 = /lib64/libcom_err.so.2 (0x7fb2a00f7000) libkrb5support.so.0 = /usr/lib64/libkrb5support.so.0 (0x7fb29feed000) libexpat.so.1 = /lib64/libexpat.so.1 (0x7fb29fcc2000) libkeyutils.so.1 = /lib64/libkeyutils.so.1 (0x7fb29fabe000) libselinux.so.1 = /lib64/libselinux.so.1 (0x7fb29f8a) That's just crazy! Somebody isn't paying a lot of attention
Re: [Xastir] CallPass possible issue on 64-bit machines?
On Mon, Dec 17, 2012 at 08:43:08PM -0500, we recorded a bogon-computron collision of the david.aitche...@gmail.com flavor, containing: Group, When running CallPass just now on my system I got the following error: aitch100s76gazpro@aitch100-Gazelle-Professional:~$ callpass kb3efs callpass: error while loading shared libraries: libXm.so.2: wrong ELF class: ELFCLASS64 aitch100s76gazpro@aitch100-Gazelle-Professional:~$ This system is of the following configuration: Ubuntu Release 12.04 (precise) 64-bit Kernel Linux 3.2.0-34-generic GNOME 3.4.2 Hardware Memory 3.8 GiB Processor: Intel? Core(TM) i7-2670QM CPU @ 2.20GHz x 8 Would I be correct in the hypothesis that CallPass only runs on 32-bit hardware? No, that's not correct. It runs fine on 64-bit. You have an issue with your shared libraries that you need to fix. I have a Gazelle Pro running 12.04 64-bit with the same kernel and gnome 3.4.2 as well, and callpass runs fine. Try rebuilding your Xastir and callpass from scratch. You've got a configuration problem. When I do an ldd on callpass, it is not even linked to libXm, so there is definitely something fishy with yours. Callpass is so simple it shouldn't be getting linked with *any* X libraries. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236http://kevan.org/brain.cgi?DDTNM echo prpv_a'rfg_cnf_har_cvcr | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] CallPass possible issue on 64-bit machines?
You're just missing the 32 bit libraries. Install those and things should work normally again. 64 bit hardware will run 32 bit programs just fine, it's the OS that's complaining. From: David A Aitcheson david.aitche...@gmail.com To: xastir@lists.xastir.org Sent: Monday, December 17, 2012 5:43 PM Subject: [Xastir] CallPass possible issue on 64-bit machines? Group, When running CallPass just now on my system I got the following error: aitch100s76gazpro@aitch100-Gazelle-Professional:~$ callpass kb3efs callpass: error while loading shared libraries: libXm.so.2: wrong ELF class: ELFCLASS64 aitch100s76gazpro@aitch100-Gazelle-Professional:~$ This system is of the following configuration: Ubuntu Release 12.04 (precise) 64-bit Kernel Linux 3.2.0-34-generic GNOME 3.4.2 Hardware Memory 3.8 GiB Processor: Intel® Core(TM) i7-2670QM CPU @ 2.20GHz x 8 Would I be correct in the hypothesis that CallPass only runs on 32-bit hardware? TNX 73 Dave - KB3EFS -- David A Aitcheson david.aitche...@gmail.com Go Green! Print this email only when necessary. ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] CallPass possible issue on 64-bit machines?
On Mon, Dec 17, 2012 at 07:32:08PM -0800, we recorded a bogon-computron collision of the kf4...@yahoo.com flavor, containing: You're just missing the 32 bit libraries.? Install those and things should work normally again.? 64 bit hardware will run 32 bit programs just fine, it's the OS that's complaining. That can't be the issue, unless David is using a 32-bit build of Xastir on his 64-bit machine. But even then, callpass should not even depend on libXm. There's something really fishy going on with his set up. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236http://kevan.org/brain.cgi?DDTNM echo prpv_a'rfg_cnf_har_cvcr | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] CallPass possible issue on 64-bit machines?
On 12/17/2012 11:41 PM, Tom Russo wrote: On Mon, Dec 17, 2012 at 07:32:08PM -0800, we recorded a bogon-computron collision of the kf4...@yahoo.com flavor, containing: You're just missing the 32 bit libraries.? Install those and things should work normally again.? 64 bit hardware will run 32 bit programs just fine, it's the OS that's complaining. That can't be the issue, unless David is using a 32-bit build of Xastir on his 64-bit machine. Hmmm that may be... 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 think I am going to move my Xastir off this laptop to a 32-bit laptop that needs commercial AC 24x7 or better yet to a system that has a serial port for linking to a TNC so it can also be RF-aware. I am really not worried about fixing it on this machine as I need to dedicate this machine to work now that college is finished with me. -- David A Aitcheson david.aitche...@gmail.com Go Green! Print this email only when necessary. ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] CallPass possible issue on 64-bit machines?
On Mon, 17 Dec 2012, David A Aitcheson wrote: Would I be correct in the hypothesis that CallPass only runs on 32-bit hardware? Nope. I'm running it on 64-bit OpenSUSE-12.1. -- Curt, WE7U.http://wetnet.net/~we7u U.S. Weather Alerts: Firenet.us, port 14580, filter t/n e/WE7U-WX ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] CallPass possible issue on 64-bit machines?
On Tue, Dec 18, 2012 at 12:09:35AM -0500, we recorded a bogon-computron collision of the david.aitche...@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? -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236http://kevan.org/brain.cgi?DDTNM echo prpv_a'rfg_cnf_har_cvcr | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] ___ Xastir mailing list Xastir@lists.xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
