github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Gitea fails to build on aarch64 #245

New Issue
Closed
opened 2025-11-02 03:15:20 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 03:15:20 -06:00
Owner
Copy Link

Originally created by @clandmeter on GitHub (Jan 18, 2017).

Im reporting this upstream and will refer to this issue.

code.gitea.io/gitea/vendor/github.com/ngaut/log
vendor/github.com/ngaut/log/crash_unix.go:16: undefined: syscall.Dup2

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @clandmeter on GitHub (Jan 18, 2017). Im reporting this upstream and will refer to this issue. code.gitea.io/gitea/vendor/github.com/ngaut/log vendor/github.com/ngaut/log/crash_unix.go:16: undefined: syscall.Dup2 <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/41075455-gitea-fails-to-build-on-aarch64?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>
GiteaMirror added the type/bug label 2025-11-02 03:15:20 -06:00
GiteaMirror commented 2025-11-02 03:15:21 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Jan 19, 2017):

Thank you for the report.

@tboerger commented on GitHub (Jan 19, 2017): Thank you for the report.
GiteaMirror commented 2025-11-02 03:15:21 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 11, 2017):

github.com/ngaut/log is only used by tidb. I think we have to take tidb tag back and make tidb not default. Because I find tidb cannot be shared read. So SSH will never be succeed. @tboerger

@lunny commented on GitHub (Feb 11, 2017): `github.com/ngaut/log` is only used by `tidb`. I think we have to take tidb tag back and make tidb not default. Because I find `tidb` cannot be shared read. So SSH will never be succeed. @tboerger
GiteaMirror commented 2025-11-02 03:15:21 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 23, 2017):

I move this to 1.2 since we have to take tidb tag back to resolve this issue.

@lunny commented on GitHub (Feb 23, 2017): I move this to 1.2 since we have to take tidb tag back to resolve this issue.
GiteaMirror commented 2025-11-02 03:15:22 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Feb 23, 2017):

The upstream lib solved the issue, so at least we can update the lib and get gitea building in arm64

@tboerger commented on GitHub (Feb 23, 2017): The upstream lib solved the issue, so at least we can update the lib and get gitea building in arm64
GiteaMirror commented 2025-11-02 03:15:22 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 24, 2017):

You mean tidb fixed the issue?

@lunny commented on GitHub (Feb 24, 2017): You mean tidb fixed the issue?
GiteaMirror commented 2025-11-02 03:15:22 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 24, 2017):

but that resulted in a new issue https://github.com/ngaut/log/issues/7. @ngaut

@lunny commented on GitHub (Feb 24, 2017): but that resulted in a new issue https://github.com/ngaut/log/issues/7. @ngaut
GiteaMirror commented 2025-11-02 03:15:22 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Mar 7, 2017):

@clandmeter please confirm #1132

@lunny commented on GitHub (Mar 7, 2017): @clandmeter please confirm #1132
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 type/bug
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#245
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?