LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Newbie to Slackware64, but not Slackware (http://www.linuxquestions.org/questions/slackware-14/newbie-to-slackware64-but-not-slackware-778772/)

marnold 12-29-2009 05:26 PM

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

manwichmakesameal 12-29-2009 05:48 PM

Not really. The rest of it is pretty much the same. When you use slackbuilds from SBo, just remember to use ARCH=x86_64.

piratesmack 12-29-2009 05:48 PM

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.

marnold 12-29-2009 08:25 PM

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.

samac 12-30-2009 03:44 AM

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

voyciz 12-30-2009 08:13 PM

Quote:

Originally Posted by marnold (Post 3808400)
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.

piratesmack 12-31-2009 03:03 AM

Quote:

Originally Posted by marnold (Post 3808400)
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"

Didier Spaier 12-31-2009 04:41 AM

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 ;)

brianL 12-31-2009 06:00 AM

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

http://www.sbopkg.org/

AlvaroG 12-31-2009 07:45 AM

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.

GooseYArd 12-31-2009 08:08 AM

Quote:

Originally Posted by AlvaroG (Post 3809891)
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.

marnold 12-31-2009 02:44 PM

Quote:

Originally Posted by AlvaroG (Post 3809891)
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?

marnold 12-31-2009 02:49 PM

Quote:

Originally Posted by samac (Post 3808653)
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 . . .

samac 12-31-2009 02:56 PM

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

vigi 12-31-2009 05:44 PM

Be careful not to get a speeding ticket! It is fast.


All times are GMT -5. The time now is 12:32 PM.