1 |
Am Freitag, 22. Februar 2008 schrieb Sebastian: |
2 |
> Hallo, |
3 |
> beim Systemupdate bleibe ich immer hängen beim emergen von gcc-4.2.3 mit |
4 |
> folgender Fehlermeldung. |
5 |
> |
6 |
> /usr/i686-pc-linux-gnu/bin/ld: crt1.o: No such file: No such file or |
7 |
> directory collect2: ld returned 1 exit status |
8 |
> make[3]: *** [cc1-dummy] Fehler 1 |
9 |
> make[3]: Leaving directory |
10 |
> `/var/tmp/portage/sys-devel/gcc-4.2.3/work/build/gcc' |
11 |
> make[2]: *** [all-stageprofile-gcc] Fehler 2 |
12 |
> make[2]: Leaving directory |
13 |
> `/var/tmp/portage/sys-devel/gcc-4.2.3/work/build' make[1]: *** |
14 |
> [stageprofile-bubble] Fehler 2 |
15 |
> make[1]: Leaving directory |
16 |
> `/var/tmp/portage/sys-devel/gcc-4.2.3/work/build' make: *** |
17 |
> [profiledbootstrap] Fehler 2 |
18 |
> * |
19 |
> * ERROR: sys-devel/gcc-4.2.3 failed. |
20 |
> * Call stack: |
21 |
> * ebuild.sh, line 49: Called src_compile |
22 |
> * environment, line 4548: Called toolchain_src_compile |
23 |
> * environment, line 5017: Called gcc_src_compile |
24 |
> * environment, line 2907: Called gcc_do_make |
25 |
> * environment, line 2737: Called die |
26 |
> * The specific snippet of code: |
27 |
> * emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" |
28 |
> LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || |
29 |
> die "emake failed with ${GCC_MAKE_TARGET}"; |
30 |
> * The die message: |
31 |
> * emake failed with profiledbootstrap |
32 |
> |
33 |
> Der Link /usr/i686-pc-linux-gnu/bin/ld verweist |
34 |
> auf /usr/i686-pc-linux-gnu/binutils-bin/2.18/ld und ist soweit ich das sehe |
35 |
> vorhanden und ausführbar. |
36 |
> Was emerge mir mit den LDFLLAGS=.. etc sagen will, verstehe ich jetzt gar |
37 |
> nicht. |
38 |
> |
39 |
> Bei Google habe ich jetzt auch nichts gefunden was mir weiterhilft. |
40 |
|
41 |
ich habe jetzt nochmal emerge gcc aufgerufen und da scheitert er jetzt schon |
42 |
am configuren. |
43 |
|
44 |
checking whether ln -s works... yes |
45 |
checking for gcc... gcc |
46 |
checking whether the C compiler (gcc -march=athlon -pipe -O2 ) works... no |
47 |
configure: error: installation or configuration problem: C compiler cannot |
48 |
create executables. |
49 |
* |
50 |
* ERROR: sys-devel/gcc-4.2.3 failed. |
51 |
* Call stack: |
52 |
* ebuild.sh, line 49: Called src_compile |
53 |
* environment, line 4548: Called toolchain_src_compile |
54 |
* environment, line 5017: Called gcc_src_compile |
55 |
* environment, line 2903: Called gcc_do_configure |
56 |
* environment, line 2669: Called die |
57 |
* The specific snippet of code: |
58 |
* "${S}"/configure ${confgcc} $@ ${EXTRA_ECONF} || die "failed to run |
59 |
configure"; |
60 |
* The die message: |
61 |
* failed to run configure |
62 |
|
63 |
Gruß |
64 |
Sebastian |
65 |
-- |
66 |
gentoo-user-de@l.g.o mailing list |