1 |
On 9/6/21 8:19 PM, cal wrote: |
2 |
> On 9/6/21 11:14 AM, n952162 wrote: |
3 |
>> On any of my 7 gentoo machines: |
4 |
>> |
5 |
>> FAILED: ^[[0mvendor/CMakeFiles/libbase.dir/libbase/logging.cpp.o |
6 |
>> /usr/bin/x86_64-pc-linux-gnu-g++ -Ivendor |
7 |
>> -I/var/tmp/portage/dev-util/android-tools-31.0.0_p1/work/android-tools-31.0.0p1/vendor/libbase/include |
8 |
>> |
9 |
>> -I/var/tmp/portage/dev-util/android-tools-31.0.0_p1/work/android-tools-31.0.0p1/vendor/core/include |
10 |
>> |
11 |
>> -I/var/tmp/portage/dev-util/android-tools-31.0.0_p1/work/android-tools-31.0.0p1/vendor/logging/liblog/include |
12 |
>> |
13 |
>> -O2 -pipe -std=gnu++2a -Wno-attributes -D_FILE_OFFSET_BITS=64 -MD -MT |
14 |
>> vendor/CMakeFiles/libbase.dir/libbase/logging.cpp.o -MF |
15 |
>> vendor/CMakeFiles/libbase.dir/libbase/logging.cpp.o.d -o |
16 |
>> vendor/CMakeFiles/libbase.dir/libbase/logging.cpp.o -c |
17 |
>> /var/tmp/portage/dev-util/android-tools-31.0.0_p1/work/android-tools-31.0.0p1/vendor/libbase/logging.cpp |
18 |
>> |
19 |
>> during RTL pass: expand |
20 |
>> /var/tmp/portage/dev-util/android-tools-31.0.0_p1/work/android-tools-31.0.0p1/vendor/libbase/logging.cpp: |
21 |
>> |
22 |
>> In member function â~@~Xvoid |
23 |
>> android::base::LogdLogger::operator()(android::base::LogId, |
24 |
>> android::base::LogSeverity, const char*, const char*, unsigned int, |
25 |
>> const char*)â~@~Y: |
26 |
>> /var/tmp/portage/dev-util/android-tools-31.0.0_p1/work/android-tools-31.0.0p1/vendor/libbase/logging.cpp:330:6: |
27 |
>> |
28 |
>> internal compiler error: in expand_expr_real_1, at expr.c:10012 |
29 |
>> 330 | void LogdLogger::operator()(LogId id, LogSeverity severity, |
30 |
>> const char* tag, const char* file, |
31 |
>> | ^~~~~~~~~~ |
32 |
>> Please submit a full bug report, |
33 |
>> with preprocessed source if appropriate. |
34 |
>> See <https://bugs.gentoo.org/> for instructions. |
35 |
>> [107/659] /usr/bin/x86_64-pc-linux-gnu-g++ -Ivendor |
36 |
>> -I/var/tmp/portage/dev-util/android-tools-31.0.0_p1/work/android-tools-31.0.0p1/vendor/libbase/include |
37 |
>> |
38 |
>> -I/var/tmp/portage/dev-util/android-tools-31.0.0_p1/work/android-tools-31.0.0p1/vendor/core/include |
39 |
>> |
40 |
>> -I/var/tmp/portage/dev-util/android-tools-31.0.0_p1/work/android-tools-31.0.0p1/vendor/logging/liblog/include |
41 |
>> |
42 |
>> -O2 -pipe -std=gnu++2a -Wno-attributes -D_FILE_OFFSET_BITS=64 -MD -MT |
43 |
>> vendor/CMakeFiles/libbase.dir/libbase/mapped_file.cpp.o -MF |
44 |
>> vendor/CMakeFiles/libbase.dir/libbase/mapped_file.cpp.o.d -o |
45 |
>> vendor/CMakeFiles/libbase.dir/libbase/mapped_file.cpp.o -c |
46 |
>> /var/tmp/portage/dev-util/android-tools-31.0.0_p1/work/android-tools-31.0.0p1/vendor/libbase/mapped_file.cpp |
47 |
>> |
48 |
>> ninja: build stopped: subcommand failed. |
49 |
>> * ERROR: dev-util/android-tools-31.0.0_p1::gentoo failed (compile phase): |
50 |
>> * ninja -v -j2 -l0 failed |
51 |
>> * |
52 |
>> * Call stack: |
53 |
>> * ebuild.sh, line 127: Called src_compile |
54 |
>> * environment, line 3186: Called cmake_src_compile |
55 |
>> * environment, line 1231: Called cmake_build |
56 |
>> * environment, line 1200: Called eninja |
57 |
>> * environment, line 1707: Called die |
58 |
>> * The specific snippet of code: |
59 |
>> * "$@" || die "${nonfatal_args[@]}" "${*} failed" |
60 |
>> |
61 |
>> I find no mention of this problem here, in the mailing list. There was |
62 |
>> one hit in an internet search, but the conclusion was a bug in go, which |
63 |
>> I don't have as described. |
64 |
>> |
65 |
>> Anybody seen this? |
66 |
>> |
67 |
> I have not experienced this issue; android-tools has emerged |
68 |
> successfully (most recently in August) for me. |
69 |
> |
70 |
> Per your build.log, you're still using GCC 9.3.0, which isn't even |
71 |
> listed on https://packages.gentoo.org/packages/sys-devel/gcc anymore |
72 |
> (9.4.0 and 10.3.0 are stable on amd64; I'm on 10.3.0 myself). |
73 |
> |
74 |
> Given the error message implies a compiler error, perhaps try upgrading |
75 |
> sys-devel/gcc first? |
76 |
> |
77 |
|
78 |
Aggh! |
79 |
|
80 |
00~/adm/gentoo/emerged>eselect gcc list |
81 |
[1] x86_64-pc-linux-gnu-9.3.0 * |
82 |
[2] x86_64-pc-linux-gnu-10.3.0 |
83 |
|
84 |
|
85 |
$ eselect news list | grep gcc |
86 |
|
87 |
doesn't turn up anything. When should/may one upgrade? |
88 |
|
89 |
Thank you for the tip! That's surely what's going on. |