This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/54918] New: libgo.so.0 is not runtime compatible between gcc-4.6.2 and gcc-4.7.x
- From: "gafton at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 13 Oct 2012 00:33:51 +0000
- Subject: [Bug go/54918] New: libgo.so.0 is not runtime compatible between gcc-4.6.2 and gcc-4.7.x
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54918
Bug #: 54918
Summary: libgo.so.0 is not runtime compatible between gcc-4.6.2
and gcc-4.7.x
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: go
AssignedTo: ian@airs.com
ReportedBy: gafton@gmail.com
gcc-4.6.2 shipped a libgo.so.0.0.0 runtime library.
Compiling a simple hello world binary against that libgo worked okay:
bash$ cat hello.go
package main
import "fmt"
func main() {
fmt.Println("Hello, world")
}
bash$ gccgo -o hello hello.go
bash$ ./hello
Hello, world
When the gcc runtime is updated on the system to gcc-4.7.2, the previouslt
compiled binary against the gcc-4.6.2 libgo.so.0 no longer works:
bash$ ./hello
./hello: symbol lookup error: ./hello: undefined symbol: libgo_os.os.Envs
Clearly the two libgo.so.0.0.0 libraries are not compatible between gcc-4.6.x
and gcc-4.7.x - as such, the soname versioning should reflect that.