I'm attempting to install Pd-extended (Pure Data) on my Slackware64 14.1 system running on a ThinkPad T410. There's a SlackBuild for this program, so it should be a pretty easy task.

After installing all of the dependencies, I installed Pd-extended. The program works as expected, however it turns out that 64-bit builds are still considered to be in beta. Because of this, I'd like to install a more stable 32-bit version. This shouldn't be a problem. I'm already using Alien Bob's multilib setup for Skype.

This is where I could use some guidance. I thought I could probably compile a 32-bit version if I first installed 32-bit versions of all the dependencies, but I didn't want to mess around with that, so I thought it would be cleaner to create a 32-bit Slackware virtual machine to compile the package.

After creating the 32-bit VM and getting all the dependencies installed, I finally got a 32-bit SlackBuilds package for Pd-extended. I copied it over to the 64-bit host system and installed it. It installs fine, but when I try to run the program, I get a bunch of errors.
The first error is that it can't find "/usr/tcl//pd-gui.tcl". The installation does create a file called pd-gui.tcl, but it's put in /usr/bin/. If I create a copy of this and put it at /usr/tcl/pd-gui.tcl, then it complains about not being able to find another component, pd_connect. I haven't dug around to find this one yet, but feel that there must be something wrong with the package. I get similar problems if I try to install and run the package on the VM that created it.

I guess my question is, is this a reasonable method to try and create a 32-bit package for my 64-bit system? Do you notice anything in my method that would explain why the package isn't installing properly?

Also, is there anyone who happens to have a 32-bit binary for Pd-extended that they wouldn't mind sharing with me?
Alternatively, is there an easy way to install a debian package? The Pure Data website does provide .deb packages.

There seems to be a multi-arch package on slackbuilds.org for this. It explains to use "pdextended" to start the 32-bit version and "pdextended64" to start the 64-bit version. If you want to compile software that is 32-bit on a 64-bit multi-arch platform, use a slackbuild script(if available) and pass it the argument "ARCH=x86_64".

It would look like this:

Thanks for the reply.

Just to clarify, I'd like to have the x86 version of the program running on my x86_64 system. Shouldn't I run:
Wouldn't this create the 32-bit binaries?

Also, when I installed it on my 64-bit system, I ended up with the "pdextended64" executable, but not "pdextended". In fact, I don't even have "pdextended" on my 32-bit VM. I'm sure there must be something wrong with the package I created.

No, if you want to create strictly 32-bit binaries you need to use "i486" as the arch flag.

No, if you want to create strictly 32-bit binaries you need to use "i486" as the arch flag.

I'm not sure if I should start a new thread for this, but when trying to run the SlackBuild, it ends part way through with the message,
Is there anything I can do about this, or do I pretty much need to talk to the author of the SlackBuild?

The directory contains:

Don't complicate things uselessly. Looking at the SlackBuild the author takes care of dealing with 64 vs 32 bits, so there should be actually no need to make a 32 bits package.

Thanks for the reply, Didier.

The reason I want to make a 32-bit package is that the 64-bit version is still considered a beta, and some libraries are known to have serious issues.

I understand. But as long as you don't personally encounter these issues, does that really matter (unless security be in concern)?