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

Message

mikeb · #21 Post by **mikeb** » Tue 17 Jun 2014, 16:18

Last item... is it possible for us to build a .sfs that includes the sym-link(s) needed?

well the snag is that would suggest haing one symlink pointing to 2 potential files and thats not allowed as such. That does not include what to do if a further name change pops up with releases....seems like a situation that needs a more generic solution than just making a particular package work.

It would involve some sort of install script...pets have that option and the sfs loader does in some manner but both are out of my domain.

I am sure someone will leap in and do the do...

Without opengl acceleration working it will indeed run like cold custard...not sure what the puppy arrangements are now...used to be the xorg hi package or proprietary driver.

mike

jamesbond · #22 Post by **jamesbond** » Tue 17 Jun 2014, 18:26

There is only one symlink required. It should point to "ld-linux-x86-64.so.2". Create the symlink in /lib (not /lib64). "ln -s ld-linux-x86-64.so.2 ld-lsb-x86-64.so.3". And that should work for all Fatdog versions (up to 631. In 700, the symlink must be in /lib64 - but that's another story

).

mikeb · #23 Post by **mikeb** » Tue 17 Jun 2014, 18:36

one symlink but to 3 possible places depending on puppy release..I believe that's the problem with a one package does all approach.

mike

Ted Dog · #24 Post by **Ted Dog** » Tue 17 Jun 2014, 18:38

FD 7 ooooooohhhhh is it coming soon? will be near highspeed internet end of workweek just putting that out there no pressure..

neerajkolte · #25 Post by **neerajkolte** » Wed 18 Jun 2014, 13:35

FD 700 ???
Nice.

- Neeraj

gcmartin · #26 Post by **gcmartin** » Wed 18 Jun 2014, 18:03

Hello @Eathray

I am not any authority, but, I ask:

With features unique to PETs, can/cannot a feature of PET run a script that determines which 64bit distro installing to, and sets the symbolic-link proper?

Here to help

Eathray · #27 Post by **Eathray** » Wed 18 Jun 2014, 19:19

My thought is similar, GC, although I wasn't thinking a script.

A little confusion... James is saying only one symlink required which leads to ld-linux-x86-64.so.2. Mike I think is saying the link could originate from one of several libs, ld-2.11.1.so or ld-2.13.so. I have the latter of the two. Only one of these would be used on any given system as I think James indicates, but if both were present... it wouldn't matter which of the two starting libs were picked up... so... two syms pointing to one file and the system will decide which one it wants to use based on which of the two libs it has as a starting point...?

Is that clear and correct? I only have the one symlink from ld-2.13.so to ld-linux-x86-64.so.2 which works, but I'm not sure how you link the other starting lib to the final if it's not present. I guess there needs to be a script to tell the system to look for either/or in order to have a pet/sfs that doesn't need a symlink afterword... or there has to be more than one pet/sfs based on which libs you have...

Or can a pet/sfs carry its own starting lib that it will prefer?

I'm just thinking outloud... maybe it's not that big of a deal to add the symlink after the fact so long as future users know about it... It's always hard for newbies to find those little details.

What do you guys say?

I can call this thread solved, because there are now adequate instructions to install from a .deb package that James gave, and there is the .sfs package Mike made, and there is documented the symlink that needs to be made. I'm not sure future searchers will easily find the info but it's here if they find and read the thread.

Suggestions? Good enough? Call it Solved?

Eathray

mikeb · #28 Post by **mikeb** » Wed 18 Jun 2014, 20:05

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

neerajkolte · #29 Post by **neerajkolte** » Thu 19 Jun 2014, 16:10

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

An Install script which will detect puppy type and do changes accordingly.... Hmmmm...
Sounds tempting, will make single pet run on all puppies, one expansive repo for all puppies. (I am dreaming for future again

)
But it will demand quite good knowledge of how different puppies works and their not so obvious differences, slacko based, debian, t2, 32bit, 64bit........
Is it even remotely possible?

mikeb · #30 Post by **mikeb** » Thu 19 Jun 2014, 17:38

well it only seems to affect the 64 bit varieties of which there are 2 I believe... Its not something that normally happens...it may only be with google earth for that matter.

mike

jamesbond · #31 Post by **jamesbond** » Fri 20 Jun 2014, 03:27

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

Ted Dog · #32 Post by **Ted Dog** » Fri 20 Jun 2014, 04:09

should name it 007 ha ha..

really should let some of us long time tinkers preview. Since I have tricky hardware I volunteer..

mikeb · #33 Post by **mikeb** » Fri 20 Jun 2014, 07:36

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 · #34 Post by **jamesbond** » Fri 20 Jun 2014, 10:06

@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

@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

mikeb · #35 Post by **mikeb** » Fri 20 Jun 2014, 10:36

Thanks for the clarification...forums make great wikis

mike

Eathray · #36 Post by **Eathray** » Fri 20 Jun 2014, 13:47

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

Eathray · #37 Post by **Eathray** » Fri 20 Jun 2014, 15:28

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** » Fri 20 Jun 2014, 16:02

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

Thanks for bringing this to forum attention, @Eathray.

Eathray · #39 Post by **Eathray** » Fri 20 Jun 2014, 16:11

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

Eathray · #40 Post by **Eathray** » Fri 20 Jun 2014, 19:33

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

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

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