LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Gonna install Slackwarex86_64; helpful links please! (http://www.linuxquestions.org/questions/slackware-14/gonna-install-slackwarex86_64%3B-helpful-links-please-816958/)

linus72 06-29-2010 07:10 AM

Gonna install Slackwarex86_64; helpful links please!
 
So
I'm gonna take the plunge and install slackware64 current today
using Ponce's dvd
http://ponce.cc/slackware/slackware64-current/

and I need to know some tthings

1) slackbuilds I must use 32bit sbopkg or are there 64bit pkgs available?

2) is there any difference between 32bit current and 64bit current?
as in "anything broke in 64version"?

Biggest issue I guess may be flashplugin for x86_64??
thanks

EDIT: Oh!
does Alien's mirror-slackware-current work with slack64?

mlpa 06-29-2010 07:48 AM

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.

If you need some more specific help just ask.

mlpa 06-29-2010 07:56 AM

Quote:

EDIT: Oh!
does Alien's mirror-slackware-current work with slack64?
Yes, just open the script and there is a option where you can choose the arch.

brianL 06-29-2010 08:00 AM

For 64-bit SlackBuilds, run:
Code:

ARCH=x86_64 ./whatever.SlackBuild
Or edit the ARCH option in the SlackBuild script.

pixellany 06-29-2010 08:01 AM

Quote:

Originally Posted by mlpa (Post 4018104)
As far as I know, there is no diference between slackware x86 and x86_64.

If Slackware is like any other Linux distro, then there is a very big difference!!

brianL 06-29-2010 08:04 AM

Some (all?) 13.1 stable SlackBuilds might not be suitable for -current.

linus72 06-29-2010 08:32 AM

Thanks to you all!

er...
Quote:

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....

what about Flashplugin?

brianL 06-29-2010 08:36 AM

No, no live CD/DVD for -current.
Adobe haven't updated their 64-bit linux plugin yet.

hitest 06-29-2010 08:39 AM

Quote:

Originally Posted by linus72 (Post 4018145)
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.

mlpa 06-29-2010 09:01 AM

Quote:

If Slackware is like any other Linux distro, then there is a very big difference!!
Sorry, what I want to said is that, there is no difference in terms of packages or functionality between slackware x86 and x86_64.

There are some applications from Google, Adobe and Sun that don't run in 64 bits.

linus72 06-29-2010 09:52 AM

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?

mlpa 06-29-2010 09:58 AM

There is a topic in LQ with a discussion about it, here.

brianL 06-29-2010 10:05 AM

I'm using Slack64 multilib, so I used convertpkg-compat32 on the 32-bit Firefox, installed it, then installed the "safe" 32-bit Flash.

dugan 06-29-2010 10:07 AM

Especially pay attention to this post:
http://www.linuxquestions.org/questi...1/#post4003711

Summary:

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.

There's also the issue of having your 32-bit programs recognize your GTK themes, which does not have an obvious answer but is covered here:
http://wiki.linuxquestions.org/wiki/Slackware-FAQ

Didier Spaier 06-29-2010 02:00 PM

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



All times are GMT -5. The time now is 03:44 PM.