Re: Debugging a go build

[Hauke Fath <hf%spg.tu-darmstadt.de@localhost>]

On Tue, 17 Mar 2026 18:42:24 +0000 (UTC), Benny Siegert wrote:
> On Tue, 17 Mar 2026, Thomas Klausner wrote:
> 
>> I suspect in the middle of building all the go modules there are some
>> error lines that are not obvious.
> 
> Exactly. [...]

Thanks - Thomas pointed me to one of the build issues. FTR, this is 
about mattermost; I have pushed what I have to wip/mattermost-server 
with a TODO, feeling slightly out of depth.

Out of interest (assume no clue about the Golang eco-system): When a 
handful of Go modules out of a hundred fail to - well, "build"? 
"integrate"?, and the error message ("undefined") points to a line in 
what looks like an interface list, what is the next step? Pester 
upstream about a platform they don't care about? Or find the respective 
module's upstream?

Cheerio,
Hauke

-- 
     The ASCII Ribbon Campaign                    Hauke Fath
()     No HTML/RTF in email            Institut für Nachrichtentechnik
/\     No Word docs in email                     TU Darmstadt
     Respect for open standards              Ruf +49-6151-16-21344