futility: Work around clang/GCC problem with libzip headers
futility: Work around clang/GCC problem with libzip headers

I don't even want to get into why this is needed. I'm so tired of
having to deal with new clang-specific toolchain bullshit 2-3 times a
year. libzip did this

https://github.com/nih-at/libzip/commit/1d949dd77339fb59605dc8f3a30f76604d693795

and then we upreved to it in CL:2245845 and now building upstream
coreboot in a Chrome OS chroot is broken.

I have to get back to wasting time on the other three random things
that broke when I ran repo sync, so someone please just approve...

BRANCH=None
BUG=None
TEST=None

Signed-off-by: Julius Werner <4d12f06cff3725783b352157673a720bc67c4afe@chromium.org>
Change-Id: Ic578e8f8e47f7fafd98d8c3148cbe24d9156886b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/vboot_reference/+/2366053
Reviewed-by: Hung-Te Lin <8a7fce4940baad93a69f5073b383c85deed9d9c4@chromium.org>
Reviewed-by: Mike Frysinger <8f3f75c74bd5184edcfa6534cab3c13a00a2f794@chromium.org>

coreboot/vboot,coreboot/vboot,coreboot/vboot,coreboot/vboot,coreboot/vboot