emerge -uDN world 问题 x86_64-pc-linux-gnu-gcc 无效???

軒轅.子

今日早上无事 就索性执行了emerge --sync 然后emerge -uDN world
出现如下错误提示 比较费解

x86_64-pc-linux-gnu-gcc 这个是什么意思

1. localhost j # emerge -uDN world
2. Calculating world dependencies... done!
3. >>> Verifying ebuild Manifests...
5. >>> Emerging (1 of 1) dev-util/boost-build-1.34.1 to /
6. * boost_1_34_1.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                   [ ok ]
7. * checking ebuild checksums ;-) ...                                      [ ok ]
8. * checking auxfile checksums ;-) ...                                     [ ok ]
9. * checking miscfile checksums ;-) ...                                    [ ok ]
10. * checking boost_1_34_1.tar.bz2 ;-) ...                                  [ ok ]
11. * Filtering out invalid CFLAG "-fopenmp"
12. * Filtering out invalid CXXFLAG "-fopenmp"
13. >>> Checking boost_1_34_1.tar.bz2's mtime...
14. >>> WORKDIR is up-to-date, keeping...
15. >>> Compiling source in /var/tmp/portage/dev-util/boost-build-1.34.1/work/boost_1_34_1/tools ...
16. ###
17. ### Using 'cc' toolset.
18. ###
19. rm -rf bootstrap
20. mkdir bootstrap
21. x86_64-pc-linux-gnu-gcc -o bootstrap/jam0 -march=athlon64 -mtune=athlon64 -O3 -msse2 -m3dnow -fomit-frame-pointer -pipe -fno-strict-aliasing command.c compile.c debug.c execunix.c expand.c fileunix.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c pathunix.c pathvms.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c w32_getreg.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execnt.c filent.c
22. ./bootstrap/jam0 -f build.jam --toolset=cc --toolset-root= clean
23. ...found 1 target...
24. ...updating 1 target...
25. ...updated 1 target...
26. ./bootstrap/jam0 -f build.jam --toolset=cc --toolset-root= --with-python
27. ...found 45 targets...
28. ...updating 2 targets...
29. [MKDIR] bin.linux
30. [COMPILE] bin.linux/bjam
31. x86_64-pc-linux-gnu-gcc: ：没有那个文件或目录
33.     "x86_64-pc-linux-gnu-gcc"   -o bin.linux/bjam -DNDEBUG -DOPT_HEADER_CACHE_EXT -DOPT_GRAPH_DEBUG_EXT -DOPT_SEMAPHORE -DOPT_AT_FILES -DOPT_FIX_TARGET_VARIABLES_EXT -DOPT_IMPROVED_PATIENCE_EXT -DYYSTACKSIZE=5000 -march=athlon64 -mtune=athlon64 -O3 -msse2 -m3dnow -fomit-frame-pointer -pipe  -fno-strict-aliasing -O "" command.c compile.c debug.c expand.c glob.c hash.c hcache.c headers.c hdrmacro.c jam.c jambase.c jamgram.c lists.c make.c make1.c newstr.c option.c parse.c regexp.c rules.c scan.c search.c subst.c w32_getreg.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c pwd.c class.c native.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c execunix.c fileunix.c pathunix.c
35. ...failed [COMPILE] bin.linux/bjam...
36. ...failed updating 1 target...
37. ...updated 1 target...
38. *
39. * ERROR: dev-util/boost-build-1.34.1 failed.
40. * Call stack:
41. *                   ebuild.sh, line 1701:  Called dyn_compile
42. *                   ebuild.sh, line 1039:  Called qa_call 'src_compile'
43. *                   ebuild.sh, line   44:  Called src_compile
44. *   boost-build-1.34.1.ebuild, line   63:  Called die
45. * The specific snippet of code:
46. *      LIBS="${LDFLAGS}" CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) || die "building bjam failed"
47. *  The die message:
48. *   building bjam failed
49. *
50. * If you need support, post the topmost build error, and the call stack if relevant.
51. * A complete build log is located at '/var/log/portage/dev-util:boost-build-1.34.1:20080214-022514.log'.
52. *
54. * Messages for package dev-util/boost-build-1.34.1:
56. * Filtering out invalid CFLAG "-fopenmp"
57. * Filtering out invalid CXXFLAG "-fopenmp"
58. *
59. * ERROR: dev-util/boost-build-1.34.1 failed.
60. * Call stack:
61. *                   ebuild.sh, line 1701:  Called dyn_compile
62. *                   ebuild.sh, line 1039:  Called qa_call 'src_compile'
63. *                   ebuild.sh, line   44:  Called src_compile
64. *   boost-build-1.34.1.ebuild, line   63:  Called die
65. * The specific snippet of code:
66. *      LIBS="${LDFLAGS}" CC=$(tc-getCC) ./build.sh ${toolset} $(use_with python) || die "building bjam failed"
67. *  The die message:
68. *   building bjam failed
69. *
70. * If you need support, post the topmost build error, and the call stack if relevant.
71. * A complete build log is located at '/var/log/portage/dev-util:boost-build-1.34.1:20080214-022514.log'.
72. *

复制代码

zhllg

x86_64-pc-linux-gnu-gcc这是你的gcc的名字
你用gcc-config再设定一下你的gcc

軒轅.子

是不是 执行 gcc-config x86_64-pc-linux-gnu-4.1.2

1. gcc-config x86_64-pc-linux-gnu-4.1.2
2. * Switching native-compiler to x86_64-pc-linux-gnu-4.1.2 ...             [ ok ]

复制代码

我执行了这个 但是还是一样的错误提示

byakko_ang

我也遇到了这样的情况我的是i686的。

jjj311

检查你的CHOST设置是否和gcc－config里面使用的一致

晨想

直接运行一下该命令看看是否成功？
gcc-config -l 有啥结果？

晨想

直接运行一下该命令看看是否成功？
gcc-config -l 有啥结果？

nainaide

重新emerge --sync 就好了，这个bug已经修复了。