SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have Steam running on two machines through this method.
EDIT: I've just through another thread that you have multilib. Hopefully Eric's Steam client will help. I would uninstall the other if I were you.
AWESOME MAN! But I am not as smart as you, this is what I type:
Code:
bash-4.3$ su
Password:
bash-4.3# ls
README README.Slackware steam_install_agreement.txt steamclient.SlackBuild
bash-4.3# ./steamclient.SlackBuild
bash: ./steamclient.SlackBuild: Permission denied
bash-4.3# make install
make: *** No rule to make target 'install'. Stop.
bash-4.3#
I tried running the slackbuild but to no avail, I THEN READ THE README like any God fearing slacker would do and still to no avail, I guess I can run the .sh script? IDK what to do next from here because this is the first time I am encountering this. I am assuming the source file is not included with the alienbob files I downloaded for 14.2?
Do you have a desire to be compiling all these programs? Because Eric (Alien Bob) makes all his SlackBuilds available as pre-compiled packages. You could simply download the package (it ends in .tgz or .txz) and then run upgradepkg against the new package and it should upgrade your old one. If you get the stuff from Eric to build the package, and get the whole folder, it will include the source. If you get the stuff from SlackBuilds.org (commonly called SBo), it won't include the source and you would need to download that separately.
But the issue with your command is that steamclient.SlackBuild doesn't have the execute permission. You would need to either add that permission (chmod +x steamclient.SlackBuild) or tell the shell to run it as a script (sh steamclient.SlackBuild). Once it is executable, it will then error out since it is missing the download. Once you have that, it should work fine.
Last edited by bassmadrigal; 06-05-2019 at 10:59 AM.
I don't know why, back they are always executable for me, I never have to run chmod. Must be automated or something.
To be honest, I've been using sbopkg for sometime now and haven't gone through the "normal" SlackBuild process in a while. I know sbopkg is doing a lot of this for me and I've started to take it for granted. Maybe it's time to go through a queue manually again just to blow the dust off that part of my memory.
My tip was solely based upon the terminal output in Slackwarefanboy's post where permission to execute was denied.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
