Cant Install on Ubuntu 20.04 about go-distributed-motion-s3 HOT 2 CLOSED

@xmaxmex , thanks for flagging this issue.

The build process is a separate process from the rest of the dms3 executables, and relies on your local machine environment configuration. While I was unable to reproduce the issue that you had (running golang 1.17.7), I can provide you with some debugging actions that may help resolve the issue.

The build process happens in func BuildComponents() (file lib_build.go in /dms3build). You'll see that this function iterates on the BuildEnv map variable. Confirm the proper configuration of BuildEnv variable (no changes should be required). Since the process exits on the compilation of individual platforms, I suspect that your local machine configuration may not support them all. These include (by default):

linuxArm6  platformType = "linuxArm6"
linuxArm7  platformType = "linuxArm7"
linuxArm8  platformType = "linuxArm8"
linuxAMD64 platformType = "linuxAMD64"

The respective compiler tags are as follows:

compileTags: "GOOS=linux GOARCH=arm GOARM=6"
compileTags: "GOOS=linux GOARCH=arm GOARM=7"
compileTags: "GOOS=linux GOARCH=arm64"
compileTags: "GOOS=linux GOARCH=amd64"

So, to test your that your local machine environment can build these different executables, I'd recommend that you build each by hand, on command line, to confirm that each will platform executable will build correctly. In short, we're going to do what BuildComponents() does programmatically.

For example, to build the ARM6 version of dms3client, you'd run the following command:

env GOOS=linux GOARCH=arm GOARM=6 go build -o dms3_release/cmd/linux_arm6/dms3client cmd/dms3client/dms3client.go

Note that the output location (dms3_release) is created as part of the build process, so feel free to save the output file (the -o flag) to another existing location.

I'd suggest you iterate over all of the platform types to identify the failing environment configuration. This will be helpful in identifying dependencies.

I'd suspect that the failure you're experiencing has something to do with the local machine build environment (possibly the golang environment). If this is indeed the case, it's possible that there is a local build environment requirement that has not yet been documented.

Good luck with your investigation.

Rich

from go-distributed-motion-s3.

No follow-up response from OP, so closing out this ticket.

from go-distributed-motion-s3.