https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121877
Sam James <sjames at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Parallel build issues with |libgo fails to build if
|libgo |/usr/lib64/libruntime.so
| |exists
Blocks|84402 |
--- Comment #2 from Sam James <sjames at gcc dot gnu.org> ---
Let's say PR104973 is for the parallel build issue (and that is fixed by the
patch for PR122794).
The other cause of this for me, is having a /usr/lib64/libruntime.so. In my
case, it is from the fbthrift package.
It's the same problem involving libtool becoming confused, like in PR122794,
but
for a different reason:
```
~/bugs/gcc-bld2/x86_64-pc-linux-gnu/libgo $ ../../gcc/gccgo -B../../gcc -c
/tmp/a.go
/tmp/a.go:1:1: error: /lib/../lib64/libruntime.so exists but does not contain
any Go export data
1 | package main; func main() {}
| ^
/tmp/a.go:1:1: error: /usr/lib/../lib64/libruntime.so exists but does not
contain any Go export data
```
`mv /usr/lib64/libruntime.so{,.bak}` lets the build succeed.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84402
[Bug 84402] [meta] GCC build system: parallelism issues (including bottlenecks)
