| Summary: | sys-fs/cryfs-0.9.7: ninja: error: 'vendor/scrypt/src/scrypt_original-build/libscrypt_sse2.a', needed by 'src/cryfs-cli/cryfs', missing and no known rule to make it | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Nathan Caldwell <saintdev> |
| Component: | Current packages | Assignee: | adebeus |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | proxy-maint |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | sys-fs-cryfs-0.9.8-build.log | ||
|
Description
Nathan Caldwell
2017-10-16 00:31:36 UTC
confirmed, doesn't build here too : >>> Working in BUILD_DIR: "/var/tmp/portage/sys-fs/cryfs-0.9.7/work/cryfs-0.9.7_build" ninja -v -j3 -l0 ninja: error: 'vendor/scrypt/src/scrypt_original-build/libscrypt_sse2.a', needed by 'src/cryfs-cli/cryfs', missing and no known rule to make it * ERROR: sys-fs/cryfs-0.9.7::gentoo failed (compile phase): * ninja -v -j3 -l0 failed tfoerste@t44 ~ $ emerge --info sys-fs/cryfs Portage 2.3.19 (python 2.7.14-final-0, default/linux/amd64/17.0/hardened, gcc-6.4.0, glibc-2.25-r9, 4.14.14 x86_64) ================================================================= System Settings ================================================================= System uname: Linux-4.14.14-x86_64-Intel-R-_Core-TM-_i5-4300U_CPU_@_1.90GHz-with-gentoo-2.4.1 KiB Mem: 12006080 total, 650516 free KiB Swap: 16777212 total, 16777212 free Timestamp of repository gentoo: Sun, 21 Jan 2018 14:51:02 +0000 Head commit of repository gentoo: 50ff4142863972a7c9e93921ce4c9b25d3b66215 sh bash 4.4_p12 ld GNU ld (Gentoo 2.29.1 p3) 2.29.1 app-shells/bash: 4.4_p12::gentoo dev-java/java-config: 2.2.0-r3::gentoo dev-lang/perl: 5.24.3::gentoo dev-lang/python: 2.7.14-r1::gentoo, 3.5.4-r1::gentoo dev-util/cmake: 3.9.6::gentoo dev-util/pkgconfig: 0.29.2::gentoo sys-apps/baselayout: 2.4.1-r2::gentoo sys-apps/openrc: 0.34.11::gentoo sys-apps/sandbox: 2.12::gentoo sys-devel/autoconf: 2.13::gentoo, 2.69-r4::gentoo sys-devel/automake: 1.15.1-r1::gentoo sys-devel/binutils: 2.29.1-r1::gentoo sys-devel/gcc: 6.4.0-r1::gentoo sys-devel/gcc-config: 1.8-r1::gentoo sys-devel/libtool: 2.4.6-r3::gentoo sys-devel/make: 4.2.1::gentoo sys-kernel/linux-headers: 4.13::gentoo (virtual/os-headers) sys-libs/glibc: 2.25-r9::gentoo Repositories: Same problem for me. The issue is that ninja doesn't work, so I presume it's really a bug in ninja, not cryfs. Bypass is not to use CMAKE_MAKEFILE_GENERATOR="emake" instead of CMAKE_MAKEFILE_GENERATOR="ninja" I have an override in /etc/portage/env to use on picky ebuilds like this. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4711906580f34d5726060a07460238b8e4f4b686 commit 4711906580f34d5726060a07460238b8e4f4b686 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2018-08-11 17:03:05 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2018-08-11 17:03:05 +0000 sys-fs/cryfs: always use emake Bug: https://bugs.gentoo.org/634392 Package-Manager: Portage-2.3.45_p0_p305925, Repoman-2.3.10_p30_p305925 sys-fs/cryfs/cryfs-0.9.7.ebuild | 1 + sys-fs/cryfs/cryfs-0.9.9.ebuild | 1 + sys-fs/cryfs/cryfs-9999.ebuild | 1 + 3 files changed, 3 insertions(+) Fixed, then? |
