I've read the notes and instructions from Alien Bob about creating a real multilib slack64 HERE. Because of my imperfect english & tech know how I wanna ask: what will be happenend, if I have to upgrade a multilib slack64? There must be gaps because my slackpkg will only upgrade slackware64, right? As a result, do I have to reinstall the 32bit libs every time manually after a upgrade?
thanks in advance
Being that all of the supported packages and versions distributed by slackware are 64 bit, you theoretically shouldn't have to worry about updating 32 bit packages.
The 32 bit packages should be largely independent of your 64 bit packages. That is unless the 32 bit package overwrites files previously installed by a 64 bit package. Like for example, you compile for 32 bits for an existing 64 bit program. If you don't change the executable names, then the 32bit package will overwrite those binaries.
If you update the tool chain (it gets updated for major releases) then you will probably have to update your tool chain in 32 bit as well. I don't know how much old 32 bit xlibs will affect you if they are older than the current 64bit xlibs.
Once slackware 13.0 is released, minor updates for security fixes shouldn't affect you much.
answer some of your questions.
My recommendation is to wait for Slackware-13.0 and do a fresh install, then
follow his guide and create the multilib enabled system, since it should be
released just any day now -- aaa_elflibs is in today's ChangeLog.
There is a major difference in Slackware64's multilib environment, and that of
Slamd64. As Alien Bob wrote, "Slamd64 has separate 64bit and 32bit gcc/glibc
multilib packages." Using the method from his wiki, your system will only
have multilib glibc and gcc packages. It seems that the recomplied 32-bit
compatible packages for Slackware64 is a much cleaner way to do it.
First, if you use slackpkg, you need to comment out glibc and gcc. Here is what
Alien Bob wrote in his instructions in the article you linked:
As lumak stated, Slackware will have packages for both x86 (32-bit) and x86_64 (64-bit)
arches. You will upgrade the x86_64 packages independently of the x86 ones. The apps
that I've recompiled using his method are for libs needed in other packages, and not
apps that you run such as Firefox, Thunderbird, GIMP, etc. Those packages have 64-bit
source, and therefore, 64-bit packages. For applications that you want to install
which don't have 64-bit source, this helps you build and run them on Slackware64.
If I'm correct, those x86 packages which are rebuilt to compat32 packages will only
need to be upgraded if software requires libs that are in their upgraded versions.
You can see that right now I have 84 compat32 packages installed:
Slacwkare-13.0 comes out, I'll install fresh and do it all again. Everything is working
very well. I have compiled some 32-bit software on here, and am running Wine and
Skype and QQ (32-bit only source) under Slackware64 -current with no problems.
If you use slackpkg, you need to be careful about what you upgrade. When you run
it you will notice when the list of available packages appears, as one is highlighted,
there is a line at the bottom of the screen to tell you the presently installed pkg.
I think the only 'gotcha' that came up for me so for was glibc and gcc, before I found
out exactly how to write their syntax to blacklist them. The only other things I have
in /etc/slackpkg/blacklist are personal packages that Slackware ships, but I have
rebuilt to meet my needs, and the kernel packages that I don't upgrade.
You will not overwrite any 64-bit binaries if you follow Alien Bob's instructions.
Remember to backup your system, and if you have any doubts along the way, just stop
and ask before going further. It worked pretty easy for me.
Once Slackware-13.0 is released, Alien Bob will answer any questions you have beyond
this point. Hope this little bit of info helps until then.
Thanks for the link to Alien Bob's Slackware64 multi-lib site. I just followed the instructions and I am now running a true multi-lib version of Slackware-current, which is relatively easy to maintain and update.
The convertpkg-compat32 script is especially useful as it allows you to convert any 32bit Slackware package to a stripped down compat32 package. This allows you to install any 32-bit packages in a way that is safe and easy to maintain.
This, in my opinion, is the best option for those that need to run 32-bit programs on their Slackware64 systems.
I would like to install multilib but I do not have a Slackware 32 disk. Is it possible to mount an ftp site so that the massconvert script will read directly from it?
Alien Bob has also made the packages available now. Read his blog post.
I've been following this post (just recently moved to 64 - thanks everyone!) I know this is late but you can use this to grab the packages (change 13.1 to 13.0 if you need):
|All times are GMT -5. The time now is 11:44 AM.|