[SOLVED] Installing 32-bit OpenAL on Slackware64-current/multilib, getting linker error ("File in wrong format")
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can you post the actual end of the build log showing the error and lines leading up to it? OpenAL is not 32-bit-only, so it should build fine on Slackware64-14.2 (of course, no guarantees about -current). You should also see if there are any updates to it in ponce's repo for -current, as that's what it is for.
Finally, you could try setting LDFLAGS. It is not an automake thing, it is a shell environment variable. Either of the following would have the same effect:
I downloaded and installed the 32-bit and 64-bit version of OpenAL version 1.17.2 from AlienBob's SlackBuild Rpo
However, this time he didn't update the 32-bit version to 1.18.0 along with the 64-bit version.
However, I was able to build a 32-bit version from the SBo Slackbuild using the wrapper script below.
The 'secret' for me was to source /etc/profile.d/32dev.sh ( part of AlienBob's Multilib Environment ).
The wrapper script seemed to do 'the right thing' and ldd resolved 32-bit libraries and doinst.sh referenced usr/lib/ as expected.
HTH
-- kjh
# this is my 'standard' SlackBuild Wrapper Script, modified to build a 32-bit version of OpenAL
# copy it into the SBo OpenAL/ directory along with 'the usual' files
#
# cat .do-OpenAL.SlackBuild-32bit.sh
Code:
#!/bin/sh
DoName="OpenAL.SlackBuild"
. ./OpenAL.info
MyVersion="$VERSION"
LogNam="$DoName-$MyVersion-32-bit.log"
unset PRGNAM
unset VERSION
unset HOMEPAGE
unset DOWNLOAD
unset MD5SUM
unset DOWNLOAD_x86_64
unset MD5SUM_x86_64
unset REQUIRES
unset MAINTAINER
unset EMAIL
#
# set and export any extra variables here
#
# README:
#
# OpenAL is a cross-platform 3D audio API appropriate for use with gaming
# applications and many other types of audio applications.
#
# this package needs the 32-bit build environment
#
. /etc/profile.d/32dev.sh
#
# set your variables here
#
export ARCH=i586
#
# do the deed
#
echo "$DoName startup at `date`" |tee $LogNam
./$DoName 2>&1 |tee -a $LogNam
RetCode=$?
#
# log your results
#
echo "$DoName complete at `date` ... RetCode = $RetCode" |tee -a $LogNam
exit $RetCode
Last edited by kjhambrick; 09-19-2017 at 06:24 AM.
Reason: 1.17.s -> 1.17.2
I actually decided to go back to 14.2 as I have no need for -current(I was hoping amdgpu would be supporting my card, but apparently not yet). So sorry to have wasted your time on this issue.
However there was a problem with 14.2. After a fresh install and format of the root partition I did the usual update gpg, update, upgrade-all, clean-system, nothing else, and X would not start:
Code:
radeon: abi major version(20) doesn't match the server's version(23)
I don't know what the deal was there, but I just said "fuck it" and once again tried -current. Now OpenAL compiles without error. Before I had sbopkg set to use the master branch and I was mixing SBo and sbopkg. Perhaps that cause some incompatibility for OpenAL?
Regardless, I have current running stable now so I'm happy. Thank you all for the assistance.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.