LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-29-2009, 06:26 PM   #1
marnold
Member
 
Registered: Dec 2005
Distribution: Slackware64 14.1
Posts: 258

Rep: Reputation: 32
Newbie to Slackware64, but not Slackware


Hi folks,

I just ordered a new i5-750 box and will be installing Slackware64 13.0 on it. I've been using Slackware since 8.x, but I've never ventured into 64 bit OSes before. Anything in particular that I should be prepared for other than the multilib stuff which seems to be well-documented?

Thanks,
Matt
 
Old 12-29-2009, 06:48 PM   #2
manwichmakesameal
Member
 
Registered: Aug 2006
Distribution: Slackware
Posts: 800

Rep: Reputation: 100Reputation: 100
Not really. The rest of it is pretty much the same. When you use slackbuilds from SBo, just remember to use ARCH=x86_64.
 
Old 12-29-2009, 06:48 PM   #3
piratesmack
Member
 
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 518

Rep: Reputation: 133Reputation: 133
The only thing different I can think of is you need to run your SlackBuilds like this:
ARCH=x86_64 ./PRGNAM.SlackBuild

Most things will now build on a 64-Bit system and the SlackBuilds have been updated. If you can use Slackware, you probably won't have any trouble using Slackware64.
 
Old 12-29-2009, 09:25 PM   #4
marnold
Member
 
Registered: Dec 2005
Distribution: Slackware64 14.1
Posts: 258

Original Poster
Rep: Reputation: 32
That's what I was hoping to hear! I'm sure there will be some hardware-related hiccups as I try to get everything working, but that's half the fun of a new box I assume I could just slap that ARCH=x86_64 in my .bashrc so I'd never have to remember it.
 
Old 12-30-2009, 04:44 AM   #5
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 137Reputation: 137
If you are a KDE user consider upgrading to current or vbatts packages for KDE 4.3.1 or using another desktop. The KDE included in Slackware 13.0 is, in my opinion, a bit "rough and ready", though it can be improved by turning off akonadi and nepomuk and replacing kwin with the openbox window manager.

samac
 
Old 12-30-2009, 09:13 PM   #6
voyciz
Member
 
Registered: Mar 2004
Distribution: Slackware
Posts: 425

Rep: Reputation: 40
Quote:
Originally Posted by marnold View Post
I assume I could just slap that ARCH=x86_64 in my .bashrc so I'd never have to remember it.
Here's the problem with that: ARCH gets started with bash, set for 64-bit. Then you run the SlackBuild script, and ARCH is redefined in the subshell and now it's back to 32. What I do is use a function I've defined in .bash_profile to tailor all build scripts, just gotta remember to run it on each one.
 
Old 12-31-2009, 04:03 AM   #7
piratesmack
Member
 
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 518

Rep: Reputation: 133Reputation: 133
Quote:
Originally Posted by marnold View Post
I assume I could just slap that ARCH=x86_64 in my .bashrc so I'd never have to remember it.
You have to export it or else the SlackBuild script won't be able to use it.
So your .bashrc should have:
Code:
export ARCH="x86_64"
 
Old 12-31-2009, 05:41 AM   #8
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,646

Rep: Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231Reputation: 1231
I do it system wide:
Code:
bash-3.1$ cat /etc/profile.d/local_setup.sh
#!/bin/sh
export ARCH=$(uname -m)
bash-3.1$
Of course local_setup.sh is executable.

If you use slackpkg, be careful to select a 64 bits mirror in /etc/slackpkg/mirrors

Last edited by Didier Spaier; 12-31-2009 at 07:15 AM.
 
Old 12-31-2009, 07:00 AM   #9
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,134
Blog Entries: 52

Rep: Reputation: Disabled
If you install sbopkg for SlackBuilds, it will detect that you're running x86_64 automatically.

http://www.sbopkg.org/
 
Old 12-31-2009, 08:45 AM   #10
AlvaroG
Member
 
Registered: Jul 2009
Location: Canelones, Uruguay
Distribution: Slackware
Posts: 128

Rep: Reputation: 31
Regarding multilib, there is an annoying problem when compiling programs from source.
Many of the build scripts will look for libraries in /usr/lib, and try to compile against them. This usually leads to configure errors due to missing libraries, or compile errors regarding mainly to pointer casting, although other kind of errors may occur.

My quick 'n' dirty solution, knowing that only a few programs actually rely on that folder (the wicd I compiled 'cause the one that came with slackware have a few issues and wine) was to temporarily rename /usr/lib to something else. Sometimes the config scripts are hard coded with the /usr/lib path, so just touching the environment variables is not enough.

I had a lot of failed compiles before really taking a look at the errors and realize the real cause.
 
Old 12-31-2009, 09:08 AM   #11
GooseYArd
Member
 
Registered: Jul 2009
Location: Reston, VA
Distribution: Slackware, Ubuntu, RHEL
Posts: 183

Rep: Reputation: 46
Quote:
Originally Posted by AlvaroG View Post
Regarding multilib, there is an annoying problem when compiling programs from source.
Many of the build scripts will look for libraries in /usr/lib, and try to compile against them.
I ran into that also, here's an example:

--- bitlbee-1.2.4/configure.orig 2009-10-17 11:26:46.000000000 -0400
+++ bitlbee-1.2.4/configure 2009-12-17 13:56:41.160985447 -0500
@@ -19,7 +19,7 @@
pidfile='/var/run/bitlbee.pid'
ipcsocket='/var/run/bitlbee.sock'
pcdir='$prefix/lib/pkgconfig'
-systemlibdirs="/lib /usr/lib /usr/local/lib"
+systemlibdirs="/lib64 /usr/lib64 /lib /usr/lib /usr/local/lib"

msn=1
jabber=1

its easy to fix the 64 bit build, but then producing a 32 bit build on a machine with lib64 would be busted. I guess maybe some conditional patching based on $ARCH is the practical workaround.
 
Old 12-31-2009, 03:44 PM   #12
marnold
Member
 
Registered: Dec 2005
Distribution: Slackware64 14.1
Posts: 258

Original Poster
Rep: Reputation: 32
Quote:
Originally Posted by AlvaroG View Post
Regarding multilib, there is an annoying problem when compiling programs from source.
Many of the build scripts will look for libraries in /usr/lib, and try to compile against them. This usually leads to configure errors due to missing libraries, or compile errors regarding mainly to pointer casting, although other kind of errors may occur.
Wouldn't that only be an issue if you were compiling a 32 bit program for a 64 bit environment or am I missing something?
 
Old 12-31-2009, 03:49 PM   #13
marnold
Member
 
Registered: Dec 2005
Distribution: Slackware64 14.1
Posts: 258

Original Poster
Rep: Reputation: 32
Quote:
Originally Posted by samac View Post
If you are a KDE user consider upgrading to current or vbatts packages for KDE 4.3.1 or using another desktop. The KDE included in Slackware 13.0 is, in my opinion, a bit "rough and ready", though it can be improved by turning off akonadi and nepomuk and replacing kwin with the openbox window manager.
I've heard reports of less than happy things with that version of KDE. Are the -current versions drop-in replacements or will that mess other things up? I suppose it would be foolish to ask if Slack 13.1 would be on the horizon for just such an update . . .
 
Old 12-31-2009, 03:56 PM   #14
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 137Reputation: 137
Quote:
Are the -current versions drop-in replacements or will that mess other things up?
No they are most definitely not drop in replacements you will have to upgrade to current completely. I believe there the vbatts KDE will drop straight in. Here is a link on how to do it http://www.linuxquestions.org/questi...vbatts-778684/

samac
 
Old 12-31-2009, 06:44 PM   #15
vigi
Member
 
Registered: May 2009
Location: australia
Distribution: slackware
Posts: 177

Rep: Reputation: 27
Be careful not to get a speeding ticket! It is fast.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware 12.2 or Slackware64 glore2002 Slackware 28 08-22-2009 07:13 PM


All times are GMT -5. The time now is 09:43 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration