Hi Forum

I am planning to go <current> <multilib>... my problem here is :

1#) is this setup, current-multilib, already without "issues"...? bugs, etc... ?

So Far, I have been using SL64 13 stable with Icewm.. and it behaves like a charm... Part of me willing to do this transition is to give a chance to the new kde...

2#) If I am bold enough to go ahead... :-) which order of events would be more advisable...? Go Current before multilib, or go multilib before current... or else, it is Independent... ?

BRGDS

Alex

If you were to upgrade to current as off today you should be fine with the slack1364 multilib packages. Just follow Alien Bob's howto and you should be good to go. The only issue I have come across with slack64 multilib is some packages can conflict with there 64bit conterpart and sometimes during compile you will get an "symbols in wrong format" error. I have this problem with the vlc package. I found out it was the fontconfig-32 package that caused the error. So anyway if you decided to go multilib I would compile all your 64bit packages first them install the multilib packages.

1 members found this post helpful.

Hi Daedra

Thks for your answer, :-)

Should I have to compile a slackbuild in the future ( after having multilib enabled ) or a src2pkg project how to i default the compilation to 64bits arch...?

I know that in a SlackBuild, one sets the ARCH environment... and this is enough ( is it... ? I mean in a multilib system... )

But what about a src2pkg build...?

BRGDS

Alex

src2pkg will automatically set the correct arch don't worry. And as for the above problem I mentioned, don't worry that much about it, I only ran into that above problem maybe on 2-3 packages.

And as for slackbuilds, you can manually edit the script and change the line ARCH=i486 to ARCH=x86_64. or you can start the build like this

ARCH=x86_64 ./whatever.SlackBuild

1 members found this post helpful.

src2pkg will set the arch to x86_64 if you are running a 64-bit kernel. But, if you want to compile a 32-bit package, you just add '-M32' to the options. It will take care of all the libdir and pkgconfig declarations either way.

1 members found this post helpful.

Hi Forum

His there some need to upgrade to <current> before going <multilib>...?

Just for curiosity...

I am already <64-current>, and BTW, Kde is WAY MUCH BETTER... and the packages I had installed were not broken by the upgrade...

I was prepared to have to rebuild everything from scratch... :-)

BRGDS

Alex

As of right now multilib will work with both current and 13.0. But that could change in the future depending on what gets upgraded in current.

The only thing that will be problematic is when Slackware updates its gcc and/or glibc packages.

All of the "*-compat32" packages are independent of their 64-bit counterparts, so if the 64-bit packages are updated in Slackware-current you are not required to update the 32-bit packages as well.

What matters is that you use a set of -compat32 packages that has been taken from a stable Slackware tree: the libraries have inter-dependencies and what we always tell about "mixing packages from several Slackware releases is not a good idea" is valid for the -compat32 package set as well.

And if Slackware updates glibc/gcc and these remain pure 64-bit packages, be sure that I have multilib versions of those new packages available around the same time.

Eric

Hi Forum

Thanks for the Enlightening

As for now I am posting from my Slack64 current multilib using KDE current... :-)

Thx AlienBob, and Thx Pat, and last but not the least Thx Forum for bearing with me all this time... :-)

Wonderful distro... only have some tiny problems before I canswitch from lenny to Slack...

But I will solve them... w/ your help probably... :-)


BRGDS

Alex

Perfectly said, I remember having to learn about glibc the hard way many years ago, lol

1 members found this post helpful.