slackware64 13.37 alpine.SlackBuild fails when trying to rebuild package
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
From the SBo FAQ
I have problems compiling with my unofficial and unsupported multilib setup.
If you are using multilib packages from somewhere and also have some 32bit packages installed, then you might run into problems with the build process trying to link 32bit libraries instead of 64bit libraries. If this occurs, it can probably be solved by placing the following line:
after the lines for CFLAGS and CXXFLAGS passed to the configure script. In other words, make it look something like this:
Beyond that, you are on your own. This is an unsupported setup.
hey hax, have you seen when latest alpine's sources have been released? I'll tell you, more than 3 years ago.
does alienbob have to patch for you all the unmaintained sources that doesn't support multilib?
maybe it's more reasonable that you go hunt yourself for patches (if they exist elsewhere) for the stuff you need to compile on your multilib install, or you can just use (like you have done, I think should have been no sweat) a pure 64 one (or a virtual machine).
I think it's evident why this setup is basically unsupported for building software and should not be a big issue too, or it's just me?
Last edited by ponce; 10-01-2011 at 06:20 PM.
Don't blame AlienBOB's Multilib packaging so I'd advise you to not point fingers.
Slackware doesn't ship with multilib for a reason. That reason is because Slackware doesn't use precompiled packages and uses SlackBuilds for source compiles instead. Because using multilib increases the workload administrators have to do, it's up to you the user to properly configure your system.
I wasn't being serious about being angry with alienbob this is only the second thing related to multilib that i've had trouble with since switching back to slackware (there's about 10^52 more things to go wrong before i get into ubuntu territory :P).