| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
we have tools that parse APKBUILDs in aports so we should never die from
global scope.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Some tests call gcc with -fuse-ld=gold these tests fail when
binutils-gold isn't installed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There were ARMv5TE boards with 512 MiB (as in RPi1), that is enough
for go.
Also remove go-bootstrap from makedepends. In a cross-build it ends
up with depending on itself which is safe (abuild handles this) but
ugly. In normal build it is duplicated which is safe but ugly too.
Do not bump pkgrel since
- no previous armel packages exist;
- makedepends change makes no difference for the created apks.
|
|
|
|
| |
fixes #9937
|
| |
|
| |
|
|
|
|
|
|
|
| |
This change broke building of various packages, like docker and
gomplate.
This reverts commit 9686793792a2c40a872ebbb2b86fa537f22491ad.
|
| |
|
| |
|
|
|
|
| |
Various tests fail on this arch, fixing them will be a lot of work.
|
|
|
|
|
|
|
|
| |
Passes locally (even in abuild rootbld) but fails on the builders with
the following error message:
testing: can't write /tmp/go-build314848300/b744/testlog.txt:
write /tmp/go-build314848300/b744/testlog.txt: broken pipe
|
|
|
|
| |
Still better than compiling and running a 'Hello World' example.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This warning seems to be emitted since we build with `-shared` for PIE
by default through our `default-buildmode-pie.patch`. Building with
shared linkage requires depending on CGO. The patch, however, doesn't
force a dependency on CGO. As with android we need to force external
linkage in order to always depend on CGO thereby resolving this warning.
I am unsure whether this is really the best way to fix the problem since
I don't know enough about the internals of the go compiler. However, I
am under the impression that the person who originally committed the
patch isn't familiar with the compiler internals either. Thus it's
probably ok to push this as is.
|
| |
|
|
|
|
|
| |
the provides is setup correctly later on based on cross compile
variables
|
|
|
|
|
|
|
|
| |
According to [0] it is no longer necessary to distribute the tools with
the package itself. Additionally, other distributions such as Arch Linux
and Void Linux no longer ship the tools with the go package itself.
[0]: https://gitlab.informatik.uni-bremen.de/BEDUINO-Master/projektbericht/merge_requests/64#note_118786
|
|
|
|
| |
See: 33f4f12cb690a294c334d3e87b2e3c3daccd7a3c
|
| |
|
|
|
|
|
|
|
|
|
| |
It should be possible to strip go binaries these days [0]:
> We don't intentionally do anything that would make stripping a binary
not OK, and strip has worked for the past five years or so.
[0]: https://groups.google.com/forum/?_escaped_fragment_=topic/golang-dev/ABppMOjYP6w#!topic/golang-dev/ABppMOjYP6w
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
CVE-2018-6574
|
| |
|
|
|
|
| |
He hasn't been active since 2015.
|
|
|
|
|
| |
Removed a ppc64le patch that was backported from upstream
and is now part of go 1.9.2
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Even though the upgrade successfully compiled on my x86_64 laptop it
seems to fail on the x86_64 builder for some reason. Reverting the
upgrade until I figure out what's going on.
See: http://build.alpinelinux.org/buildlogs/build-edge-x86_64/community/go/go-1.9.1-r0.log
This reverts commit a51cc78c60ec483e63747c15c8321a4996db7fd0.
|
| |
|
|
|
|
|
|
|
| |
When a MOVDstorezero (8 bytes) is used the offset field
in the instruction must be a multiple of 4. This situation
had been corrected in the rules for other types of stores
but not for the zero case.
|
| |
|
|
|
|
|
|
| |
_main has an early check to verify if a binary is statically or dynamically
linked that depends on R0 being zero. R0 is not guaranteed to be zero at that
point and this can break Go on ppc64le.
|
|
|
|
|
|
|
|
|
| |
Also remove cover:
> For Go releases 1.5 and later, this tool lives in the standard
repository. The code here is not maintained.
See: https://godoc.org/golang.org/x/tools/cmd/cover
|
| |
|
|
|
|
|
|
|
|
| |
- remove unneeded "|| return 1"
- make copying sources as separate step
- fix 'rootpkg' to be invokable as individual step multiple times
(fix environment, and not moving things out of $builddir)
- do not ship cross-built tools in 'go-tools' package
|
| |
|
|
|
|
|
|
|
| |
The external linker for ppc64le was pointing to /lib64/ld-musl-ppc64le.so.1
but the valid path for alpine ppc64le is /lib/ld-musl-powerpc64le.so.1.
This issue was found by Lynn Boger from IBM go compiler team.
|
| |
|
|
|
|
| |
set-external-linker.patch adresses golang/go#18243
|
|
|
|
|
|
|
|
| |
Go package build was disabled on ppc64le because it was missing go-bootstrap dependency.
As the last version of go-bootstrap (1.4) is not available for ppc64le, I cross-compiled
it and uploaded it to: ftp://ftp.unicamp.br/pub/ppc64el/alpine/go-bootstrap/
The go-bootstrap is now installed in build-edge-ppc64le and can compile the go package.
|
| |
|
| |
|