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

Jim Diamond Jim.Diamond at acadiau.ca
Sun Dec 22 19:16:40 UTC 2013

On Sat Dec 21 18:09:15 UTC 2013, Gerardo Zamudio wrote

> On Sat, Dec 21, 2013 at 11:30 AM, Jim Diamond <Jim.Diamond at acadiau.ca>wrote:

>> libtool: link: ( cd "ltdl/.libs" && rm -f "libltdlc.la" && ln -s
>> "../libltdlc.la" "libltdlc.la" )
>> /usr/bin/grep: /usr/lib/liblzma.la: No such file or directory
>> /usr/bin/sed: can't read /usr/lib/liblzma.la: No such file or directory
>> libtool: link: `/usr/lib/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/


thanks very much for that info.

In the bigger picture, while I can appreciate that the multilib setup
is not "officially supported", I am wondering if there is any danger
to adding 
to the slackbuild template (and to most slackbuilds).

That is, if
(a) it doesn't break anything on non-multilib systems, and
(b) it makes more slackbuilds work on multilib systems
then aside from one more line of code, is there any harm?



More information about the SlackBuilds-users mailing list