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 installed some tgz packages that don't compiled for my current system (Slackware 10.2), and they work very good. But when I download packages from www.linuxpackages.net, I found they are marked that compiled for a certain version of operating system (Slackware 10, 10.1. 10.2). So I want to know if I install a package don't compiled for my current system, will it cause something wrong? If it won't, why people distinguish different version?
Usually, they are just optimized for a certain system but will run (or not, if they are from LinuxPackages; that is one mixed bunch). You should be more careful with the version number, if they are older than 10.0. Obviously, it all comes down to program and kernel dependencies.
Do you mean: if a package works, I can use it. If it cannot work, I should leave it?
Not exactly.
Actually it is like the particular package is tested on some Standard system, and that version no. or so is included.
If you try the package on some other system, it *may* work, but success is not guaranteed.
Installing the software on the recommended system is a sureshot win.
Thank you!
I want an old wine version (20041019) for winetools, but there are no compiled package for Slackware 10.2, and I can't compile it by myself (I did it on Slackware 10.1. I think the gcc in 10.2 may produce some wrong files when compile it). What can I do?
Originally posted by shadkong Thank you!
I want an old wine version (20041019) for winetools, but there are no compiled package for Slackware 10.2, and I can't compile it by myself (I did it on Slackware 10.1. I think the gcc in 10.2 may produce some wrong files when compile it). What can I do?
compiling it yourself should be possible.
so what compile errors do you get ?
One should be very careful to install the necessary compilers when installing the system... I rarely have things that won't compile (except little, light-weight Abiword, which needs half a Gnome to function).
I cannot compile d4x 2.5.5 and wine-20041019 on Slackware 10.2. And I'm sure compilers are installed correctly. And I think the software I cannot compile are not the only two listed above.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.