Darth Vader polluting the forum space again with nonsense. You have no idea what you are talking about Darth Vader when you think 32-bit libs pollute some opiate delusions of 64-bit pureness. So you have a fancy computer with a shitty graphics card, have you actually ever worked in IT? Even for 5 minutes? I really do not care what you think Pat or Eric think, mind your own business and let them speak for themselves!

Ssshhh.....
https://www.youtube.com/watch?v=2j2gVSGVpqg

1 members found this post helpful.

However, I think he's right.

Looks like everybody installs Slackware64, then use Multi-Lib to run their 32-bit software. So many, that they try to merge it in the distribution.

If that fact reflects in the Slackware 32-bit sales, and they flop, obviously the consequences are that the Slackware 32-bit "product" will be abandoned sooner or later, which will result also in the disapereance of Multi-Lib project of Eric Hameleers.

I am fraid that this is not forum polution but a warning about the consequences of our actions made today.

2 members found this post helpful.

It is FUD from the marketing department, that is all.

1 members found this post helpful.

Next time, maybe make a fast investigation before asking

2 members found this post helpful.

You do not know how much I have idea about these things and how they work.

To be honest, I have several fancy computers with shitty graphics cards.

Because what I do is usually related to things which does not need fancy graphics cards, for example Apache, PHP, MySQL, Redis, etc...

I worked in IT continuously on the last 25 years and I also used Slackware on the last 20 years.

Just because you are a newcomer, that does not make a rule that everybody is like you.

That Multi-Lib thing is a recursive story, so recursive that I learned the end results. Yet, I hope that I am mistaken this time.

BUT, did you see it in Slackware64? First time when it was proposed and extensively debated, was while Slackware64 13.1 development cycle, BTW...

2 members found this post helpful.

Then, from Patrick Volkerding? I understand that he's one-man army also in Slackware, Inc.

However, if that's true, will make Darth Vader's words a very serious warning.

1 members found this post helpful.

I do NOT work for Patrick Volkerding or Slackware, Inc.

And I never worked for him or his company.

I am just a Slackware user, nothing more.

2 members found this post helpful.

I still don't see how anyone has addressed why it would be *harmful* to the Slackware community in any way, to have multilib gcc/glibc and compat32-tools available in EXTRA; I'm seeing there's enough of a backlash not to have them installed by default on a 64-bit machine, or even as part of the main tree. I *personally* disagree that it even needs to be in extra, but I think it's a good compromise.

To Darth (whom I've ignored so far due to his consistently alarmist tone) I heed the words of Mr. Volkerding well. However, I also remember him saying in a podcast in October 2006 on The Linux Link Tech Show (around the release of Slackware 11.0) that people who want to run a pure 64-bit system may find that they DON'T actually want to, and people might surprise themselves as to how reliant they are on 32-bit software. At that time, I took that as a warning to steer clear of 64-bit altogether on my desktop machine; I ran 32-bit Slackware on it, it ran GREAT and all was right in the world.

But a couple years back, I found myself feeling the time was right to switch (as I already had on my Slackware *server* for some time) and I was actually surprised at how meaningless the words "multilib-ready" were, and that, as I said before, turning to AlienBOB's *3rd party repository* was all but necessary to make Slackware64 *truly* multilib-ready.

So yes, I admit I'm late to the discussion, but I was fully aware of it before Slackware64 even came out, as I've indicated.

It may seem like it's too late to bring this up. But in a funny way, is this not the *best* time? 64-bit has all but taken over the landscape, and there are very few apps now that require 32-bit functionality. So if we operate under the assumption that Slackware32 is going away at some point in the next number of years, wouldn't it make sense *now* to set up a transition path, so that when we *do* look to fully phasing out 32-bit, we can have some way to bridge that gap? I would think that even if 32-bit goes away, having a compatibility layer present so that old apps are at least operational would be a good idea.

3 members found this post helpful.

Recursive? What are you babbling about? You fill another thread with off topic garbage. All those years and I would have assumed you would have learnt by now the wisdom of keeping a thread on topic.

Cross compiling is not anything new, mixing 32-bit libs on a 64-bit system does not ruin some opiate addicts delusions of purity, only in their own mind. According to your ramblings we can throw out every operating system out there and most games. Let us start throwing out audio and video files because they are not 64-bit 'pure' too! Why not stop there, and all the PDFs not 64-bit 'pure' should be burned too.

I' am not new to Linux and almost two decades ago ran Slackware on gaming computers I built. Got lazy and been distro hopping though for awhile now.

This current round of FUD reminds me more of a Windoze purist' s mad monologues.

2 members found this post helpful.

There is a place for your forum posts DV. It is called a blog. :-)

https://www.linuxquestions.org/questions/blog/

I am not the one who chosen the pure 64-bit path for Slackware64, even I agree totally with this idea.

I'd just explained why this probably will never be adopted; and what disappoint me is that you people behavior make faster the Slackware 32-bit doom, while I appreciate very much it.

And the proposals to adopt Multi-Lib on Slackware64 aren't revolutionary ideas; like I said, the first ones appeared long years ago while 13.1 development cycle.

Then, they reappeared after several years, and so on. Probably what I said is just FUD, at least in your opinion, in other hand, there is still no Multi-Lib adopted even today. Ask yourself why.

BTW, the Multi-Lib aka multi-architecture GLIBC and GCC aren't the same with cross-compiling.

A quick googling made me to learn that apparently "pure 64-bit" is a term used for the x86_64 operating systems which has no native support for running 32-bit applications.

Then, in the lawman terms, a "pure 64-bit" Linux will be a non Multi-Lib operating system. Like the Slackware64 today.

Excuse me, but looks like you are overacting, insulting around while you have no clue about what they talk.

You are kind to google a bit, at least, just like me, before acting all mighty?

Apparently that "pure 64-bit" is a legit term which describe exactly the Slackware developers choices.

2 members found this post helpful.

Semantics, technically not compiling for a different architecture but a different word length but there is significant/subtle architectural differences to warrant 'clean' 32 and 64-bit Slackware (x86 & x86_64) and hence it is technically cross-compiling. You do not need a 32-bit Slackware branch to create 32-bit libs on Slackware64, or any other distro. The end of 32-bit Slackware does not effect multilib as far as I know. Years from now. I lost my crystal ball on the bus though, it was broken, and I think DV found it.

If this was a windows forum from a few years ago DV would be rambling about the horrid state of affairs when there is no 16-bit hardware being made to feed DOS nostalgia and how much faster and better programs ran under DOS before memory protection and other bloated, useless, crap introduced by NT...

Yes, but there was explained that the actual Multi-Lib made by Eric Hameleers reuse the Slackware 32-bit packages and he has no intention to maintain his own 32-bit libs after the Slackware 32-bit end of life.

How Patrick Volkerding apparently will not be too happy to still maintain 32-bit libs for Slackware64 and Eric Hameleers has no intentions to, the result will be the end of Multi-Lib for Slackware, too.

And I remember that somewhere I read myself Eric's statements.

Which would be an opportunity for the community to take some of the load off.