golang/go

cmd/go: -compiler=gccgo: -buildmode=c-archive can't produce an archive with statically linked libgo

Open

#61,549 opened on Jul 24, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (19,008 forks)batch import
GoCommandNeedsInvestigationhelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

What version of Go are you using (go version)?

Does this issue reproduce with the latest release?

Yes

What operating system and processor architecture are you using (go env)?

What did you do?

What did you expect to see?

The program compiles and then executes without errors. This is what happens when using the standard "gc" compiler.

What did you see instead?

The created archive size is much smaller than archive created by "gc" (100634 vs 4876006 bytes on my machine). This clearly indicates that "-gccgoflags=-static-libgo" option got ignored.

Contributor guide

Research direction
Investigate how the ` gccgoflags= static libgo` flag is passed to the gccgo linker and why it fails to produce a fully static archive. Trace the build process in `cmd/go` and examine the handling of ` buildmode=c archive` with gccgo.
Tech stack
go
Domain
compilers
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gogccgocgo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20