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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
64-bit GoogleEarth... Well, Almost.
Got a notice from GoogleEarth today, downloaded it and
Code:
ta-root-/usr/local/packages: GoogleEarthLinux.bin
Verifying archive integrity... All good.
Uncompressing Google Earth for GNU/Linux 6.0.0.1735..............................................................
./setup.sh: line 216: setup.data/bin/Linux/amd64/setup.gtk2: No such file or directory
./setup.sh: line 216: setup.data/bin/Linux/amd64/setup.gtk: No such file or directory
The setup program seems to have failed on amd64
Fatal error, installer failed to run at all!
I just looked at this. By changing the keep variable to 'y' instead of 'n', it keeps the installation directories instead of deleting them when it errors out. amd64 is a symlink to x86, and the files it is referencing are 32-bit binaries. The 'No such file or directory' error is just masking the problem. You still require multilib to use (or at least to install) Google Earth.
To confirm how essential multilib is, the 32-bit binaries (with no 64-bit substitute) in googleearth-data.tar:
Code:
./gpsbabel: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), not stripped
./plugins/imageformats/libqjpeg.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped
./plugins/imageformats/libqgif.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped
In fact, there are *no* 64-bit binaries at all in the file structure created by the install script. Google clearly has no plans for a pure 64-bit release of Google Earth.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
I've been looking at this too. I got rather excited at the thought of Google Earth on my 64 bit Slackware. I really miss Google Earth. Running this install like this
saves everything to the sub directory (which I first created) google-earth. When I looked at that I thought I saw amd64 and x86_64 directories under Linux but it turns out they are just links to the x86 directory. Google obviously expects the people running 64 bit to have multilib installed. Oh well. I might one day go the multilib route so I may run a few 32 bit only applications but I have stayed away from this as I think it would make maintaining my system a lot more involved (a bit of a PITA to be honest).
Last edited by bgeddy; 12-01-2010 at 04:10 PM.
Reason: spelling
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Original Poster
Rep:
Yup, it's 32-bit and they're symbolic links and that's the name of that tune. Sigh. Been out shopping and didn't get back quickly enough, sorry.
I miss it too and I've been reluctant to install Multilib (although, yeah, I am well aware that it works just fine and GoogleEarth and Adobe Reader will work that way). Just don't want to fiddle with it that badly.
./GoogleEarthLinux.bin --target /tmp/ge
cd /tmp/ge/setup.data/bin/Linux/x86/ (for 64-bit: cd /tmp/ge/setup.data/bin/Linux/x86_64/)
mv setup.gtk setup.gtk2
cd /tmp/ge
./setup.sh
Note: tested on 32-bit system only. I haven't tried this at 64-bit (pure/multilib)
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
I have tried your solution and this happened.
Code:
./GoogleEarthLinux.bin --target /tmp/ge
Creating directory /tmp/ge
Verifying archive integrity... All good.
Uncompressing Google Earth for GNU/Linux 6.0.0.1735..............................................................
./setup.sh: line 216: setup.data/bin/Linux/amd64/setup.gtk2: No such file or directory
./setup.sh: line 216: setup.data/bin/Linux/amd64/setup.gtk: No such file or directory
The setup program seems to have failed on amd64
Fatal error, installer failed to run at all!
So I went on to run the rest of your commands and got :
Code:
./setup.sh
./setup.sh: line 216: setup.data/bin/Linux/amd64/setup.gtk2: No such file or directory
Admitedly these are stupid errors and easily debuggable but I have only just tried your solution and not attempted any fault finding as of yet. Are you saying you have managed to get Google Earth to install and run a on pure 64 bit system (not multilib)? If so I am very interested in any help you can offer. Having ran "file" on the installer apps and seeing that their x86_64/amd_64 directories just link to x86 it seems to me that the installer only works with 32 bit extensions on a 64 bit system. I hope I am wrong with this!
I checked every file (using `find . -exec file {} \; | grep 64-bit`) and retrieved nothing, both for the bare install directory and when untarring the two tar archives, as shown in my post. This will never work on a pure 64-bit system -- the setup.gtk problem that may or may not have plagued the 32-bit installation is a very separate and much less serious problem than the one in this thread. The fact remains that a multilib system is required for Google Earth on a 64-bit distro.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.