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.
As far as I know, there is no diference between slackware x86 and x86_64.
If you use slackbuilds, there is no problem, allmost all programs can be compiled for 64 bits.
Alien bob have a tutorial to make a slackware multilib in is wiki.
Some (all?) 13.1 stable SlackBuilds might not be suitable for -current.
I use alot of sbopkg 13.1 in nfluxos slack current edition and have noticed 0 problems!
maybe it'll be so for 64 too...
is there a -current x86_64 livecd/dvd available?
I couldn't find one...although I did find BlueWhite64 miniLive which is pretty cool!
its 12.0 though
OK
I'm gonna start the install using Ponce's unofficial dvd and will report back
and will start Alien's mirror-slackware-current.sh for x86_64 on other pc....
OK
I'm gonna start the install using Ponce's unofficial dvd and will report back
and will start Alien's mirror-slackware-current.sh for x86_64 on other pc....
I have used unofficial -current ISOs before and they worked okay. However, I now maintain and only use Alien Bob's -current ISOs. I like the md5 checksum feature of Eric's -current script.
Edit(added later): I also manually upgrade my boxes to -current.
mmmm
well flashplugin from slackbuilds crashes just like on the arch64 I installed
though it only crashes if I open a extra tab on a window that uses flash...
is there a how-to on how to get 32bit firefox, flash, etc working slack64?
If you replace Seamonkey with the 32-bit version (not the 32-bit compatibility version, the 32-bit version), and install the 32-bit or (64-bit and 32-bit compatibility) versions of ORBit2 and GConf, then you can run 32-bit Chrome.
As of 13.1, you machine's architecture is automatically detected by the slackbuilds. This is true for the "official" ones, i.e. those shipped with Slackware 13.1, and for those provided by slackbuilds.org as well. So there is no more need to indicate it at package building time -- provided you are not cross-compiling, of course
See below the relevant part of a "new" slackbuild:
Code:
# Automatically determine the architecture we're building on:
if [ -z "$ARCH" ]; then
case "$( uname -m )" in
i?86) export ARCH=i486 ;;
arm*) export ARCH=arm ;;
# Unless $ARCH is already set, use uname -m for all other archs:
*) export ARCH=$( uname -m ) ;;
esac
fi
Last edited by Didier Spaier; 06-29-2010 at 01:17 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.