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