1 |
Jack wrote: |
2 |
> I now get this error trying to emerge two different packages: |
3 |
> libofx-0.10.7 and gnupg (both 2.2.39 and 2.3.6). It might also be the |
4 |
> same problem for a few bugs on b.g.o found by searching on "cannot |
5 |
> create exectuables." |
6 |
> |
7 |
> The relevant lines from build.log are |
8 |
> |
9 |
> checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc |
10 |
> checking whether the C compiler works... no |
11 |
> configure: error: in |
12 |
> `/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7': |
13 |
> configure: error: C compiler cannot create executables |
14 |
> See `config.log' for more details |
15 |
> |
16 |
> and from config.log: |
17 |
> |
18 |
> Thread model: posix |
19 |
> Supported LTO compression algorithms: zlib |
20 |
> gcc version 11.3.0 (Gentoo 11.3.0 p4) |
21 |
> configure:2952: $? = 0 |
22 |
> configure:2941: x86_64-pc-linux-gnu-gcc -V >&5 |
23 |
> x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option '-V' |
24 |
> x86_64-pc-linux-gnu-gcc: fatal error: no input files |
25 |
> compilation terminated. |
26 |
> configure:2952: $? = 1 |
27 |
> configure:2941: x86_64-pc-linux-gnu-gcc -qversion >&5 |
28 |
> x86_64-pc-linux-gnu-gcc: error: unrecognized command-line option |
29 |
> '-qversion'; did you mean '--version'? |
30 |
> x86_64-pc-linux-gnu-gcc: fatal error: no input files |
31 |
> compilation terminated. |
32 |
> configure:2952: $? = 1 |
33 |
> configure:2972: checking whether the C compiler works |
34 |
> configure:2994: x86_64-pc-linux-gnu-gcc -march=native -O2 -pipe -og |
35 |
> -ggdb -Wl,-O1 -Wl,--as-needed conftest.c >&5 |
36 |
> configure:2998: $? = 0 |
37 |
> configure:3036: result: no |
38 |
> configure: failed program was: |
39 |
> | /* confdefs.h */ |
40 |
> | #define PACKAGE_NAME "libofx" |
41 |
> | #define PACKAGE_TARNAME "libofx" |
42 |
> | #define PACKAGE_VERSION "0.10.7" |
43 |
> | #define PACKAGE_STRING "libofx 0.10.7" |
44 |
> | #define PACKAGE_BUGREPORT "" |
45 |
> | #define PACKAGE_URL "" |
46 |
> | /* end confdefs.h. */ |
47 |
> | |
48 |
> | int |
49 |
> | main () |
50 |
> | { |
51 |
> | |
52 |
> | ; |
53 |
> | return 0; |
54 |
> | } |
55 |
> configure:3041: error: in |
56 |
> `/var/tmp/portage/dev-libs/libofx-0.10.7/work/libofx-0.10.7': |
57 |
> configure:3043: error: C compiler cannot create executables |
58 |
> See `config.log' for more details |
59 |
> |
60 |
> The thing I find curious is that it appears to me that the output of |
61 |
> the test compile is a file called "g" which I don't recall ever |
62 |
> seeing, and so I wonder if the problem is that something has changed |
63 |
> with gcc defaults and configure does not yet recognize that change. I |
64 |
> also don't know the significance of the two "fatal error: no input |
65 |
> files". |
66 |
> |
67 |
> The fact that this happens with two unrelated packages suggests that |
68 |
> it's not specific to either of them, but something in my system or |
69 |
> configuration. |
70 |
> |
71 |
> Any thoughts or suggestions? |
72 |
> |
73 |
> Jack |
74 |
> |
75 |
> |
76 |
> |
77 |
|
78 |
|
79 |
I ran into this ages ago. I think the fix was to reset which compiler |
80 |
it is set to use. I used to keep two installed, in case one would fail |
81 |
or some package couldn't build with a newer version yet. If I recall |
82 |
correctly, I would list the available options with gcc-config -l and |
83 |
then if two are available, set to older one and then change back or if |
84 |
only one is installed, just set it to the one you have. It's been a |
85 |
good while and it could be that the cause of the problem has changed but |
86 |
I don't think it will hurt anything to try this. I think some settings |
87 |
gets messed up and resetting it fixes it. |
88 |
|
89 |
Hope that helps. If not, clueless. :/ |
90 |
|
91 |
Dale |
92 |
|
93 |
:-) :-) |