AIX build is broken

[bmarwell]

Hi,

I just noticed the env vars GOOS=aix GOARCH=ppc64 will lead to a build error:

$ GOOS=aix GOARCH=ppc64 go build
# github.com/dgraph-io/badger
../../../../go/pkg/mod/github.com/dgraph-io/badger@v1.6.2/dir_unix.go:63:13: undefined: unix.Flock
# github.com/dgraph-io/badger/v2
../../../../go/pkg/mod/github.com/dgraph-io/badger/v2@v2.2007.4/dir_unix.go:62:13: undefined: unix.Flock
# github.com/google/certificate-transparency-go/x509
../../../../go/pkg/mod/github.com/google/certificate-transparency-go@v1.1.6/x509/cert_pool.go:65:9: undefined: loadSystemRoots
../../../../go/pkg/mod/github.com/google/certificate-transparency-go@v1.1.6/x509/root.go:21:32: undefined: loadSystemRoots
../../../../go/pkg/mod/github.com/google/certificate-transparency-go@v1.1.6/x509/verify.go:759:12: c.systemVerify undefined (type *Certificate has no field or method systemVerify)

I think this should have worked out of the box? => https://gist.github.com/asukakenji/f15ba7e588ac42795f421b48b8aede63

I found no infos about AIX not being supported. Any help is appreciated.

[bmarwell]

Just for reference, other not-so-common platforms work fine, too.

~/git/caddy-2.7.6-src/caddy ⌚ 10:25:19
$ GOOS=linux GOARCH=ppc64le go build

~/git/caddy-2.7.6-src/caddy ⌚ 10:27:32
$ file caddy
caddy: ELF 64-bit LSB executable, 64-bit PowerPC or cisco 7500, OpenPOWER ELF V2 ABI, version 1 (SYSV), statically linked, Go BuildID=G8uALCkYZAyhWc4CyD6c/zliuk-1icIxIIpa3eOMl/vI3N5kg7rx6eOf2RfoYl/on9sJjH1QcQMdAMjc8O0, with debug_info, not stripped

~/git/caddy-2.7.6-src/caddy ⌚ 10:27:34
$ GOOS=linux GOARCH=s390x go build

~/git/caddy-2.7.6-src/caddy ⌚ 10:27:53
$ file caddy
caddy: ELF 64-bit MSB executable, IBM S/390, version 1 (SYSV), statically linked, Go BuildID=mkeLzHm9-bugelmaRTtG/PPW-2hvu4VfD7pgOy9Wu/97vrcGdc2E5OZK_rR8Rq/bXuMaIM1H6bX4ZVQfbd7, with debug_info, not stripped

[francislavoie]

I've never even heard of aix. We're not testing for that in our crossbuild job https://github.com/caddyserver/caddy/blob/master/.github/workflows/cross-build.yml

Either way, this is a problem with upstream dependencies. You'll probably need to get the attention of dgraph-io/badger and google/certificate-transparency-go to fix it.

[mohammed90]

For badger, the issue is a gap further upstream in golang.org/x/sys/unix, which is missing some syscalls for AIX, notably Lock.

[bmarwell]

I really do not know what to do here. If you would like to help me out, you'd need to create upstream issues for this -- sorry! (and thanks for the quick analysis!).

[mohammed90]

I really do not know what to do here. If you would like to help me out, you'd need to create upstream issues for this -- sorry! (and thanks for the quick analysis!).

Just so we know the use case, are you trying to use Caddy on AIX, or just mere curiosity?

[bmarwell]

Just so we know the use case, are you trying to use Caddy on AIX, or just mere curiosity?

I would like to evaluate different web- and reverse-proxy servers for a few use cases. But AIX is a must-have for me for inclusion into my compatibility matrix. But in terms of use-case, it is just a proof-of-concept, so something in-between, probably.

[bmarwell]

I've never even heard of aix. We're not testing for that in our crossbuild job https://github.com/caddyserver/caddy/blob/master/.github/workflows/cross-build.yml

Either way, this is a problem with upstream dependencies. You'll probably need to get the attention of dgraph-io/badger and google/certificate-transparency-go to fix it.

Oh, I can add a PR for that! #5971
Let me just find and sign the CLA form. 😊

[mohammed90]

Reported upstream:

• x/sys/unix: missing some AIX syscalls, notably Flock golang/go#64669
• [BUG]: compilation fails with GOOS=aix (Unix) hypermodeinc/badger#2035
• Compilation Failure on GOOS=aix google/certificate-transparency-go#1276

[mholt]

We might have to defer this as I think this is largely out of our control. It looks like AIX simply does not support the API needed. But with the tag we can revisit this more easily. Thanks for reporting!

Closing because there's nothing actionable we can do right now (more than Mohammed has done), as far as I know... but feel free to continue discussion.