[help救急]update world后出问题了[gcc升级问题 老gcc被depclean删除] ［感谢:blackwh

杨珂

Gentoo Desktop # fix_libtool_files.sh 4.1.2
* Scanning libtool files for hardcoded gcc library paths...
gcc-config error: Could not run/locate "gcc"
:0: assertion failed: (gcc -dumpversion) | getline NEWVER)
Gentoo Desktop #

Gentoo Desktop # gcc-config -l        
* gcc-config: Active gcc profile is invalid!
[1] i686-pc-linux-gnu-4.3.2
Gentoo Desktop #

还是不行

blackwhite

应该是gcc的版本混乱了。
ls /usr/share/gcc-data/x86_64-pc-linux-gnu/
gcc -v
gcc-config -f i686-pc-linux-gnu-4.3.2
env-update && source /etc/profile
fix_libtool_files.sh 4.1.2

杨珂

Post by blackwhite;1976746
应该是gcc的版本混乱了。
ls /usr/share/gcc-data/x86_64-pc-linux-gnu/
gcc -v
gcc-config -f i686-pc-linux-gnu-4.3.2
env-update && source /etc/profile
fix_libtool_files.sh 4.1.2

1. 
   
2. Gentoo Desktop # gcc-config -f i686-pc-linux-gnu-4.3.2
   
3. * Switching native-compiler to i686-pc-linux-gnu-4.3.2 ...
   
4. 
   
5. * Your gcc has a bug with GCC_SPECS.
   
6. * Please re-emerge gcc.
   
7. * http://bugs.gentoo.org/68395
   
8. 
   
9. >>> Regenerating /etc/ld.so.cache...                                      [ ok ]
   
10. 
    
11. * If you intend to use the gcc from the new profile in an already
    
12. * running shell, please remember to do:
    
13. 
    
14. *   # source /etc/profile
    
15. 
    
16. Gentoo Desktop #
    
17. 
    
18. Gentoo Desktop # env-update && source /etc/profile
    
19. >>> Regenerating /etc/ld.so.cache...
    
20. Gentoo Desktop # fix_libtool_files.sh 4.1.2
    
21. * Scanning libtool files for hardcoded gcc library paths...
    
22. *   [1/8] Scanning /lib ...
    
23. *   [2/8] Scanning /usr/lib ...
    
24. *   [3/8] Scanning //usr//lib/opengl/xorg-x11/lib ...
    
25. *   [4/8] Scanning /opt/sun-jdk-1.4.2.19/jre/lib/i386 ...
    
26. *   [5/8] Scanning /usr/games/lib ...
    
27. *   [6/8] Scanning /usr/i686-pc-linux-gnu/lib ...
    
28. *   [7/8] Scanning /usr/local/lib ...
    
29. *   [8/8] Scanning /usr/qt/3/lib ...
    
30. Gentoo Desktop #

复制代码

之后emerge了 libtool apr 然后emerald
现在我已经在登录usr桌面了

多谢 ！！！

我去看了看gcc upgrade guide  知道是操作不当造成的
请问一下 现在这样的情况 我还应该为系统做点什么 多谢指教

杨珂

Post by nainaide;1976736
升级gcc后是不是把旧版本干掉之前没运行fix_libtool_files.sh？如果是可以试试：gcc-config -f

不好意思 我当时没反应过来老兄的正确提示

杨珂

after using : emerge --update --deep --newuse world && emerge --depclean
there is no time to do that and ‘revdep-rebuild’ can not fix it
so i think the command :
emerge --update --deep --newuse world && emerge --depclean && revdep-rebuild
should be considered as dangerous !

blackwhite

Post by 杨珂;1976769
after using : emerge --update --deep --newuse world && emerge --depclean
there is no time to do that and ‘revdep-rebuild’ can not fix it
so i think the command :
emerge --update --deep --newuse world && emerge --depclean && revdep-rebuild
should be considered as dangerous !

如果这个过程中升级了gcc，python了（大的版本升级，gcc-config -l可以列出来,python是从。x升级到。y了），要先升级用gcc-config和python-updater。然后才可以用depclean。

lingyunxs

我觉得大的升级，比如升级gcc和python，
升级后都运行一下：
revdep-rebuild 和 python-updater

还有，运行一下
gcc-config -l  看看现在系统使用的gcc是哪个版本的。
eselect python list  看看现在系统使用的python是哪个版本的。

conquer

可以请教一个问题么？
今天我升级python出错，reboot之后进不了系统。

localhost ~ # python-updater


GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info

>>> Failed to emerge dev-util/subversion-1.6.1, Log file:

>>> '/var/tmp/portage/dev-util/subversion-1.6.1/temp/build.log'

* Messages for package dev-util/subversion-1.6.1:

* APR-Util is linked against Berkeley DB 4.6, but you are trying
* to build Subversion with support for Berkeley DB 4.7.
* Rebuild dev-libs/apr-util or set SVN_BDB_VERSION="4.6".
* Aborting to avoid possible run-time crashes.
*
* ERROR: dev-util/subversion-1.6.1 failed.
* Call stack:
* ebuild.sh, line 49: Called pkg_setup
* subversion-1.6.1.ebuild, line 79: Called die
* The specific snippet of code:
* die "Berkeley DB version mismatch"
* The die message:
* Berkeley DB version mismatch
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/dev-util/subversion-1.6.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-util/subversion-1.6.1/temp/die.env'.
*

* IMPORTANT: 1 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.

localhost ~ # python-updater

ion:
GENTOO_VM= CLASSPATH="" JAVA_HOME=""
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info

>>> Failed to emerge dev-util/subversion-1.6.1, Log file:

>>> '/var/tmp/portage/dev-util/subversion-1.6.1/temp/build.log'

* Messages for package dev-util/subversion-1.6.1:

* APR-Util is linked against Berkeley DB 4.6, but you are trying
* to build Subversion with support for Berkeley DB 4.7.
* Rebuild dev-libs/apr-util or set SVN_BDB_VERSION="4.6".
* Aborting to avoid possible run-time crashes.
*
* ERROR: dev-util/subversion-1.6.1 failed.
* Call stack:
* ebuild.sh, line 49: Called pkg_setup
* subversion-1.6.1.ebuild, line 79: Called die
* The specific snippet of code:
* die "Berkeley DB version mismatch"
* The die message:
* Berkeley DB version mismatch
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/dev-util/subversion-1.6.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-util/subversion-1.6.1/temp/die.env'.
*

* IMPORTANT: 1 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.