On Tue, 4 Mar 2025, Ian Lance Taylor wrote: > On Tue, Mar 4, 2025 at 2:12 AM Richard Biener <rguent...@suse.de> wrote: > > > As PR119098 shows the gccgo driver uses the install path compiled > > into the shared libgo and thus updating that but not the driver > > will cause the driver to fail to find other tools like cgo. > > > > Thus bump the SONAME for GCC 15 as well, as we've done for each > > release in the past. > > > > I think libgo changes go through another "upstream", so Ian, can you > > please take care of this? > > > > Thanks, committed. > > I'll try to fix the underlying issue.
Thanks - during a quick inspection we wondered if gccgo could simply set the GOROOT (or how it was called) environment if not set which would override the built-in path. I was also wondering whether/how relocating a GCC install works for GO with the compiled-in libexecdir. Richard. > Ian > -- Richard Biener <rguent...@suse.de> SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg, Germany; GF: Ivo Totev, Andrew McDonald, Werner Knoblich; (HRB 36809, AG Nuernberg)
