[SOLVED] Google Earth will not run 13.37 64 bit and Multi-lib
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.1, 14.2
Posts: 5,270
Rep:
Google Earth will not run 13.37 64 bit and Multi-lib
I have installed Google Earth from SlackBuilds. It will not start. The README states you have to make a sym link
Quote:
ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3
As far as I know, the target has to exist, it does not on my system for what ever reason I can not determine. A few commands shows:
Quote:
bash-4.1# ls -l /lib/ld-linux.so.2
ls: cannot access /lib/ld-linux.so.2: No such file or directory
bash-4.1# ls -l /lib/ld-lsb.so.3
ls: cannot access /lib/ld-lsb.so.3: No such file or directory
bash-4.1# updatedb
bash-4.1# locate ld-lsb.so.*
/boot/initrd-tree/lib/ld-lsb.so.3
bash-4.1# file /boot/initrd-tree/lib/ld-lsb.so.3
/boot/initrd-tree/lib/ld-lsb.so.3: broken symbolic link to `/lib/ld-linux.so.2'
I did a removepkg for the compat32, and re-installed, and still do not have /lib/ld-lsb.so.3
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.1, 14.2
Posts: 5,270
Original Poster
Rep:
My system shows:
Quote:
ls -l /lib/ld-*
/bin/ls: cannot access /lib/ld-*: No such file or directory
grep ld-2.13.so /var/adm/packages/*
/var/adm/packages/glibc-2.13-x86_64-4:lib64/incoming/ld-2.13.so
/var/adm/packages/glibc-solibs-2.13-x86_64-4:lib64/incoming/ld-2.13.so
So I know something is wrong. I don't understand how to fix it. Can someone advise?
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.1, 14.2
Posts: 5,270
Original Poster
Rep:
Those are the instructions I followed. Unfortunately, I must have messed something up. I have gone around this thing for a long time, I guess I don't see the error in my way.
I have the solibs along with the other packages.
Quote:
ls *solibs*
glibc-solibs-2.13_multilib-x86_64-4alien.lst glibc-solibs-2.13_multilib-x86_64-4alien.txz
glibc-solibs-2.13_multilib-x86_64-4alien.meta glibc-solibs-2.13_multilib-x86_64-4alien.txz.asc
glibc-solibs-2.13_multilib-x86_64-4alien.txt glibc-solibs-2.13_multilib-x86_64-4alien.txz.md5
Did you re-install the graphics card driver after you went multi-lib?
Thats only if he is running proprietary drives such as nvidia.... I dont think he has mention that he is using any type of specific driver.... And if he all ready installed the driver and chose to install 32bit compatibility libs at the time of install than he should be fine. In my case I had a bad install.
Yes. I think I did the Nvidia driver after the multi-lib install.
Beggin' yer pardon, but “I think” has got me into a lot of trouble in the past.
If your not sure I'd reinstall the driver just so that can be eliminated. I done this same little boo boo more than once. The Nvidia driver must go in after the multi-libs.
Beggin' yer pardon, but “I think” has got me into a lot of trouble in the past.
If your not sure I'd reinstall the driver just so that can be eliminated. I done this same little boo boo more than once. The Nvidia driver must go in after the multi-libs.
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 14.1, 14.2
Posts: 5,270
Original Poster
Rep:
I have some concerns on the correct way to remove the multi-lib installation I have now.
Does it matter which packages I remove first? I suspect I should remove the compat32 layer first, and then the 64 bit layer next.
I'm concerned that removing the 64 bit code will leave the system broken, if I use 'removepkg *.t?z in the directory where I downloaded the gcc and glibc packages.
I have some concerns on the correct way to remove the multi-lib installation I have now.
Does it matter which packages I remove first? I suspect I should remove the compat32 layer first, and then the 64 bit layer next.
I'm concerned that removing the 64 bit code will leave the system broken, if I use 'removepkg *.t?z in the directory where I downloaded the gcc and glibc packages.
Could someone guide me here?
I have installed the two packages at these links.
I will re-install the nvidia driver after I have used the above tools to install the 64 bit and 32 bit layers.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
