Just installed 14.2 from DVD on Dell xps-410 - previously had 14.1 64 bit w/multilib from Alien, worked fine.
Now, reading Alien's instructions, "Adding Multilib Capability to Slackware on x86_64 Architecture"; I *think* I've completed the installation, but not sure.
I followed the 'quick and dirty' instructions to the letter, as root, with no difficulty. Downloaded all, using the lftp command to Alien's mirror; then executed "# upgradepkg --reinstall --install-new *.t?z"; and then, I *do have* the desired directory, "slackware64-compat32", so executed the other command: "# upgradepkg --install-new slackware64-compat32/*-compat32/*.t?z" with no problems.
Then the next sentence in Alien's instructions says, "That's All!", so I assumed I'm all done.
BUT ... reading further down the page, it gets pretty complex, and has words like, "...adding all the glibc and gcc names to (slackpkg's) blacklist." I guess this would be needed?
And I assume it's not necessary to run 'massconvert..' at all.
Am I right?
Thanks for comments...jrc
---
Also, I continue to be surprised at the ease and completeness each time I install a new Slackware version. Good Work guys!

If you're going to use slackpkg to keep your system updated, then you'd either want to blacklist those files or add the plugin slackpkg+ and add the multilib repo to that. It would allow you to install any updates to the multilib packages as they come out using slackpkg.

As for the massconvert, you're correct that you don't need to worry about it. That is if you don't have the rest of the slackware64-compat32 directory containing packages. This script allows you to point it to a 32bit Slackware tree and it will create all those compat32 packages that he included in that directory.

1 members found this post helpful.

Thanks, bass...appreciate the comment.
jrc