On Sat, Jan 3, 2015 at 5:10 PM, Ryan P.C. McQuen wrote:
>
> On Jan 3, 2015 4:32 PM, "Larry Hajali" 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 ha
On Jan 3, 2015 4:32 PM, "Larry Hajali" 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/co
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.
--Larry
On Wed, Dec 17, 2014 at 4:53 PM, B Watson wrote:
> On 12/17/14, Ryan P.C. McQuen wrote:
> > Furthermore, does someone know a better
On 12/17/14, Ryan P.C. McQuen 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
I maintain apulse, which has a COMPAT32=yes switch. I'm wondering how
everyone feels about putting a check for compat32 into the SlackBuild,
and the best way to do that.
I was thinking something like this:
if [ ! -z '$( find /var/log/packages/ -name "*compat32*" -print )' ]; then
export COMPAT3
