How to make a Multilib Toolchain for Slackware i585? Aka wanting a self-sufficient Slackware 32bit with 64bit kernels built locally
by LuckyCyborg from LinuxQuestions.org on (#5FR89)
As probably everybody know, it is possible to run a 32bit userspace with a 64bit kernel and works well.
From my own experiments with kernel packages grabbed from Slackware64 and installed on a Slackware i586 system, the results are even better than of a standard 32bit or 64bit system.
It has a lower memory consumption and it is quite fast - long story short, I am very satisfied.
However, I want to not depend on a Slackware64 system (or packages repository) but I want to build my own 64bit kernels on this particular system.
So, I guess that I need a Multilib Toolchain for 32bit systems, a GCC & Comp. capable to build a proper 64bit kernel.
I wonder how I can make this particular Multilib Toolchain, used and/or usable ONLY for building 64bit kernels and their external modules.


From my own experiments with kernel packages grabbed from Slackware64 and installed on a Slackware i586 system, the results are even better than of a standard 32bit or 64bit system.
It has a lower memory consumption and it is quite fast - long story short, I am very satisfied.
However, I want to not depend on a Slackware64 system (or packages repository) but I want to build my own 64bit kernels on this particular system.
So, I guess that I need a Multilib Toolchain for 32bit systems, a GCC & Comp. capable to build a proper 64bit kernel.
I wonder how I can make this particular Multilib Toolchain, used and/or usable ONLY for building 64bit kernels and their external modules.