1 |
Stanislaw Jesmanowicz posted |
2 |
<jqLu4PQv.1144670541.5541150.stan@××××××××××××××××.com>, excerpted below, |
3 |
on Mon, 10 Apr 2006 14:02:21 +0200: |
4 |
|
5 |
> Dear amd64 users, |
6 |
> |
7 |
> Since gcc3.4.5 is released ( two weeks ), I cannot emerge it successfully. |
8 |
> I get the error message showed below. |
9 |
> I have even installed 2006.0 distribution from scratch, and after |
10 |
> emerge sync, I get the same error. |
11 |
> |
12 |
> Is that known ? Do I miss something ? |
13 |
> |
14 |
> Regards, |
15 |
> Stan |
16 |
> |
17 |
> |
18 |
> ----- error --- message ---- |
19 |
> ... |
20 |
> ... |
21 |
> checking whether make sets $(MAKE)... yes |
22 |
> checking for x86_64-pc-linux-gnu-gcc... |
23 |
> /var/tmp/portage/gcc-3.4.5/work/build/gcc/xgcc |
24 |
> -B/var/tmp/portage/gcc-3.4.5/work/build/gcc/ |
25 |
> -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem |
26 |
> /usr/x86_64-pc-linux-gnu/include -isystem |
27 |
> /usr/x86_64-pc-linux-gnu/sys-include -m32 |
28 |
> checking for C compiler default output file name... a.out |
29 |
> checking whether the C compiler works... configure: error: cannot run C |
30 |
> compiled programs. |
31 |
> If you meant to cross compile, use `--host'. |
32 |
> See `config.log' for more details. |
33 |
> make[1]: *** [configure-target-libstdc++-v3] Error 1 |
34 |
> make[1]: Leaving directory `/var/tmp/portage/gcc-3.4.5/work/build' |
35 |
> make: *** [profiledbootstrap] Error 2 |
36 |
> |
37 |
> !!! ERROR: sys-devel/gcc-3.4.5 failed. |
38 |
|
39 |
I have it merged here, with no issues that I recall. (However, I did |
40 |
merge it using gcc-4.1.0 as the compiler, IIRC, as I've unmasked and am |
41 |
running it as my default compiler.) |
42 |
|
43 |
So... have you done what it suggested and checked config.log in the |
44 |
working/compiling dir? Have you then traced the config.log error down to |
45 |
the line in the configure script to see what's going on? |
46 |
|
47 |
One of the issues I ran into a couple times (not with this package, but |
48 |
with this test in other packages) is that depending on exactly how it |
49 |
tests, it may not like certain CFLAGS (or CXXFLAGS, if it's a C++ |
50 |
compile). Thus, the usual advice applies -- try reducing your CFLAGS (or |
51 |
CXXFLAGS, but that shouldn't apply to this package) to the basics: |
52 |
|
53 |
CFLAGS="-march=k8 -pipe -O2" |
54 |
|
55 |
Just to cover something that comes up occasionally, that's NOT a zero in |
56 |
-O2, that's a "capital oh". <g> Depending on your display font, it might |
57 |
be worth retyping that part of your CFLAGS just to make sure it's right. |
58 |
|
59 |
If that doesn't help, post the error again, and config.log as well. It |
60 |
wouldn't hurt to include the configure script itself too, except that it's |
61 |
too big to be appropriate for the list. If you have a web site or other |
62 |
place you can put them to make them available for examination, maybe you |
63 |
could post both the config.log and the configure script itself there and |
64 |
post the URLs here. (Experts may be able to go from just the config.log, |
65 |
but I don't claim to be that good -- I nearly always have to reference the |
66 |
log against the configure script to see what it's actually doing that made |
67 |
the log print what it did.) |
68 |
|
69 |
-- |
70 |
Duncan - List replies preferred. No HTML msgs. |
71 |
"Every nonfree program has a lord, a master -- |
72 |
and if you use the program, he is your master." Richard Stallman in |
73 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
74 |
|
75 |
|
76 |
-- |
77 |
gentoo-amd64@g.o mailing list |