32bit applications on 64bit Puppy or Quirky

A home for all kinds of Puppy related projects
Post Reply
Message
Author
slavvo67
Posts: 1610
Joined: Sat 13 Oct 2012, 02:07
Location: The other Mr. 305

32bit applications on 64bit Puppy or Quirky

#1 Post by slavvo67 »

I see a few Puppies have a 32bit sfs pet that I guess adds the basic 32bit lib files to run applications on a 64bit build. Is that it? Just looking to do the same for Quirky and I'm trying to see if there's anything in this concept I'm missing.

So do you just package a bunch of the basic 32bit lib files?

Anyone?? Bueller... Bueller....

User avatar
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#2 Post by Burn_IT »

Even in 64 bit builds there are many 32 bit processes, mainly because the 64bit ones have yet to be written and tested - even if they ever will.
"Just think of it as leaving early to avoid the rush" - T Pratchett

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

Re: 32bit applications on 64bit Puppy or Quirky

#3 Post by jamesbond »

slavvo67 wrote:I see a few Puppies have a 32bit sfs pet that I guess adds the basic 32bit lib files to run applications on a 64bit build. Is that it?
Yes, that's it really. Of course the devil is in the details, but that's it. You also need to make sure that the 64-bit kernel is compiled with support for 32-bit applications (IA32_EMULATION is enabled). This is usually the case.
So do you just package a bunch of the basic 32bit lib files?
The details:
1. You need to ensure that 32bit libraries and 64bit libraries live in different directories (many of them have same names, so you can't just dump them into the same location). Several strategy has been used in the past, depending on how your layout for your 64-bit libraries, e.g:
- 64-bit in /usr/lib64, 32-bit in /usr/lib
- 64-bit in /usr/lib, 32-bit in /usr/lib32
- 64-bit in /usr/lib64, 32-bit in /usr/lib32
- 64-bit in /usr/lib, 32-bit lib in /opt/lib
etc, you get my drift.

2. You need to have the directory containing these 32-bit libraries exposed, either via LD_LIBRARY_PATH or via /etc/ld.so.conf.

3. Some programs (e.g. GTK) load additional libraries on-demand. They usually have config files to tell them where to look for libraries. You need to have two sets of config files, one for 64-bit and one for 32-bit.

The 32-bit libs don't have to come from the same source. Here's an example:
- Fatdog64 500 - 64-bit comes from T2, 32-bit comes from Wary (T2)
- Fatdog64 600 - 64-bit comes from T2, 32-bit comes from Slacko (Slackware)
- Fatdog64 700 - 64-bit comes from LFS, 32-bit comes from Slacko (Slackware)
- Fatdog64 710 - 64-bit comes from LFS, 32-bit comes from LFS (we build both 64-bit and 32-bit libs together).

But all of them work equally well.
Bueller... Bueller....
Hehehe ... what's that? :lol:
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
Burn_IT
Posts: 3650
Joined: Sat 12 Aug 2006, 19:25
Location: Tamworth UK

#4 Post by Burn_IT »

"Just think of it as leaving early to avoid the rush" - T Pratchett

slavvo67
Posts: 1610
Joined: Sat 13 Oct 2012, 02:07
Location: The other Mr. 305

#5 Post by slavvo67 »

Thank you all for your replies. Sorry, I thought most knew Ferris Bueller's Day Off movie. A classic from what.. the 80's I think.

Trying to kick Quirky Xerus up a notch with 32 bit. Reinventing Quirky April (32 bit) as well but this question has nothing to do with the April project....

Thanks again, guys. I think that puts me off in the right direction.

Best,

Slavvo67

Post Reply