How to make a pet or sfs of Google Earth 64?.

Using applications, configuring, problems
Message
Author
jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#31 Post by jamesbond »

mikeb wrote:Ok to restate... only one link is needed...BUT the link itself will vary depending on the system. A sfs made for one will fail on another for example. I believe pets can run install scripts..I assume thats the way to deal with this.

mike
No, only one link is needed. Located in /lib, ld-lsb-x86-64.so.3 should be linked to ld-linux-x86-64.so.2. This will work across all published Fatdog64 versions (and LH64 too, I believe, but I have not checked that).
FD 7 ooooooohhhhh is it coming soon? will be near highspeed internet end of workweek just putting that out there no pressure..
All in due time :wink:
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
Ted Dog
Posts: 3965
Joined: Wed 14 Sep 2005, 02:35
Location: Heart of Texas

#32 Post by Ted Dog »

should name it 007 ha ha.. :lol: really should let some of us long time tinkers preview. Since I have tricky hardware I volunteer..

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#33 Post by mikeb »

Well
ln -s ld-2.11.1.so ld-lsb-x86-64.so.3 # for Fatdog 521
ln -s ld-2.13.so ld-lsb-x86-64.so.3 # for Fatdog 631
(up to 631. In 700, the symlink must be in /lib64 - but that's another story Wink ).
led me to believe there were at least 2 possibilities...just trying to get the record straight here based on supplied information.

Mike

jamesbond
Posts: 3433
Joined: Mon 26 Feb 2007, 05:02
Location: The Blue Marble

#34 Post by jamesbond »

@mikeb,
Correct, that was my original post. But it has since been superseded this http://murga-linux.com/puppy/viewtopic. ... 852#783852 and the top post of this page - you don't need to link it directly to ld-2.11.1 or ld-2.13, instead link it to ld-linux-x86-64.so.2. And create that link in /lib (not lib64). As for Fatdog64 700 requiring another location - well, Fatdog64 700 isn't released yet so you can ignore it :wink:

@Ted Dog,
Yes planning for that, but each time I want to upload the ISO I found another bug that requires fixing ... it's like cooking popcorn in microwave. You just have to wait until the pop goes down to once or twice a second or so to know it's good to go :)
Fatdog64 forum links: [url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Latest version[/url] | [url=https://cutt.ly/ke8sn5H]Contributed packages[/url] | [url=https://cutt.ly/se8scrb]ISO builder[/url]

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#35 Post by mikeb »

Thanks for the clarification...forums make great wikis :D

mike

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

#36 Post by Eathray »

Cool...

Can we make a .sfs that will include the one link? Or not worth it?

As far as Fatdog and Lighthouse, I've never seen a pet or sfs for one that did not work in the other, especially in the 5xx series, but also the 6xx too, which I've played with a little.

Eathray

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

#37 Post by Eathray »

Note:

I mentioned Google Earth didn't like my graphics card and that I would update my driver.

Previously I was running the vesa driver because it is so compatible and performs fine with most things I do. I upgraded to the Intel i945 and ran Earth. Initially it gave a false warning as before about not supporting the card, but I set that warning not to show again, and it launched without incident. I took it for a spin, found my house, and was able to see my Jeep parked there next to my wife's Jeep, his and hers.

Seems to be working perfectly.

Eathray

gcmartin

#38 Post by gcmartin »

Is it now time to elevate these packages to the FD Repo?

Thanks for bringing this to forum attention, @Eathray.

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

#39 Post by Eathray »

Hey GC,

I would love to see it elevated to the repo's... but I'm not sure how we let people know that it needs a symlink once installed. There's not really a way to let others know from the repo's unless it's in the title.

All it seems we need is to recompile the .sfs with the symlink included, but I've never actually done a .sfs before. I've done 1 pet package, and 1 puppy remaster... which is to say, as amateur developers go, I am extremely, deeply and profoundly amateur.

But I love to learn if someone wants to lead the way...

Eathray

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

#40 Post by Eathray »

Tried to install on a second computer with an nvidia card, just wanting to see the performance... Installed the same as on my laptop which now works, but this one returned an error:

[quote]Failed to load “/opt/google/earth/free/libinput_plugin.so

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#41 Post by mikeb »

newer version of /usr/lib/libstdc++.so.6 actually.
3.4.14 or newer as it demands...

Getting it depends on the pup...

mike

User avatar
Eathray
Posts: 723
Joined: Sun 06 Sep 2009, 19:42

#42 Post by Eathray »

So I've been trying to figure out why I have the newer version of glib in one of my Fatdogs (and lighthouse) but not this other install on a different computer since it's the same version of Fatdog (520)...

It looks like in the file system, I have six entries for the new glib on my laptop, and they seem to be associated with Skype. I think when I installed Skype on Fatdog and Lighthouse on my laptop, I must have picked up the new glib as a dependency.

Is there any reason why I can't just copy the new glib file from my laptop and put it where it goes on the desktop I'm trying out? The error message seems to indicate that the system knows where to look for it, so if I manually put it there, Google Earth should just find it and use it, should it not?

Eathray

User avatar
mikeb
Posts: 11297
Joined: Thu 23 Nov 2006, 13:56

#43 Post by mikeb »

this is nothing to do with glib(c) its libstdc+++ which is a different library altogether... its for c++ based applications rather than c.

Changing glibc will do nothing for this problem.
Mike

Post Reply