Cant compile @kernel -> cryptsetup faild Unable to find kernel sources at /usr/src/linux

[gumtree.jack]

Im making fresh install and I have problem before building the kernel. After emerge -1 @kernel command there are installing depences like cryptsetup but it faild because it cannot find kernel in /usr/src/linux. Sounds logical because kernel will be next to install. Is it a bug or Im doing something bad?

 

 

/usr/lib64/libgcrypt.so.20: undefined reference to `gpg_err_code_from_syserror@GPG_ERROR_1.0'

/usr/lib64/libgcrypt.so.20: undefined reference to `gpg_err_code_from_errno@GPG_ERROR_1.0'

/usr/lib64/libgcrypt.so.20: undefined reference to `gpg_err_set_errno@GPG_ERROR_1.0'

/usr/lib64/libgcrypt.so.20: undefined reference to `gpg_strsource@GPG_ERROR_1.0'

/usr/lib64/libgcrypt.so.20: undefined reference to `gpg_strerror@GPG_ERROR_1.0'

collect2: error: ld returned 1 exit status

make[2]: *** [veritysetup] Error 1

make[2]: *** Waiting for unfinished jobs....

make[2]: Leaving directory `/var/tmp/portage/sys-fs/cryptsetup-1.6.5/work/cryptsetup-1.6.5/src'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/var/tmp/portage/sys-fs/cryptsetup-1.6.5/work/cryptsetup-1.6.5'

make: *** [all] Error 2

* ERROR: sys-fs/cryptsetup-1.6.5 failed (compile phase):

* emake failed

*

* If you need support, post the output of `emerge --info '=sys-fs/cryptsetup-1.6.5'`,

* the complete build log and the output of `emerge -pqv '=sys-fs/cryptsetup-1.6.5'`.

* The complete build log is located at '/var/tmp/portage/sys-fs/cryptsetup-1.6.5/temp/build.log'.

* The ebuild environment file is located at '/var/tmp/portage/sys-fs/cryptsetup-1.6.5/temp/environment'.

* Working directory: '/var/tmp/portage/sys-fs/cryptsetup-1.6.5/work/cryptsetup-1.6.5'

* S: '/var/tmp/portage/sys-fs/cryptsetup-1.6.5/work/cryptsetup-1.6.5'

 

>>> Failed to emerge sys-fs/cryptsetup-1.6.5, Log file:

 

>>> '/var/tmp/portage/sys-fs/cryptsetup-1.6.5/temp/build.log'

 

* Messages for package sys-fs/cryptsetup-1.6.5:

 

* Unable to find kernel sources at /usr/src/linux

* Unable to calculate Linux Kernel version for build, attempting to use running version

* ERROR: sys-fs/cryptsetup-1.6.5 failed (compile phase):

* emake failed

*

* If you need support, post the output of `emerge --info '=sys-fs/cryptsetup-1.6.5'`,

* the complete build log and the output of `emerge -pqv '=sys-fs/cryptsetup-1.6.5'`.

* The complete build log is located at '/var/tmp/portage/sys-fs/cryptsetup-1.6.5/temp/build.log'.

* The ebuild environment file is located at '/var/tmp/portage/sys-fs/cryptsetup-1.6.5/temp/environment'.

* Working directory: '/var/tmp/portage/sys-fs/cryptsetup-1.6.5/work/cryptsetup-1.6.5'

* S: '/var/tmp/portage/sys-fs/cryptsetup-1.6.5/work/cryptsetup-1.6.5'

 

[Deklan?]

Why do not you lower your kernel sources in the common way?

In my case:

# USE="bfsonly" emerge -pqv =sys-kernel/ck-sources-3.18.3

Look what happens to me with cryptsetup:

# emerge -pqv cryptsetup

!!! Problem resolving dependencies for sys-fs/cryptsetup

!!! The ebuild selected to satisfy "cryptsetup" has unmet requirements.
- sys-fs/cryptsetup-1.6.7::gentoo USE="gcrypt nls openssl python udev -kernel -nettle -pwquality -reencrypt -static -static-libs -urandom" ABI_X86="64" PYTHON_SINGLE_TARGET="python2_7 -python3_3 -python3_4" PYTHON_TARGETS="python2_7 python3_3 python3_4"

  The following REQUIRED_USE flag constraints are unsatisfied:
    exactly-one-of ( gcrypt kernel nettle openssl )

  The above constraints are a subset of the following complete expression:
    exactly-one-of ( gcrypt kernel nettle openssl ) python? ( exactly-one-of ( python_single_target_python3_3 python_single_target_python3_4 python_single_target_python2_7 ) python_single_target_python3_3? ( python_targets_python3_3 ) python_single_target_python3_4? ( python_targets_python3_4 ) python_single_target_python2_7? ( python_targets_python2_7 ) ) static? ( !gcrypt )

[gumtree.jack]

I was doing stable installation with Funtoo Install guide. I tried current branch for i7 and kernel compiled without any problems so it must be a bug. Now I have other problem :)

[drobbins]

This looks like a bug and should be reported. Someone finally did it: https://bugs.funtoo.org/browse/FL-2368

[drobbins]

Committed a fix that is on the way to the Portage tree...