This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/23912] Go binaries do not call __libc_start_main
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 28 Nov 2018 08:19:51 +0000
- Subject: [Bug libc/23912] Go binaries do not call __libc_start_main
- Auto-submitted: auto-generated
- References: <bug-23912-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23912
--- Comment #4 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Adhemerval Zanella from comment #3)
> $ go tool link -linkmode external main.o
“-linkmode external” selects the system (binutils/GCC) linker. The problem is
with the Go (internal) linker.
> I am failing to see in which scenario Go linker or runtime is not calling
> _libc_start_main.
It happens if the Go linker is used to produce a dynamically linked executable.
For example, this happens if a pure Go (no cgo) program indirectly calls
getaddrinfo or anything else that needs NSS.
--
You are receiving this mail because:
You are on the CC list for the bug.