I have had this problem before on some packages. Make will pick up libraries in /usr/lib instead of /usr/lib64, adding these lines to the buildscript has fixed it for me.

if [ "$ARCH" = "i486" ]; then
SLKCFLAGS="-O2 -march=i486 -mtune=i686"
SLKLDFLAGS=""; LIBDIRSUFFIX=""
elif [ "$ARCH" = "i686" ]; then
SLKCFLAGS="-O2 -march=i686 -mtune=i686"
SLKLDFLAGS=""; LIBDIRSUFFIX=""
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC"
SLKLDFLAGS="-L/usr/lib64"; LIBDIRSUFFIX="64"
else
SLKCFLAGS="-O2"
SLKLDFLAGS=""; LIBDIRSUFFIX=""
fi

Then a little farther down add this

CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
LDFLAGS="$SLKLDFLAGS" \


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:
LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \
after the lines for CFLAGS and CXXFLAGS passed to the configure script. In other words, make it look something like this:
CFLAGS="$SLKCFLAGS" \
CXXFLAGS="$SLKCFLAGS" \
LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \
./configure \
Beyond that, you are on your own. This is an unsupported setup.

[Solved]slackware64-13-37 alpine.SlackBuild fails when trying to rebuild package
 

/me stabs alienbob's multilib stuff in the troat <_<
yeah ... it compiles just fine on a pure 64bit slackware64-13.37 install :/

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?

Also did you try adding the lines I suggested to the build? Adding those two lines solves this problem almost all the time.

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

sorry, I misunderstood :D