-s/--step, it cleaned a specific step in the part lifecycle (pull, build, stage, or prime). You’re right, that feature no longer exists. You can clean specific parts completely (snapcraft clean <part>), but for the most part snapcraft should be smart enough to determine when individual lifecycle steps need to be cleaned. I’m curious why a build script would be doing this, that feature was normally used during a development iteration (clean something, run it again, etc.)-- can you give a little context so we can help get you to a happy place?
I’m currently re-running the script. What it’s doing is building an image for a specific hardware platform. It appears that that particular step would clean the entire build step, kernel and all, and re-clone and compile the kernel from scratch. This is going to take a hot sec
UPDATE: Now getting this error:
Issues while validating snapcraft.yaml: must be one of base: <base> and type: <app|gadget>, base: bare (with a build-base), or type: <base|kernel|snapd> (without a base)
Snapcraft runs ldd on ELF files to try and understand what libs are required for various reasons. Sounds like ldd is exiting non-zero on that file. That isn’t unheard of, it’s just a warning, but you can try running ldd on it yourself and see what it says (I’m curious as well). Are you noticing problems as a result of this?