F96-CE3: 32bit compatibility SFS?

[mow9902]

Is there a 32bit-compatibility-fossa64.sfs for F96 ...or should one just use the file from F95?

[rockedge]

@mow9902 Interesting question! I would try the v95 version and see if it works.

I am going to do some more testing as well

[mow9902]

@rockedge

The F95 compatibility sfs seems to load fine ...but the system library paths are not updated to include the extra 32bit libraries which it generates ie
/usr/lib/i386-linux-gnu
/lib/i386-linux-gnu

If I manually add these libraries into the search path with a 'wrapper' script then my 32bit apps (at least those I've tested) seem to load normally. Obviously it would be a pain to have to do this for each app, so I'm hoping there is a file somewhere which can be updated to automatically add these libraries to the system search paths.

[mikeslr]

Initial questions: Why do you think you need to run 32-bit applications/which applications?

Peebee's 32bit Compatibility SFS, https://www.forum.puppylinux.com/viewto ... 294#p78294 may work. Note that it is not recommended for "VoidPup64 due to its lib structure". That may also be the case with fossapup64_9.5's 32bit Compatibility SFS.

What has happened is referred to as the 'usr-merge' rule. In the past binaries and their dependencies could be located anywhere. But the recently implemented rule (If I understand it correctly) prevents the use of the top level /bin /lib/ /sbin etc. folders, thus requiring bins and libs previously located there to no be placed/moved to /usr/bin /usr/lib /usr/sbin etc.

So, if the 32-bit compatibility SFS you are trying doesn't work --or worse screws up your system-- what you can do is mount that SFS, copy its files into a folder, move any files from the top level into their logical places under /usr and repack.

[mow9902]

Thanks for replying.

There is just a couple of old 32bit apps which I've been using for ages, and generally like to have them available. BUT - you are correct, there is alternatives and I should just abandon the old apps and keep my new (F96) system as clean as possible. Thanks for setting me straight.

[amethyst]

Or you can keep on running a 32-bit system like some others and myself. New 32-bit Puppys are still produced as are new 32-bit internet browsers. I have not seen any reason for myself to change to 64-bit at this point in time OR you can add a 32-bit Puppy (maybe even an old one depending on the apps you are running). This is what is nice about frugal Puppys, you can run a lot of Puppys from the same partition. Choose at bootup which one you want to use. It's relatively easy to add another Puppy manually. Actually, I'm guessing that majority of older Puppy users will probably have more than one Puppy installed for whatever reason.

[vtpup]

Okay so I've finally wandered here after forum searches from my attempts to get my older Dell Color Laser printer working in F96-CE rev4.

I've narrowed the problem down to the fact that the necessary CUPS printer filters are 32 bit, hence I need 32 bit compatibility in F96-CE. It is not possible to get 64 bit filters. They don't exist.

There is no problem printing from Fossapup64 with 32 bit compatibility added. The problem occurs in F96-CE. The following from above promises a solution:

The F95 compatibility sfs seems to load fine ...but the system library paths are not updated to include the extra 32bit libraries which it generates ie
/usr/lib/i386-linux-gnu
/lib/i386-linux-gnu

If I manually add these libraries into the search path with a 'wrapper' script then my 32bit apps (at least those I've tested) seem to load normally. Obviously it would be a pain to have to do this for each app, so I'm hoping there is a file somewhere which can be updated to automatically add these libraries to the system search paths.

Is it possible to provide an answer to their last question? I think that would solve my CUPS printing problem. Thanks in advance!

[vtpup]

Solution to the 32 bit compatibility problem was posted here:

https://www.forum.puppylinux.com/viewto ... 10#p134710