LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-13-2011, 09:59 AM   #1
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Google Earth won't start on Slackware64 13.37 with multi-lib


The problem, I can not get Google Earth to start on Slackware 64 bit system. This system I upgraded from 13.1, and I have Multi-lib support installed. I followed Alien Bob's doc to install Multi-lib.

There is one nagging question I have with the upgrade. Should I have deleted the /lib directory before re-installing multi-lib? I did not, I guessed the new versions of each file would overwrite the old versions.

Now, with some investigation, I can't make the symlink called for in the README,
Quote:
ln -sf /lib/ld-linux.so.2 /lib/ld-lsb.so.3
I ran the file command, and got this:

Quote:
file ld-lsb.so.3
ld-lsb.so.3: broken symbolic link to `/lib/ld-linux.so.2'
What I don't understand, is should there be a file ld-lsb.so.3 ? or a file ld-linux.so.2 ? I thought ( from what little I understand about symlinks, ) ld-lsb.so.3 should be a real file. Is that correct? If yes, what where do I get that file from?

If I have it backwards, where do I get ld-linux.so.2 from?
 
Old 05-13-2011, 10:19 AM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
There should definitely be a file /lib/ld-linux.so.2(actually that is a symlink itself). On Slackware 13.37 I have:
Code:
lrwxrwxrwx 1 root root 10 Mar 25 14:03 /lib/ld-linux.so.2 -> ld-2.13.so*
The symlink /lib/ld-lsb.so.3 -> /lib/ld-linux.so.2 is something that you have to do yourself.

Eric
 
Old 05-13-2011, 12:22 PM   #3
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Original Poster
Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Quote:
The symlink /lib/ld-lsb.so.3 -> /lib/ld-linux.so.2 is something that you have to do yourself.
I know, I tried. From what you have said, I'm missing the file ld-linux.so.2 Where do I get that from?

I removed the broken sym link. I re-ran the command 'upgradepkg --install-new *-compat32/*.t?z' from the slackware64-compat32 directory, however ld-linux.so.2 doesn't get installed.

When the command ran, I saw the message 'package skipped, already installed' So,

where can I find ld-linux.so.2 ???

Last edited by camorri; 05-13-2011 at 12:49 PM.
 
Old 05-13-2011, 12:54 PM   #4
55020
Senior Member
 
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,307
Blog Entries: 4

Rep: Reputation: Disabled
You get ld-2.13.so from glibc-2.13_multilib-x86_64-4alien and/or glibc-solibs-2.13_multilib-x86_64-4alien. Apparently you don't have ld-2.13.so, so apparently your multilib is broken.

You should only use installpkg, upgradepkg and removepkg (or the higher level tools like slackpkg and sbopkg) to install, upgrade/reinstall and remove packages. If you only use these tools, you will never need to delete anything manually. Especially not /lib ;-)
 
Old 05-13-2011, 01:05 PM   #5
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Original Poster
Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Quote:
bash-4.1# locate ld-2.13.so
/lib/ld-2.13.so
/lib64/ld-2.13.so
/boot/initrd-tree/lib64/ld-2.13.so
I have ld-2.13.so, I just did a locate, it is there.
 
Old 05-13-2011, 03:43 PM   #6
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Original Poster
Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Well, progress of sorts. What I did was re-ran the install of compat32-tools. I then had ld-linux.so.2, which is a sym-link to ld-2.13.so. I made the sym-link as per the README for GoogleEarth.

I now see
Quote:
file /lib/ld-lsb.so.3
/lib/ld-lsb.so.3: symbolic link to `/lib/ld-linux.so.2'
If I run googleearth, it now Seg Faults.

Don't know what else to try. Your thoughts.
 
Old 05-13-2011, 04:11 PM   #7
afreitascs
Member
 
Registered: Aug 2004
Distribution: Debian
Posts: 443

Rep: Reputation: 30
Quote:
Originally Posted by camorri View Post
Well, progress of sorts. What I did was re-ran the install of compat32-tools. I then had ld-linux.so.2, which is a sym-link to ld-2.13.so. I made the sym-link as per the README for GoogleEarth.

I now see

If I run googleearth, it now Seg Faults.

Don't know what else to try. Your thoughts.
Please, you made​​:

Quote:
removepkg /var/log/packages/*-compat32-*

upgradepkg --reinstall ( Alien multilib packages )

mkdir compat32/
cd compat32/
massconvert32.sh -i (slackware directory path, the tree 32bit Slackware )
installpkg *-compat32/*.t?z
?????

good luck
 
Old 05-13-2011, 05:08 PM   #8
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095

Rep: Reputation: 7273Reputation: 7273Reputation: 7273Reputation: 7273Reputation: 7273Reputation: 7273Reputation: 7273Reputation: 7273Reputation: 7273Reputation: 7273Reputation: 7273
Quote:
Originally Posted by camorri View Post
The problem, I can not get Google Earth to start on Slackware 64 bit system. This system I upgraded from 13.1, and I have Multi-lib support installed. I followed Alien Bob's doc to install Multi-lib...
Where did you get the GoogleEarth package you are trying to run?

Once I had Slackware64 13.37 and the multilib files installed, I had trouble with the GoogleEarth package I had
previously downloaded from Google and ran on 'current.'

I went to GoogleEarth's web site and couldn't find a "generic" package, i.e., there was no longer (that I could find) a GoogleEarth.sh package, but only packages for .deb and .rpm. So, I went to SlackBuilds.org, download the script and the source, ran the script, and the resulting package installed and worked without a problem.

Just FYI.
 
Old 05-14-2011, 08:08 AM   #9
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Original Poster
Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Quote:
I went to GoogleEarth's web site and couldn't find a "generic" package, i.e., there was no longer (that I could find) a GoogleEarth.sh package, but only packages for .deb and .rpm. So, I went to SlackBuilds.org, download the script and the source, ran the script, and the resulting package installed and worked without a problem.
I got it from slackbuilds.org. It seg-faults.

Here is what is reported in dmesg.

Quote:
googleearth-bin[3083]: segfault at 729a3e4a ip 00000000f654bc96 sp 00000000ffdae708 error 6 in libGL.so.270.41.06[f64f3000+a1000]
It appears libGL.so.270.41.06 has something to do with it.
 
Old 05-14-2011, 08:33 AM   #10
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106Reputation: 8106
libGL.so.270.41.06 is part of Nvidia's binary driver which you seem to have installed. Perhaps try to install it (or a newer version) again? Make sure to answer "YES" to the question whether 32-bit driver should be installed as well.

Eric
 
Old 05-15-2011, 08:50 AM   #11
camorri
LQ 5k Club
 
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,215

Original Poster
Rep: Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849Reputation: 849
Problem solved. I re-downloaded the driver from Nvidia, re-installed it from the new download, and said YES to 32 bit driver support. This is what I had done after the upgrade. Other 32 bit apps were O.K. specifically Frostwire worked like a charm.

I'm writing this one off to purple smoke and mirrors. Why GoogleEarth seg-faulted on the first install of the Nvidia driver, and not on the -re-install, I don't know.

Thank-you to all those who helped.
 
  


Reply

Tags
solved



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Slackware64 multi-lib and Nvidia graphics? Lufbery Slackware 14 08-15-2010 03:47 PM
[SOLVED] multi-lib Slackware64 13.1 slugman Slackware 5 07-10-2010 01:40 PM
[SOLVED] Google Earth Slackware64 Multilib mlangdn Slackware 20 03-19-2010 03:35 AM
Google Earth won't start on Suse 10.3 mwrath Linux - Desktop 5 02-16-2009 06:22 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 09:49 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration