>> I am the former aom maintainer for Sbo and when I looked after the 
>> script I also kept a tarball on my personal web space. If there is a
>> new maintainer they will need to do the same I suspect; that web
>> space no longer exists...
>> 
>> Andrew
>> 
>> On Sun, 5 July 2026, 12:02 KB_SBo, <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>>     Hello
>> 
>>     aom-3.60:
>> 
>>     expected: 4c73a44a710688e8c496b3740ecee84b
>>     found: d41d8cd98f00b204e9800998ecf8427e
>> 
>>     reason:  source file is EMPTY - unable to download via wget or
>> HTTP
>> 
>>     -Ed
>
>Andrew,
>
>No worries; aom is now included in Slackware-current going forward.  I 
>took over for the time being and updated the version. Archive is now
>on Sourceforge SBo links.

Ed, 

please follow the SlackBuild templates when you take over

please remove this part
NUMJOBS=${NUMJOBS:-" -j $(expr $(nproc) + 1) "}
make $NUMJOBS || make || exit 1

the previous code was -j1
that's probably there for a reason
https://git.slackbuilds.org/slackbuilds/commit/?id=38dee70ccd621e9a078a4cb4f0e3847703f694f5

also the comments here
# Automatically determine the architecture we're building on:
# Unless $ARCH is already set, use uname -m for all other archs:

# If the variable PRINT_PACKAGE_NAME is set, then this script will
# report what +# the name of the created package would be, and then
exit. This information +
# could be useful to other scripts.

--
Willy Sudiarto Raharjo

Attachment: pgp8q6RDOy3Mh.pgp
Description: OpenPGP digital signature

_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Reply via email to