github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-11 17:46:29 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Building gitea with golang1.18 binary fails #8819

New Issue
Closed
opened 2025-11-02 08:19:49 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 08:19:49 -06:00
Owner
Copy Link

Originally created by @gesangtome on GitHub (Apr 12, 2022).

I tried to build gitea with the latest binary package of golang, and exported the environment variable $GOROOT, it looked fine at first, but when running go generate, I got this error:

Running go generate...
make[1]: *** No rule to make target 'modules/public/bindata.go', needed by 'gitea'. Stop.
make[1]: Leaving directory '/home/gesangtome/rpm-packages/gitea/BUILD/gitea-1.16.5'

what happened?

Originally created by @gesangtome on GitHub (Apr 12, 2022). I tried to build gitea with the latest binary package of golang, and exported the environment variable $GOROOT, it looked fine at first, but when running go generate, I got this error: Running go generate... make[1]: *** No rule to make target 'modules/public/bindata.go', needed by 'gitea'. Stop. make[1]: Leaving directory '/home/gesangtome/rpm-packages/gitea/BUILD/gitea-1.16.5' what happened?
GiteaMirror added the issue/needs-feedback label 2025-11-02 08:19:49 -06:00
GiteaMirror commented 2025-11-02 08:19:50 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Apr 12, 2022):

FWIW, gitea's 1.16.x branch is being built with golang 1.18 but it looks like that is somehow related to make instead of go itself.

To confirm an assumption made, is the binary you are using for go have the name go or is it go1.18 or something similar?

@techknowlogick commented on GitHub (Apr 12, 2022): FWIW, gitea's 1.16.x branch is being built with golang 1.18 but it looks like that is somehow related to make instead of go itself. To confirm an assumption made, is the binary you are using for go have the name `go` or is it `go1.18` or something similar?
GiteaMirror commented 2025-11-02 08:19:50 -06:00
Author
Owner
Copy Link

@42wim commented on GitHub (Apr 12, 2022):

Can you also paste the output of go env ?

@42wim commented on GitHub (Apr 12, 2022): Can you also paste the output of `go env` ?
GiteaMirror commented 2025-11-02 08:19:51 -06:00
Author
Owner
Copy Link

@gesangtome commented on GitHub (Apr 13, 2022):

@techknowlogick
Assuming this error caused by the GOLANG binary package, we need to break it, but I only have one PC and need more test results.

Can it be verified together? Thanks.

https://golang.google.cn/dl/go1.18.1.linux-amd64.tar.gz

@gesangtome commented on GitHub (Apr 13, 2022): @techknowlogick Assuming this error caused by the GOLANG binary package, we need to break it, but I only have one PC and need more test results. Can it be verified together? Thanks. https://golang.google.cn/dl/go1.18.1.linux-amd64.tar.gz
GiteaMirror commented 2025-11-02 08:19:51 -06:00
Author
Owner
Copy Link

@gesangtome commented on GitHub (Apr 13, 2022):

@42wim

GOROOT=/home/${username}/golang; export GOROOT
PATH=$GOROOT/bin:$PATH; export PATH

go version
go version go1.18.1 linux/amd64

go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/${username}/.cache/go-build"
GOENV="/home/${username}/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/${username}/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/${username}/go"
GOPRIVATE=""
GOPROXY="https://goproxy.cn,direct"
GOROOT="/home/${username}/golang"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/${username}/golang/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.1"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/${username}/gitea-1.16.5/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2105614396=/tmp/go-build -gno-record-gcc-switches"

@gesangtome commented on GitHub (Apr 13, 2022): @42wim GOROOT=/home/${username}/golang; export GOROOT PATH=$GOROOT/bin:$PATH; export PATH go version go version go1.18.1 linux/amd64 go env GO111MODULE="" GOARCH="amd64" GOBIN="" GOCACHE="/home/${username}/.cache/go-build" GOENV="/home/${username}/.config/go/env" GOEXE="" GOEXPERIMENT="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOINSECURE="" GOMODCACHE="/home/${username}/go/pkg/mod" GONOPROXY="" GONOSUMDB="" GOOS="linux" GOPATH="/home/${username}/go" GOPRIVATE="" GOPROXY="https://goproxy.cn,direct" GOROOT="/home/${username}/golang" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/home/${username}/golang/pkg/tool/linux_amd64" GOVCS="" GOVERSION="go1.18.1" GCCGO="gccgo" GOAMD64="v1" AR="ar" CC="gcc" CXX="g++" CGO_ENABLED="1" GOMOD="/home/${username}/gitea-1.16.5/go.mod" GOWORK="" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2105614396=/tmp/go-build -gno-record-gcc-switches"
GiteaMirror commented 2025-11-02 08:19:51 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Apr 13, 2022):

To confirm, this works when you use golang 1.17?

@techknowlogick commented on GitHub (Apr 13, 2022): To confirm, this works when you use golang 1.17?
GiteaMirror commented 2025-11-02 08:19:51 -06:00
Author
Owner
Copy Link

@gesangtome commented on GitHub (Apr 14, 2022):

@techknowlogick

I verified again with the command TAGS="bindata sqlite sqlite_unlock_notify" make build and the error disappeared, why?

@gesangtome commented on GitHub (Apr 14, 2022): @[techknowlogick](https://github.com/techknowlogick) I verified again with the command TAGS="bindata sqlite sqlite_unlock_notify" make build and the error disappeared, why?
GiteaMirror commented 2025-11-02 08:19:51 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Apr 14, 2022):

The 1.16.5 tag hasn't changed, so it must be something locally had changed. I suspect it could be related to go generate not making the bindata files initially and so then make couldn't file them.
I'm going to close this as it is now working, but if you have issues later on please open a thread in our forum: https://discourse.gitea.io/

@techknowlogick commented on GitHub (Apr 14, 2022): The 1.16.5 tag hasn't changed, so it must be something locally had changed. I suspect it could be related to go generate not making the bindata files initially and so then make couldn't file them. I'm going to close this as it is now working, but if you have issues later on please open a thread in our forum: https://discourse.gitea.io/
GiteaMirror commented 2025-11-02 08:19:52 -06:00
Author
Owner
Copy Link

@gesangtome commented on GitHub (Apr 17, 2022):

@techknowlogick thank

@gesangtome commented on GitHub (Apr 17, 2022): @techknowlogick thank
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/needs-feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8819
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?