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

[Jim Diamond]

On Wed, Jan  1, 2014 at 11:54 (-0500), xgizzmo wrote:

> It breaks Handbreak.

Hmmm... so it does.

Can anyone comment on whether this is a bug in the HandBreak build
process or whether it is a fundamental problem?

Cheers.

> On 12/31/13, Eric Hameleers (SBo) <alien at slackbuilds.org> wrote:
>> Jim Diamond schreef op 31-12-2013 16:44:
>>> On Mon, Dec 23, 2013 at 09:41 (-0600), Gerardo Zamudio wrote:

>>>> On Sun, Dec 22, 2013 at 1:16 PM, Jim Diamond <Jim.Diamond at acadiau.ca>
>>>> wrote:
>>>>> Gerardo,
>>>>> 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
>>>>> LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}"
>>>>> 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?
>>>>> Thanks.

>>>> I think the reason is simply because multilib is not Slackware standard,
>>>> and the scripts are meant for a stock Slackware installation. Perhaps a
>>>> SlackBuilds admin can better answer that question.
>>> No comments from On High?

>>> Can anyone point out a situation where adding
>>> 	LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}"
>>> to the configure is certainly/likely/possibly going to break something?

>>> Thanks.

>>> 				Jim

>> In my opinion, it _never_ hurts to have that in a SlackBuild.

>> Eric