[SOLVED] Cannot install fpc 32 bit on 64 bit multilib slackbuild.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Cannot install fpc 32 bit on 64 bit multilib slackbuild.
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…
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.
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.
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...
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
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.
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
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Cannot install fpc 32 bit on 64 bit multilib slackbuild.
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.
