viniciusalmeida
(usa Slackware)
Enviado em 03/03/2013 - 19:50h
eu acho que é coisa no meu pc mesmo, pq ja tinha dado um problema parecido qndo fui instalar um outro pct:
(instalação do samsung-unified driver)
virtual memory exhausted: Não foi possível alocar memória
make[2]: ** [Source/CMakeFiles/CMakeLib.dir/cmMakefile.cxx.o] Erro 1
make[2]: *** Esperando que os outros processos terminem....
make[1]: ** [Source/CMakeFiles/CMakeLib.dir/all] Erro 2
make: ** [all] Erro 2
* ERROR: dev-util/cmake-2.8.10.2-r1 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=dev-util/cmake-2.8.10.2-r1'`,
* the complete build log and the output of `emerge -pqv '=dev-util/cmake-2.8.10.2-r1'`.
* The complete build log is located at '/var/tmp/portage/dev-util/cmake-2.8.10.2-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-util/cmake-2.8.10.2-r1/temp/environment'.
* Working directory: '/var/tmp/portage/dev-util/cmake-2.8.10.2-r1/work/cmake-2.8.10.2_build'
* S: '/var/tmp/portage/dev-util/cmake-2.8.10.2-r1/work/cmake-2.8.10.2'
>>> Failed to emerge dev-util/cmake-2.8.10.2-r1, Log file:
>>> '/var/tmp/portage/dev-util/cmake-2.8.10.2-r1/temp/build.log'
* Messages for package dev-util/cmake-2.8.10.2-r1:
* ERROR: dev-util/cmake-2.8.10.2-r1 failed (compile phase):
* emake failed
*
* If you need support, post the output of `emerge --info '=dev-util/cmake-2.8.10.2-r1'`,
* the complete build log and the output of `emerge -pqv '=dev-util/cmake-2.8.10.2-r1'`.
* The complete build log is located at '/var/tmp/portage/dev-util/cmake-2.8.10.2-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-util/cmake-2.8.10.2-r1/temp/environment'.
* Working directory: '/var/tmp/portage/dev-util/cmake-2.8.10.2-r1/work/cmake-2.8.10.2_build'
* S: '/var/tmp/portage/dev-util/cmake-2.8.10.2-r1/work/cmake-2.8.10.2'
* GNU info directory index is up-to-date.
* IMPORTANT: 8 news items need reading for repository 'gentoo'.
* Use eselect news to read news item
_________________
além disso, em um sudo emerge sys-devel/gcc :
virtual memory exhausted: Não foi possível alocar memória
make[3]: ** [insn-recog.o] Erro 1
make[3]: *** Esperando que os outros processos terminem....
make[2]: ** [all-stage2-gcc] Erro 2
make[1]: ** [stage2-bubble] Erro 2
make: ** [bootstrap-lean] Erro 2
emake failed
* ERROR: sys-devel/gcc-4.7.2-r1 failed (compile phase):
* emake failed with bootstrap-lean
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 4104: Called toolchain_src_compile
* environment, line 4767: Called gcc_do_make
* environment, line 2403: Called die
* The specific snippet of code:
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
*
* If you need support, post the output of `emerge --info '=sys-devel/gcc-4.7.2-r1'`,
* the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.7.2-r1'`.
*
* Please include /var/tmp/portage/sys-devel/gcc-4.7.2-r1/work/build/gcc-build-logs.tar.bz2 in your bug report
*
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.7.2-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.7.2-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-devel/gcc-4.7.2-r1/work/build'
* S: '/var/tmp/portage/sys-devel/gcc-4.7.2-r1/work/build'
>>> Failed to emerge sys-devel/gcc-4.7.2-r1, Log file:
>>> '/var/tmp/portage/sys-devel/gcc-4.7.2-r1/temp/build.log'
* Messages for package sys-devel/gcc-4.7.2-r1:
*
* LTO support is still experimental and unstable.
* Any bugs resulting from the use of LTO will not be fixed.
*
* ERROR: sys-devel/gcc-4.7.2-r1 failed (compile phase):
* emake failed with bootstrap-lean
*
* Call stack:
* ebuild.sh, line 93: Called src_compile
* environment, line 4104: Called toolchain_src_compile
* environment, line 4767: Called gcc_do_make
* environment, line 2403: Called die
* The specific snippet of code:
* emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}";
*
* If you need support, post the output of `emerge --info '=sys-devel/gcc-4.7.2-r1'`,
* the complete build log and the output of `emerge -pqv '=sys-devel/gcc-4.7.2-r1'`.
*
* Please include /var/tmp/portage/sys-devel/gcc-4.7.2-r1/work/build/gcc-build-logs.tar.bz2 in your bug report
*
* The complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.7.2-r1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.7.2-r1/temp/environment'.
* Working directory: '/var/tmp/portage/sys-devel/gcc-4.7.2-r1/work/build'
* S: '/var/tmp/portage/sys-devel/gcc-4.7.2-r1/work/build'
(to com o gcc do entropy instalado:
>> @@ Pacote: sys-devel/gcc-4.6.3 branch: 5, [sabayonlinux.org]
>> Disponível: versão: 4.6.3 ~ tag: NoTag ~ revisão: 0
>> Instalado: versão: 4.6.3 ~ tag: NoTag ~ revisão: 0
___________________
basicamente: não to conseguindo instalar muita coisa no portage.
Ja tinha modificado o client.conf (ctrl c/ctrl v do client.conf em
http://www.vivaolinux.com.br/artigo/Como-instalar-pacotes-no-Sabayon?pagina=5),