Здравствуйте, после последнего обновления перестали собираться некоторые пакеты.
Код:
make[2]: выход из каталога «/var/tmp/portage/dev-libs/libcec-3.1.0-r1/work/libcec-3.1.0_build»
[ 97%] Built target cecc-client
[100%] Linking CXX executable cec-client
cd /var/tmp/portage/dev-libs/libcec-3.1.0-r1/work/libcec-3.1.0_build/src/cec-client && /usr/bin/cmake -E cmake_link_script CMakeFiles/cec-client.dir/link.txt --verbose=1
/usr/bin/x86_64-pc-linux-gnu-g++ -O2 -pipe -std=c++11 -Wl,-O1 -Wl,--as-needed CMakeFiles/cec-client.dir/cec-client.cpp.o CMakeFiles/cec-client.dir/curses/CursesControl.cpp.o -o cec-client-3.1.0 -rdynamic -L/usr/lib64 -lp8-platform -lpthread -lpthread -ldl -lcurses -lrt
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/../../../../x86_64-pc-linux-gnu/bin/ld: CMakeFiles/cec-client.dir/curses/CursesControl.cpp.o: неопределённая ссылка на символ «keypad»
/lib64/libtinfo.so.6: error adding symbols: DSO missing from command line
collect2: ошибка: выполнение ld завершилось с кодом возврата 1
make[2]: *** [src/cec-client/CMakeFiles/cec-client.dir/build.make:121: src/cec-client/cec-client-3.1.0] Ошибка 1
make[2]: выход из каталога «/var/tmp/portage/dev-libs/libcec-3.1.0-r1/work/libcec-3.1.0_build»
make[1]: *** [CMakeFiles/Makefile2:86: src/cec-client/CMakeFiles/cec-client.dir/all] Ошибка 2
make[1]: выход из каталога «/var/tmp/portage/dev-libs/libcec-3.1.0-r1/work/libcec-3.1.0_build»
make: *** [Makefile:128: all] Ошибка 2
* ERROR: dev-libs/libcec-3.1.0-r1::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=dev-libs/libcec-3.1.0-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-libs/libcec-3.1.0-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-libs/libcec-3.1.0-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/libcec-3.1.0-r1/temp/environment'.
* Working directory: '/var/tmp/portage/dev-libs/libcec-3.1.0-r1/work/libcec-3.1.0_build'
* S: '/var/tmp/portage/dev-libs/libcec-3.1.0-r1/work/libcec-libcec-3.1.0'
>>> Failed to emerge dev-libs/libcec-3.1.0-r1, Log file:
>>> '/var/tmp/portage/dev-libs/libcec-3.1.0-r1/temp/build.log'
* Messages for package dev-libs/libcec-3.1.0-r1:
* ERROR: dev-libs/libcec-3.1.0-r1::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=dev-libs/libcec-3.1.0-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-libs/libcec-3.1.0-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-libs/libcec-3.1.0-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-libs/libcec-3.1.0-r1/temp/environment'.
* Working directory: '/var/tmp/portage/dev-libs/libcec-3.1.0-r1/work/libcec-3.1.0_build'
* S: '/var/tmp/portage/dev-libs/libcec-3.1.0-r1/work/libcec-libcec-3.1.0'
Грешу на GCC.
Пробовал обновлять GCC по этой инструкции. Но ошибка ни куда не уходит.
Здравствуйте. Пришлось открыть тему снова.
Пришло обновление GCC-5.4.0, сдуру установил его. И теперь не собираются пакеты: GLIBC
Код:
CPP='x86_64-pc-linux-gnu-gcc -m32 -Wl,-O1 -Wl,--as-needed -E -x c-header' /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/cross-rpcgen -Y ../scripts -c rpcsvc/bootparam_prot.x -o /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/xbootparam_prot.T
CPP='x86_64-pc-linux-gnu-gcc -m32 -Wl,-O1 -Wl,--as-needed -E -x c-header' /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/cross-rpcgen -Y ../scripts -c rpcsvc/nlm_prot.x -o /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/xnlm_prot.T
/bin/sh: /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/cross-rpcgen: Нет такого файла или каталога
make[2]: *** [Makefile:203: /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/xnlm_prot.stmp] Ошибка 127
make[2]: *** Ожидание завершения заданий…
/bin/sh: /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/cross-rpcgen: Нет такого файла или каталога
make[2]: *** [Makefile:203: /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/xbootparam_prot.stmp] Ошибка 127
mkdir -p -- /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/rpcsvc
CPP='x86_64-pc-linux-gnu-gcc -m32 -Wl,-O1 -Wl,--as-needed -E -x c-header' /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/cross-rpcgen -Y ../scripts -h rpcsvc/bootparam_prot.x -o /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/rpcsvc/bootparam_prot.T
/bin/sh: /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/cross-rpcgen: Нет такого файла или каталога
make[2]: *** [Makefile:194: /var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl/sunrpc/rpcsvc/bootparam_prot.stmp] Ошибка 127
make[2]: выход из каталога «/var/tmp/portage/sys-libs/glibc-2.23-r3/work/glibc-2.23/sunrpc»
make[1]: *** [Makefile:215: sunrpc/others] Ошибка 2
make[1]: выход из каталога «/var/tmp/portage/sys-libs/glibc-2.23-r3/work/glibc-2.23»
make: *** [Makefile:9: all] Ошибка 2
make: выход из каталога «/var/tmp/portage/sys-libs/glibc-2.23-r3/work/build-x86-x86_64-pc-linux-gnu-nptl»
* ERROR: sys-libs/glibc-2.23-r3::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=sys-libs/glibc-2.23-r3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.23-r3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.23-r3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.23-r3/temp/environment'.
* Working directory: '/var/tmp/portage/sys-libs/glibc-2.23-r3/work/glibc-2.23'
* S: '/var/tmp/portage/sys-libs/glibc-2.23-r3/work/glibc-2.23'
>>> Failed to emerge sys-libs/glibc-2.23-r3, Log file:
>>> '/var/tmp/portage/sys-libs/glibc-2.23-r3/temp/build.log'
* Messages for package sys-libs/glibc-2.23-r3:
* Simple build failed ... assuming this is desired #324685
* Simple build failed ... assuming this is desired #324685
* Messages for package sys-libs/glibc-2.23-r3:
* ERROR: sys-libs/glibc-2.23-r3::gentoo failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=sys-libs/glibc-2.23-r3::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sys-libs/glibc-2.23-r3::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.23-r3/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.23-r3/temp/environment'.
* Working directory: '/var/tmp/portage/sys-libs/glibc-2.23-r3/work/glibc-2.23'
* S: '/var/tmp/portage/sys-libs/glibc-2.23-r3/work/glibc-2.23'
dimonchik230 dima #
suitesparseconfig
Код:
checking for a BSD-compatible install... /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
checking for i686-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc -m32
checking whether the C compiler works... no
configure: error: in `/var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/work/suitesparseconfig-4.2.1-abi_x86_32.x86':
configure: error: C compiler cannot create executables
See `config.log' for more details
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/work/suitesparseconfig-4.2.1-abi_x86_32.x86/config.log
* ERROR: sci-libs/suitesparseconfig-4.2.1-r1::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 115: Called src_configure
* environment, line 1399: Called multilib-minimal_src_configure
* environment, line 905: Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
* environment, line 1119: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 835: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 833: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
* environment, line 246: Called multilib-minimal_abi_src_configure
* environment, line 899: Called multilib_src_configure
* environment, line 1331: Called econf '--disable-static'
* phase-helpers.sh, line 665: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=sci-libs/suitesparseconfig-4.2.1-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sci-libs/suitesparseconfig-4.2.1-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/work/suitesparseconfig-4.2.1-abi_x86_32.x86'
* S: '/var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/work/suitesparseconfig-4.2.1'
>>> Failed to emerge sci-libs/suitesparseconfig-4.2.1-r1, Log file:
>>> '/var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/temp/build.log'
* Messages for package sci-libs/suitesparseconfig-4.2.1-r1:
* ERROR: sci-libs/suitesparseconfig-4.2.1-r1::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 115: Called src_configure
* environment, line 1399: Called multilib-minimal_src_configure
* environment, line 905: Called multilib_foreach_abi 'multilib-minimal_abi_src_configure'
* environment, line 1119: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 835: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_configure'
* environment, line 833: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_configure'
* environment, line 246: Called multilib-minimal_abi_src_configure
* environment, line 899: Called multilib_src_configure
* environment, line 1331: Called econf '--disable-static'
* phase-helpers.sh, line 665: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=sci-libs/suitesparseconfig-4.2.1-r1::gentoo'`,
* the complete build log and the output of `emerge -pqv '=sci-libs/suitesparseconfig-4.2.1-r1::gentoo'`.
* The complete build log is located at '/var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/work/suitesparseconfig-4.2.1-abi_x86_32.x86'
* S: '/var/tmp/portage/sci-libs/suitesparseconfig-4.2.1-r1/work/suitesparseconfig-4.2.1'
И даже libtool. Прямо мистика какая-то.
Устанавливал GCC так:
Код:
emerge -avu gcc
# gcc-config -l
[1] x86_64-pc-linux-gnu-4.9.4 *
[2] x86_64-pc-linux-gnu-5.4.0
# fix_libtool_file.sh 5.4.0
# gcc-config 2
# env-update && source /etc/profile
# emerge -av libtool --oneshot
И вот здесь выскакивает ошибка и libtool не собирается.
$ gcc -m32 -xc - <<<'main(){}'
<stdin>:1:1: предупреждение: по умолчанию возвращаемый тип функции - «int» [-Wimplicit-int]
$ ./a.out
bash: ./a.out: Нет такого файла или каталога
$ gcc -m32 -xc - <<<'main(){}'
<stdin>:1:1: предупреждение: по умолчанию возвращаемый тип функции - «int» [-Wimplicit-int]
$ ./a.out
bash: ./a.out: Нет такого файла или каталога
По какой-то причине gcc ожидает наличия 32-битного ld-linux в каталоге /lib, при том, что у вас /lib - это симлинк на /lib64, а не /lib32. Я не знаю, откуда такое несоответствие. Я давно не пользовался multilib-профилем, но разве /lib в нём не должен быть симлинком на /lib32?
С другой стороны, я боюсь, что если перенаправить этот симлинк, то могут вылезти другие проблемы.
В качестве обходного пути, попробуйте подложить в /lib симлинк на 32-битный ld-linux:
Shell
# ln -s /lib32/ld-linux.so.2 /lib/ld-linux.so.2
Довольно грубый хак, который пытается обойти проблему вместо её решения, но, возможно, поможет.
Я давно не пользовался multilib-профилем, но разве /lib в нём не должен быть симлинком на /lib32?
/lib с самого начала был симликом на /lib64.
Я сделал как написали и пока сборка пакетов пошла. Если будут ошибки напишу.
В добавление ldd a.out теперь показывает.
checking boost/program_options.hpp presence... yes
checking for boost/program_options.hpp... yes
checking for the Boost program_options library... no
configure: error: cannot find the flags to link with Boost program_options
!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/dev-cpp/libcmis-0.5.2_pre20160820/work/libcmis-da8c3fdc281a0cb3753a6bb9eaa63ac6385e2963/config.log
* ERROR: dev-cpp/libcmis-0.5.2_pre20160820::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 115: Called src_configure
* environment, line 1771: Called econf '--program-suffix=-0.5' '--disable-werror' '--without-man' '--disable-static' '--disable-tests' '--enable-client'
* phase-helpers.sh, line 665: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=dev-cpp/libcmis-0.5.2_pre20160820::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-cpp/libcmis-0.5.2_pre20160820::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-cpp/libcmis-0.5.2_pre20160820/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-cpp/libcmis-0.5.2_pre20160820/temp/environment'.
* Working directory: '/var/tmp/portage/dev-cpp/libcmis-0.5.2_pre20160820/work/libcmis-da8c3fdc281a0cb3753a6bb9eaa63ac6385e2963'
* S: '/var/tmp/portage/dev-cpp/libcmis-0.5.2_pre20160820/work/libcmis-da8c3fdc281a0cb3753a6bb9eaa63ac6385e2963'
>>> Failed to emerge dev-cpp/libcmis-0.5.2_pre20160820, Log file:
>>> '/var/tmp/portage/dev-cpp/libcmis-0.5.2_pre20160820/temp/build.log'
* Messages for package media-fonts/liberation-fonts-2.00.1-r1:
* The following fontconfig configuration files have been installed:
*
* 60-liberation.conf
*
* Use `eselect fontconfig` to enable/disable them.
* Messages for package dev-cpp/libcmis-0.5.2_pre20160820:
* ERROR: dev-cpp/libcmis-0.5.2_pre20160820::gentoo failed (configure phase):
* econf failed
*
* Call stack:
* ebuild.sh, line 115: Called src_configure
* environment, line 1771: Called econf '--program-suffix=-0.5' '--disable-werror' '--without-man' '--disable-static' '--disable-tests' '--enable-client'
* phase-helpers.sh, line 665: Called __helpers_die 'econf failed'
* isolated-functions.sh, line 117: Called die
* The specific snippet of code:
* die "$@"
*
* If you need support, post the output of `emerge --info '=dev-cpp/libcmis-0.5.2_pre20160820::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-cpp/libcmis-0.5.2_pre20160820::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-cpp/libcmis-0.5.2_pre20160820/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-cpp/libcmis-0.5.2_pre20160820/temp/environment'.
* Working directory: '/var/tmp/portage/dev-cpp/libcmis-0.5.2_pre20160820/work/libcmis-da8c3fdc281a0cb3753a6bb9eaa63ac6385e2963'
* S: '/var/tmp/portage/dev-cpp/libcmis-0.5.2_pre20160820/work/libcmis-da8c3fdc281a0cb3753a6bb9eaa63ac6385e2963'
* GNU info directory index is up-to-date.
* IMPORTANT: 18 news items need reading for repository 'gentoo'.
* Use eselect news read to view new items.
Попробуйте обновить/пересобрать boost и boost-build
Уже, вроде только boost.
При сборке пакетов наблюдаю такую надпись, это страшно?
Код:
checking for the toolset name used by Boost for x86_64-pc-linux-gnu-g++... configure: WARNING: could not figure out which toolset name to use for x86_64-pc-linux-gnu-g++
Что "уже"? "Уже обновил, и заработало", "уже обновил, но не заработало", "уже проехали"? И что "только boost"? "Только boost обновился", "только boost остался", "только boost был установлен"?
При сборке пакетов наблюдаю такую надпись, это страшно?
Код:
checking for the toolset name used by Boost for x86_64-pc-linux-gnu-g++... configure: WARNING: could not figure out which toolset name to use for x86_64-pc-linux-gnu-g++
Не знаю, но, судя по тому, что у меня она тоже вылезает и проблем не вызывает, думаю, не страшно.
Что "уже"? "Уже обновил, и заработало", "уже обновил, но не заработало", "уже проехали"? И что "только boost"? "Только boost обновился", "только boost остался", "только boost был установлен"?
Достаточно было boost пересобрать и заработало. Извиняюсь не корректно написал.
Проблема была из за glibc установленного из оверлея. Благодаря помощи /dev/random, удалось таки собрать glibc:: gentoo, ну и boost тоже пришлось пересобрать. Тему пока не закрываю, может еще какие ошибки вылезут.
[ebuild U ] sys-apps/hwids-20170328::gentoo [20150717-r1::gentoo] USE="net pci udev usb" 2 002 KiB
[ebuild U ] virtual/perl-Encode-2.800.100_rc::gentoo [2.730.0-r1::gentoo] 0 KiB
[uninstall ] perl-core/Encode-2.730.0::gentoo
[blocks b ] <perl-core/Encode-2.800.100_rc ("<perl-core/Encode-2.800.100_rc" is blocking virtual/perl-Encode-2.800.100_rc)
Total: 49 packages (44 upgrades, 1 new, 2 in new slots, 2 reinstalls, 1 uninstall), Size of downloads: 222 855 KiB
Conflict: 1 block
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-lang/perl:0
(dev-lang/perl-5.24.1-r1:0/5.24::gentoo, ebuild scheduled for merge) pulled in by
=dev-lang/perl-5.24* required by (virtual/perl-MIME-Base64-3.150.0-r2:0/0::gentoo, installed)
^ ^^^^^
(and 20 more with the same problem)
(dev-lang/perl-5.22.3_rc4:0/5.22::gentoo, installed) pulled in by
dev-lang/perl:0/5.22= required by (virtual/perl-Exporter-5.720.0-r2:0/0::gentoo, installed)
^^^^^^^^
(and 46 more with the same problem)
NOTE: Use the '--verbose-conflicts' option to display parents omitted above
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.
For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.
mail ~ # emerge -auv perl
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] dev-lang/perl-5.24.1-r1:0/5.24::gentoo [5.22.3_rc4:0/5.22::gentoo] USE="berkdb gdbm -debug -doc -ithreads" 11 414 KiB
Total: 1 package (1 upgrade), Size of downloads: 11 414 KiB
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-lang/perl:0
(dev-lang/perl-5.24.1-r1:0/5.24::gentoo, ebuild scheduled for merge) pulled in by
=dev-lang/perl-5.24* required by (virtual/perl-MIME-Base64-3.150.0-r2:0/0::gentoo, installed)
^ ^^^^^
dev-lang/perl (Argument)
(and 7 more with the same problems)
(dev-lang/perl-5.22.3_rc4:0/5.22::gentoo, installed) pulled in by
=dev-lang/perl-5.22.3* required by (virtual/perl-Storable-2.530.200_rc:0/0::gentoo, installed)
^ ^^^^^^^
dev-lang/perl:0/5.22= required by (virtual/perl-Digest-MD5-2.540.0-r2:0/0::gentoo, installed)
^^^^^^^^
(and 71 more with the same problems)
NOTE: Use the '--verbose-conflicts' option to display parents omitted above
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in
the dependencies of two different packages, then those packages can
not be installed simultaneously. You may want to try a larger value of
the --backtrack option, such as --backtrack=30, in order to see if
that will solve this conflict automatically.
For more information, see MASKED PACKAGES section in the emerge man
page or refer to the Gentoo Handbook.
Так предлагает. Но не значит ли это что все пакеты он обновит до нестабильного релиза? За что отвечает ключ backtrak-9999?
Разбор зависимостей с блокировками - NP-полная задача. В особо неудачных случаях её решение может занять тысячелетия. Поэтому emerge ограничивает пространство поиска решений. Опция backtrack указывает, насколько далеко можно отходить от "прямого маршрута", не пытающегося обходить блокировки, а сразу вываливающегося с ошибкой. Значение по умолчанию - 3.