golang/go

cmd/vet,cmd/compile: failures with `not a Go object file`

Open

#63,866 opened on Nov 1, 2023

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
NeedsInvestigationcompiler/runtimehelp wanted

Repository metrics

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

Description

#!watchflakes
post <- log ~ `could not import .* \(not a [Gg]o object file`

Issue created automatically to collect these failures.

Example (log):

../../../../pkg/mod/github.com/go-pdf/fpdf@v0.6.0/svgbasic.go:20:2: could not import encoding/xml (not a go object file: )<arch>
)

— watchflakes

Contributor guide

Research direction
Investigate the 'not a Go object file' error when importing encoding/xml. Check if the build cache is corrupted or if there is a mismatch in architecture. Look at the path of the .a file and ensure it matches the expected format.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
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.
Mostly clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45