Re: Urgent Help Is needed, PLEASE
On Thursday 28 June 2007 09:38:16 Danny Tiberman wrote: Hello there, I have installed debian etch 4 every is runnning fine BUT i am trying to run a program I get : error while loading shared libraries: libtk8.4.so: cannot open object file: no such file or directory but the file is there under /usr/lib and the package is installed (dpkg -l shows the program) WHAT am I missing ??? what is wrong ? You might me missing the package containing libtk8.4.so Go to the following page http://www.debian.org/distrib/packages And Search the contents of packages libtk8.4.so It will show you the following package tk8.4-dev which you have to install. If you are running a Debian program. Then please report it as a bug because then it is missing dependencies (and it shouldn't use development library anyway). Hope it helps. Gudjon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Urgent Help Is needed, PLEASE
On Thursday 28 June 2007 08:38, Danny Tiberman wrote: Hello there, I have installed debian etch 4 every is runnning fine BUT i am trying to run a program I get : error while loading shared libraries: libtk8.4.so: cannot open object file: no such file or directory but the file is there under /usr/lib and the package is installed (dpkg -l shows the program) WHAT am I missing ??? what is wrong ? Maybe it's looking for a 32-bit version of the tk library. Did you compile the program yourself from source in your 64-bit environment? Did you run `ldconfig` ? Try running `ldd` on the binary, which lists what libraries it uses, and see what it says. Especially note the size of the hex numbers it reports. If they are 16 hex digits long, it's a 64-bit binary; if they are 8 hex digits long, it's 32-bit. Sometimes packages in Sid are just broken. You should be able to download the Etch or Lenny source and build that, though. -- AJS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AMD 64 X2
On Wed, Jun 27, 2007 at 01:09:02PM -0400, Lennart Sorensen wrote: It appears though that none of the mobile X2's have Pacifica, which I find somewhat surprising. If Ed in this thread is correct that the svm flag in /proc/cpuinfo indicates Pacifica, then the Turion64 X2 TL-52 (1.6Ghz) has it (also there is a flag in the bios on this machine). -- When you do things right, people won't be sure you've done anything at all. Daniel Tryba -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AMD 64 X2
On Thu, Jun 28, 2007 at 04:51:17PM +0200, Daniel Tryba wrote: If Ed in this thread is correct that the svm flag in /proc/cpuinfo indicates Pacifica, then the Turion64 X2 TL-52 (1.6Ghz) has it (also there is a flag in the bios on this machine). Oh right. I forgot they went from Mobile Athlon 64 to Turion 64. It appears from what I can find that all Turion 64 X2's have virtualization (some of the none X2's have it too, but not all of them). -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AMD 64 X2
Lennart Sorensen wrote: On Thu, Jun 28, 2007 at 04:51:17PM +0200, Daniel Tryba wrote: If Ed in this thread is correct that the svm flag in /proc/cpuinfo indicates Pacifica, then the Turion64 X2 TL-52 (1.6Ghz) has it (also there is a flag in the bios on this machine). Oh right. I forgot they went from Mobile Athlon 64 to Turion 64. It appears from what I can find that all Turion 64 X2's have virtualization (some of the none X2's have it too, but not all of them). -- Len Sorensen Yes ... I looked at Turion 64 dual-core laptops briefly before buying the desktop Athlon64 X2. There were some Turion 64 dual cores without the virtualization assist, but I think they all have it now. The main reason I didn't get a laptop is that I wanted a reasonable price for 4 GB of RAM and a fast hard drive, not because of the processors. :) Besides, I think my next laptop will be a Mac because that's what most of the Ruby geeks use. ;) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
