/etc/profile.d/qt5.csh has incorrect syntax for setenv command
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.
No one has used (t)csh for decades, so this kind of error is left unnoticed. There is also a commented line '#setenv MALLOC_CHECK_=1' in glibc.csh and a few similar commented lines in libreoffice.csh of Alien's libreoffice package.
No one has used (t)csh for decades, so this kind of error is left unnoticed. There is also a commented line '#setenv MALLOC_CHECK_=1' in glibc.csh and a few similar commented lines in libreoffice.csh of Alien's libreoffice package.
Mon Mar 21 07:31:06 UTC 2022
l/qt5-5.15.3_20220318_e507d3e5-x86_64-1.txz: Upgraded.
Pulled from git again to fix missing liblocationlabsplugin.so.
Fixed syntax error in qt5.csh. Thanks to rkomar.
No one has used (t)csh for decades, so this kind of error is left unnoticed...
I have been using tcsh for decades, so maybe not "no one". However, I agree that it isn't common, and I'm not surprised that the odd error comes up. No hard feelings on my side.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.