[Slackbuilds-users] COMPAT32 question
Ryan P.C. McQuen
ryan.q at linux.com
Sun Jan 4 01:10:22 UTC 2015
<ryanpcmcquen.com>
On Jan 3, 2015 4:32 PM, "Larry Hajali" <larryhaja at gmail.com> wrote:
>
> Has this been signed off by the SBo admins? I see that apulse now has
the "[ -e /lib/libc.so.6 ] && COMPAT32="${COMPAT32:-yes}" check in the
ready queue.
>
Actually it has been live on SBo since 12.20:
http://slackbuilds.org/cgit/slackbuilds/commit/?id=58e9ea52ff1b6b018bd0d601e43fbeb4800ff5e2
> --Larry
>
> On Wed, Dec 17, 2014 at 4:53 PM, B Watson <yalhcru at gmail.com> wrote:
>>
>> On 12/17/14, Ryan P.C. McQuen <ryan.q at linux.com> wrote:
>> > Furthermore, does someone know a better way to perform this check.
>> > Maybe I should be relying on checking glibc or gcc ...
>>
>> That's what I'd do. In the section that checks ARCH:
>>
>> ...
>> elif [ "$ARCH" = "x86_64" ]; then
>> SLKCFLAGS="-O2 -fPIC"
>> LIBDIRSUFFIX="64"
>> [ -e /lib/libc.so.6 ] && COMPAT32="${COMPAT32:-yes}"
>> else
>> ...
>>
>> Doing it that way will autodetect, but still allow the user to override
>> with COMPAT32=no in the environment. It also avoids the use of find,
>> which is kinda slow and heavy.
>>
>> As to whether it's a good idea... I don't see why not. The existing
>> apulse.SlackBuild already has multilib-specific code, this just automates
>> enabling it (instead of user having to manually COMPAT32=yes).
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - http://slackbuilds.org/faq/
>>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20150103/e19dd6d9/attachment.html>
More information about the SlackBuilds-users
mailing list