ORBit2 Slackbuild fails when building 32 bit package on current multilib
I am trying to build ORBit2 as a dependency for GConf and then google-chrome. This is a multilib system and I want 32 bit chrome. Both my 64 bit and compat32 packages are all current as of today per ftp://slackware.mirrors.tds.net/pub/slackware/. I have edited the Slackbuild as follows:
Code:
PRGNAM=ORBit2 Code:
/usr/lib64/gcc/x86_64-slackware-linux/4.4.3/../../../../x86_64-slackware-linux/bin/ld: skipping incompatible /usr/lib64/gcc/x86_64-slackware-linux/4.4.3/../../../libIDL-2.so when searching for -lIDL-2 I have run: Code:
. /etc/profile.d/32dev.sh |
Quote:
This is how I would build a 32-bit packages for my 64-bit multilib system:
It works every time. I run 64-bit Slackware, and I have 32-bit Slackware in a VirtualBox virtual machine. The -LIDL-2 error is exactly what I got when I tried to build a 32-bit Firefox package from source on my 64-bit system. Building it on my 32-bit system worked. |
Does using this work?:
SLKCFLAGS="-m32 -O2" |
just guessing, haven't tried it myself, but I think you need to install a libidl-compat32 package as a dependency for building ORBit2.
from a root prompt Code:
cd /tmp |
Quote:
Code:
SLKCFLAGS="-O2 -mtune=i686" I guess I should start a new thread for the last bit of 32 bit google-chrome on multiltib PITAness which is that I can't access of all things gmail.com due to ssl failure. I've managed to get the internal flash going. |
All times are GMT -5. The time now is 05:49 PM. |