Do what you want, but you probably will spare yourself a lot of issues (and many among us a lot of support provided for free to no avail) trying first to just install a genuine (not multilib) Slackware 14.2 and build these packages. Then if you encounter issues due to a too old kernel, you will be able to install (not build) a newer kernel. IIRC you can just install a kernel for Slackware-current in Slackware 14.2, if I am wrong please someone corrects me.
I am not convinced that you be well prepared to run neither -current nor multilib, finding yourself how to sort the issues that can arise. You would need to first make a lot of thorough reading, like e.g. http://docs.slackware.com/slackware:multilib Thorough reading means understand not only the "how" but also the "why" of what you read instead of just apply blindly a recipe. Best, Didier PS If you need to run some 32-bit applications, it's usually possible to find other ones providing very similar features, else it's much easier to fire up a virtual machine with a 32-bit Slackware than to maintain a multilib system. And with 32G of RAM running virtual machines is not an issue at all On 10/4/18 2:50 PM, Rich Shepard wrote: > On Thu, 4 Oct 2018, 414N wrote: > >> I've got no problems too building glabels on a Slackware64 14.2 system >> with Eric's multilib packages installed. > >> If it is gcc, what version are you using? Is it >> "gcc-5.5.0_multilib-x86_64-1alien"? > > > Alan, > > The issue seems to be the newness of the hardware, most likely the CPU; > perhaps also the motherboard. Packages that have built with no issues on the > three 64-bit portables here that are older will not build on this new > system. > > A couple of examples. OpenBLAS (which I need for GRASS, the spatial > analysis tool) would not build until I added a line to the build script > specifying TARGET=ZEN. 'ZEN' is the codename for AMD's Ryzen line of > high-performance CPUs that were first released last year. Adding that target > allowed OpenBLAS to build. > > AlienBOB wrote that he, too, has a Ryzen CPU in a desktop and experienced > some failure issues just running. He fixed that by uupgrading the 14.2's > kernel to one in the 4.14 series. > > In order to build GnuCash I need goffice/goffice8, and neither will build > on this new box. But, LyX, TeXlive, and JabRef built flawlessly (and > quickly.) All this seems to point to support for a CPU released well after > the basic (and fully patched) 14.2 was released. > > Unless Those Who Know tell me not to upgrade to -current, just upgrade the > kernel (and it's been more than 15 years since I built a custom kernel from > kernel.org source; not since 2003 when I switched from Red Hat 7.4 to > Slackware-8.0) I'll do the upgrade this coming weekend. After learning how > best to do this. > > Thanks, > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users@slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/