LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Google Earth will not run 13.37 64 bit and Multi-lib (https://www.linuxquestions.org/questions/slackware-14/google-earth-will-not-run-13-37-64-bit-and-multi-lib-889359/)

camorri 07-01-2011 06:23 AM

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

How do I fix this?

I followed the instructions here -->http://connie.slackware.com/~alien/multilib/ to install multi-lib ( the fast track ).

dolphin77 07-01-2011 06:30 AM

Working fine here. Slackware64 with multilib

Code:

ls -l /lib/ld-*
-rwxr-xr-x 1 root root 134937 Май 25 04:08 /lib/ld-2.13.so*
lrwxrwxrwx 1 root root    10 Май 26 11:06 /lib/ld-linux.so.2 -> ld-2.13.so*
lrwxrwxrwx 1 root root    18 Июн  2 17:31 /lib/ld-lsb.so.3 -> /lib/ld-linux.so.2*

Code:

grep ld-2.13.so /var/adm/packages/*
/var/adm/packages/glibc-2.13_multilib-x86_64-5alien:lib/ld-2.13.so
/var/adm/packages/glibc-2.13_multilib-x86_64-5alien:lib64/incoming/ld-2.13.so
/var/adm/packages/glibc-solibs-2.13_multilib-x86_64-5alien:lib/ld-2.13.so
/var/adm/packages/glibc-solibs-2.13_multilib-x86_64-5alien:lib64/incoming/ld-2.13.so


camorri 07-01-2011 07:52 AM

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?

dolphin77 07-01-2011 08:34 AM

it looks like you didn't upgrade glibc and glibc-solibs with appropriate _multilib packages from Alien Bob.

I would advise you to read http://connie.slackware.com/~alien/multilib/README

There are step by step instructions there on how to properly update your system to become multilib

camorri 07-01-2011 08:46 AM

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
This is what shows, for the .txz files.

Quote:

ls *.txz
gcc-4.5.2_multilib-x86_64-2alien.txz glibc-2.13_multilib-x86_64-4alien.txz
gcc-g++-4.5.2_multilib-x86_64-2alien.txz glibc-i18n-2.13_multilib-x86_64-4alien.txz
gcc-gfortran-4.5.2_multilib-x86_64-2alien.txz glibc-profile-2.13_multilib-x86_64-4alien.txz
gcc-gnat-4.5.2_multilib-x86_64-2alien.txz glibc-solibs-2.13_multilib-x86_64-4alien.txz
gcc-java-4.5.2_multilib-x86_64-2alien.txz glibc-zoneinfo-2.13_multilib-noarch-4alien.txz
gcc-objc-4.5.2_multilib-x86_64-2alien.txz
I ran this command
Quote:

upgradepkg --reinstall --install-new *.t?z
to install the gcc and glibc stuff. I don't understand what I did wrong.

SeRi@lDiE 07-01-2011 09:11 AM

camorri,

Look at my post here for some pointers on the issues I also ran in too.

http://www.linuxquestions.org/questi...-issue-888765/

I would also advice to uninstall your current multilib pkgs and let the scripts from Sebastien do the work.

You will need multilib and compat32 from

http://multilibpkg.sourceforge.net/
http://compat32pkg.sourceforge.net/

and look at this post for instructions:


http://www.linuxquestions.org/questi...7/#post4310982

Note: Change the version from 13.1 to 13.37 in your case. It worked for me :)
Good Luck

slackass 07-01-2011 09:14 AM

Did you re-install the graphics card driver after you went multi-lib?

SeRi@lDiE 07-01-2011 09:20 AM

Quote:

Originally Posted by slackass (Post 4401385)
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.

camorri 07-01-2011 09:35 AM

Quote:

Did you re-install the graphics card driver after you went multi-lib?
Yes. I think I did the Nvidia driver after the multi-lib install.

slackass 07-01-2011 10:10 AM

Quote:

Originally Posted by camorri (Post 4401407)
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. :D
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.

SeRi@lDiE 07-01-2011 10:11 AM

Quote:

Originally Posted by slackass (Post 4401444)
Beggin' yer pardon, but “I think” has got me into a lot of trouble in the past. :D
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.

That I agree with :)

camorri 07-02-2011 07:15 PM

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.

SeRi@lDiE 07-02-2011 11:14 PM

Quote:

Originally Posted by camorri (Post 4402909)
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.

You can do:

removepkg /var/log/packages/*compat32*

SeRi@lDiE 07-02-2011 11:23 PM

Look at this post.

camorri 07-03-2011 08:05 AM

Could you post the link? I would be happy to look at it.

Thank-you in advance.

phenixia2003 07-03-2011 09:34 AM

Hello,

Quote:

Originally Posted by camorri (Post 4402909)
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.

You can do this in any order.

Quote:

Originally Posted by camorri (Post 4402909)
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.

If you proceed this way, you're going to break your system (!)

As you have downloaded (and installed) compat32pkg and multilibpkg, you can safely remove whole of the multilib as below :

Code:

su
password:
$ multilibpkg --uninstall @WorldWide-13.37

multilibpkg ver. 1.1.110412 (stable)
(WARNING) You're using multilibpkg in mode --uninstall, while the system is not                             
(WARNING) in run level 1: current runlevel is (3).

Do you want to continue (Y/N) ? Y
...

$ compat32pkg --remove all

compat32pkg ver. 1.4.110408 (stable)
...

Notes:
1. multilibpkg --uninstall @WorldWide-13.37

This will uninstall the 64-bit part of the multilib (ie the packages gcc*,glibc* and compat32-tools
from Eric). This is a two step process. 1) the installed multilib version of gcc* and glibc* are superseded
by their 64-bit pure counterpart available onto the selected Slackware-64 mirror. 2) The installed packages
of the '64-bit part of the multilib' which have no 64-bit pure counterpart are removed.


2. compat32pkg --remove all
This will remove all the installed compat32 packages.



Cheers.

--
SeB

camorri 07-03-2011 12:06 PM

Thank-you, I will give it a go, and post back.

camorri 07-04-2011 01:12 PM

An update. I removed the compat32 packages, and the multilib packages. I installed the two tools at these links; I used the two tools to re-install multilib and compat layers. All went well, although it did take some time to install the multilib packages.

I then re-installed the Nvidia driver, as instructed. I made the symlink that is called for in the README file for GoogleEarth. The program now launches.

Last problem, now the globe does not show up. I get the frame, the panel on the left side, but no Earth. It remains a white hole. I tried booting, that has made no difference.

If I click on the Google Maps option, they show up as normal.

So, progress, but its not working correctly, yet.

camorri 07-04-2011 01:34 PM

I logged out of XFCE with compiz. Logged in using KDE, Google Earth worked. Started compiz, it still worked. Logged out, back in with XFCE, no compiz, and Google Earth worked. Started compiz, Google Earth still worked.

I have no idea why I saw the white hole. Its gone, and all is well.

Thank-you to all those who responded, and helped.


All times are GMT -5. The time now is 10:30 AM.