Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Error en baselayout - TODO el sistema caido!! [SOLVED]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Spanish
View previous topic :: View next topic  
Author Message
natrix
Guru
Guru


Joined: 23 Aug 2013
Posts: 556

PostPosted: Tue Jun 26, 2018 11:57 pm    Post subject: Error en baselayout - TODO el sistema caido!! [SOLVED] Reply with quote

Hola:

A partir de un error de compilación del "baselayout", agregué la línea 'SYMLINK_LIB=no' en mi make.conf siguientdo https://forums.gentoo.org/viewtopic-t-1081914-start-0.html

Al compilar baselayout-2.4 saltó el siguiente error y el sistema dejó de responder entre ellos 'portage'.

Qué debo hacer?

Muchas gracias


Code:
Emerging (1 of 1) sys-apps/baselayout-2.4.1-r2::gentoo
 * baselayout-2.4.1.tar.bz2 BLAKE2B SHA512 size ;-) ...                                                               [ ok ]
 * Converting /lib from a symlink to a dir
 * Migrating /lib32 to /lib
 * Converting /usr/lib from a symlink to a dir
 * Migrating /usr/lib32 to /usr/lib
 * Initializing /usr/local/lib as a dir
/usr/bin/python3.5m: can't open file '/usr/lib/portage/python3.5/filter-bash-environment.py': [Errno 2] No such file or directory
 * ERROR: sys-apps/baselayout-2.4.1-r2::gentoo failed (setup phase):
 *   filter-bash-environment.py failed
 *
 * Call stack:
 *            ebuild.sh, line  792:  Called __ebuild_main 'setup'
 *   phase-functions.sh, line 1105:  Called __filter_readonly_variables '--filter-features'
 *   phase-functions.sh, line  148:  Called die
 * The specific snippet of code:
sed: can't read /usr/lib/portage/python3.5/phase-functions.sh: No such file or directory
 *
 * If you need support, post the output of `emerge --info '=sys-apps/baselayout-2.4.1-r2::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-apps/baselayout-2.4.1-r2::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/temp/environment'.
 * Working directory: '/usr/lib64/python3.5/site-packages'
 * S: '/var/tmp/portage/sys-apps/baselayout-2.4.1-r2/work/baselayout-2.4.1'
/usr/lib/portage/python3.5/isolated-functions.sh: line 242: /usr/lib/portage/python3.5/ebuild-ipc: No such file or directory
 * The ebuild phase 'setup' has exited unexpectedly. This type of behavior
 * is known to be triggered by things such as failed variable assignments
 * (bug #190128) or bad substitution errors (bug #200313). Normally, before
 * exiting, bash should have displayed an error message above. If bash did
 * not produce an error message above, it's possible that the ebuild has
 * called `exit` when it should have called `die` instead. This behavior
 * may also be triggered by a corrupt bash binary or a hardware problem
 * such as memory or cpu malfunction. If the problem is not reproducible or
 * it appears to occur randomly, then it is likely to be triggered by a
 * hardware problem. If you suspect a hardware problem then you should try
 * some basic hardware diagnostics such as memtest. Please do not report
 * this as a bug unless it is consistently reproducible and you are sure
 * that your bash binary and hardware are functioning properly.
/bin/bash: /usr/lib/portage/python3.5/misc-functions.sh: No such file or directory
 * The ebuild phase 'die_hooks' has exited unexpectedly. This type of
 * behavior is known to be triggered by things such as failed variable
 * assignments (bug #190128) or bad substitution errors (bug #200313).
 * Normally, before exiting, bash should have displayed an error message
 * above. If bash did not produce an error message above, it's possible
 * that the ebuild has called `exit` when it should have called `die`
 * instead. This behavior may also be triggered by a corrupt bash binary or
 * a hardware problem such as memory or cpu malfunction. If the problem is
 * not reproducible or it appears to occur randomly, then it is likely to
 * be triggered by a hardware problem. If you suspect a hardware problem
 * then you should try some basic hardware diagnostics such as memtest.
 * Please do not report this as a bug unless it is consistently
 * reproducible and you are sure that your bash binary and hardware are
 * functioning properly.

>>> Failed to emerge sys-apps/baselayout-2.4.1-r2, Log file:


Last edited by natrix on Wed Jun 27, 2018 6:02 pm; edited 1 time in total
Back to top
View user's profile Send private message
natrix
Guru
Guru


Joined: 23 Aug 2013
Posts: 556

PostPosted: Wed Jun 27, 2018 6:02 pm    Post subject: Reply with quote

Solucionado!

Seguí los pasos contrarios a:
Code:
 * Converting /lib from a symlink to a dir
 * Migrating /lib32 to /lib
 * Converting /usr/lib from a symlink to a dir
 * Migrating /usr/lib32 to /usr/lib


Cuando tuve portage trabajando corrí 'unsymlink-lib' para hacer la migración.

Ahora todo volvió a la normalidad.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Spanish All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum