[Slackbuilds-users] slackbuild(s) failing on S14.1-64 when compat32 installed

King Beowulf kingbeowulf at gmail.com
Sat Dec 21 19:26:10 UTC 2013

Hash: SHA1

On 12/21/2013 10:09 AM, Gerardo Zamudio wrote:
> On Sat, Dec 21, 2013 at 11:30 AM, Jim Diamond
> <Jim.Diamond at acadiau.ca <mailto:Jim.Diamond at acadiau.ca>> wrote:
> libtool: link: ( cd "ltdl/.libs" && rm -f "libltdlc.la 
> <http://libltdlc.la>" && ln -s "../libltdlc.la
> <http://libltdlc.la>" "libltdlc.la <http://libltdlc.la>" ) 
> /usr/bin/grep: /usr/lib/liblzma.la <http://liblzma.la>: No such
> file or directory /usr/bin/sed: can't read /usr/lib/liblzma.la
> <http://liblzma.la>: No such file or directory libtool: link:
> `/usr/lib/liblzma.la <http://liblzma.la>' is not a valid libtool
> archive make[1]: *** [magick/libGraphicsMagick.la] Error 1 make[1]:
> *** Waiting for unfinished jobs.... make[1]: Leaving directory
> `/tmp/SBo/GraphicsMagick-1.3.17' make: *** [all] Error 2
> Hello,
> Multilib is not officially supported, but you need to add 
> LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \ before the CFLAGS and
> CXXFLAGS lines in the configure script. Check out #18 on the FAQ
> at http://slackbuilds.org/faq/

There are a number of occasions that, to compile x86_64 on multilib,
you have to adjust the scripts as above.  (This was very common under
SLAMD64).  However, I suggest it is best (and cleaner) to compile and
build packages on a pure Slackware64 environment. Either have a build
box, or use a qemu or virtualbox VM.

- -Ed

Version: GnuPG v2.0.22 (GNU/Linux)


More information about the SlackBuilds-users mailing list