[SOLVED] Cannot install fpc 32 bit on 64 bit multilib slackbuild.

george-lappies · 05-26-2011, 12:49 AM

Hi all, I can’t seem to compile lazarus on my multilib setup. It uses fpc to compile. I had 64bit version of fpc installed and lazarus can not compile. I uninstalled 64 bit fpc, but can’t seem to install the 32 bit version via slackbuild. It keeps looking for the 64 bit archive in the slackbuild directory…

piratesmack · 05-26-2011, 01:00 AM

edit: sorry, misread your post

Try running the fpc Slackbuild like this to package the 32-Bit version:
ARCH=i486 ./fpc.SlackBuild

george-lappies · 05-26-2011, 01:14 AM

Quote:

Originally Posted by piratesmack

edit: sorry, misread your post

Try running the fpc Slackbuild like this to package the 32-Bit version:
ARCH=i486 ./fpc.SlackBuild

Thanks I have been to that faq

Actually I do not have the problem they list the solution for there. My problem is even after running the script to set the build env to 32 bit the slackbuild bombs out saying it cant find the 64 bit tar file with the source... so I don't even get to the compile stage yet.

Daedra · 05-26-2011, 01:20 AM

I've always had trouble compiling 32bit programs in slackware64 with multilib installed. It's probably just me but now I just install slack 32bit in a virtual machine and compile any 32bit programs I need there. It's a little more time consuming but it works.

george-lappies · 05-26-2011, 04:47 AM

Quote:

Originally Posted by Daedra

I've always had trouble compiling 32bit programs in slackware64 with multilib installed. It's probably just me but now I just install slack 32bit in a virtual machine and compile any 32bit programs I need there. It's a little more time consuming but it works.

sure, i'll go that route as well. My problem is virtualbox slackbuild is 32bit only...

bgeddy · 05-26-2011, 05:42 AM

Quote:

sure, i'll go that route as well. My problem is virtualbox slackbuild is 32bit only...

VirtualBox is one of the only applications I just install on my Slackware64 system without building a package. It works fine. Admittedly it would be nice to build a package but I have't had the time to look into this much and have got used to the fact that it 'just works'. It's not very difficult to uninstall should you want.

george-lappies · 05-26-2011, 06:49 AM

Quote:

Originally Posted by bgeddy

VirtualBox is one of the only applications I just install on my Slackware64 system without building a package. It works fine. Admittedly it would be nice to build a package but I have't had the time to look into this much and have got used to the fact that it 'just works'. It's not very difficult to uninstall should you want.

Downloaded and installed the 64bit 4.0.8 virtualbox binary. It does work extremely well

Kowalczyk · 05-26-2011, 07:16 AM

They have a 64bits installer for Virtualbox on their page

http://www.virtualbox.org/wiki/Linux_Downloads

Here. Download that and run the installer script.

Or download that and modify the slackbuild script.

(PS. I havent tried it, so Im not sure how it works)

bgeddy · 05-26-2011, 10:37 AM

Quote:

Or download that and modify the slackbuild script.

Well you won't get far with that. The installable VirtualBox is a prebuilt, packed, binary with a header attached to unpack the binary on installation and do various other stuff. The SlackBuild version builds from source. Creating a package from this would involve extracting the prebuilt archive and installing it somewhere temporarily then building a package. This will probably involve extensively modding the install scripts,(or maybe using a chroot), from the binary and is a a lot more work than just modifying the original SlackBuild to suit.

Besides all that it looks like the OP has successfully installed the binaries now anyway.