[Slackbuilds-users] libheif / cargo-c compiling problem

Jim zsd+slackbuilds at jdvb.ca
Sat Nov 18 14:42:28 UTC 2023

In case anyone else runs into this issue, here is a work-around.

On a whim, rather than running
        sboupgrade libheif
which starts by compiling cargo-c, I did
        sboupgrade cargo-c
by itself, and in this case it successfully compiled and built the package.
After that I ran 'sboupgrade libheif' and it worked as expected.

So now I wonder whether people who successfully upgraded to the latest
libheif already had cargo-c installed for some other reason, and thus
didn't need to compile it as a dependency of libheif.

I also wonder why sboupgrade does something different when building cargo-c
directly, as opposed to building it as a dependency of libheif.


On Mon, Nov  6, 2023 at 10:41 (-0400), Jim wrote:

> Alexander and Willy,

> thanks for your replies.

> I tried it inside a S64-15.0 vbox VM, but got the same complaint.
> Presumably I have done the same Bad Thing inside the VM as I have in my
> bare-iron installation.

> I guess I have a project for a rainy day... :-(

> Jim

> On Sun, Nov  5, 2023 at 00:10 (+0300), Alexander Verbovetsky wrote:

>> On Sat, Nov 04, 2023 at 05:31:20PM -0300, Jim wrote:
>>> Using Slackware64 15.0...

>>> After today's updates, I tried to sboupgrade libheif, and the first thing
>>> sboupgrade wanted to do was to build cargo-c.  After downloading many
>>> files, it unpacks cargo-c and then whines thusly:

>>> ...
>>> cargo-c-0.9.27/src/config.rs
>>> cargo-c-0.9.27/src/install.rs
>>> cargo-c-0.9.27/src/lib.rs
>>> cargo-c-0.9.27/src/pkg_config_gen.rs
>>> cargo-c-0.9.27/src/target.rs
>>> tar: /usr/sbo/repo/development/cargo-c/addr2line-0.19.0.crate: Cannot open: No such file or directory
>>> tar: Error is not recoverable: exiting now
>>> Failure encountered while building cargo-c:
>>> cargo-c.SlackBuild return non-zero

>>> Do you want to proceed? [n]
>>> Failures:
>>> cargo-c: cargo-c.SlackBuild return non-zero

>>> Perhaps there is something peculiar on my system, but before I go on the
>>> hunt, can anyone in slackbuild land tell me whether their 64-bit 15.0
>>> system is happy about compiling libheif?

>> libheif has several new dependencies, one of them is rav1e, which in
>> turn depends on cargo-c. Both are Rust packages and require rust16
>> during the build.

>> I have successfully tested everything on a clean 64-bit version of 15.0.

>> It's strange that cargo-c wants addr2line, it's not its dependency.
>> rav1e requires addr2line.

>> Best regards,
>> Alexander

More information about the SlackBuilds-users mailing list