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.
Since 13.0, Slackware has an official x86_64 port. There is no grub package by default, and if you simply try to install it, you will get an error. A lot of users, including me, prefer grub over lilo.
It is not so much difficult to install grub on Slackware64, and I finally managed to do it. So it I thought it will be helpful for those who are new to Slackware64 and wants the old grub back. Hence the guide. Hope this will help you guys.
UGH! ok I was trying to compile q4wine for god knows what reason and half the variables in the build/CMakeCache.txt were pointing to /usr/lib64/qt and the other half were pointint to /usr/lib/qt.
I solved my issue by adding
Code:
CMAKE_PREFIX_PATH=/usr/lib$LIBDIRSUFFIX/qt \
on the line right before
cmake \
Hope this helps somebody else with cmake and qt problems.
EDIT: I added a new script for 195.36.24 as well as a script to compile libvdpau-compat32 on a 64 bit system. I never hear any feedback on this stuff... is it working for other people? Do I have errors anywhere?
ORIGINAL POST:
I'm one of those people that personally don't like installing things on my system without having proper packages made for tracking the files. As such I edited the scripts on SlackBuilds.org for an additional package to support this. ...
Additional note: A broadcom-sta package has now been added to the Slackbuilds Repository. (It also appears that a patch is no longer necessary for the 2.6.29 kernels. I haven't tested this though... unless I upgrade kernels I'm leaving this alone.)
(Note: onebuck pointed out in the Slackware forum that Broadcom provides a patch for kernel 2.6.29. I had been having trouble finding the correct patches, so I was using the patched Debian source. That's pointless now, so I've deleted the...
When I saw the announcement on Slackware.com that Slackware64-current had gone public, I had to try it. (I've been running Slackware as my primary OS--both desktop and server--for years.)
I downloaded the kernels, isolinux, and the slackware64 (packages) directories and begin reading.
OK, first step is to generate a boot CD. No problem! The directions in isolinux/README.TXT provided all the information I needed to make a boot DVD or CD. I opted to make a boot CD...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.