Mender-client version unknown

General Discussions
#1

Hello everybody.

I have a minor problem with the cross compilation of Mender-client.
Everything works great but when I run “mender -version” the shown version is unknown. (So in mender server the version of Mender client for every device is unknown too).

Perhaps I am missing some parameter that has to be given when compailing.

Any body has faced this?

best regards.

#2

Hi @aro86 welcome. How do you crosscompile mender-client? Using some build system or manually? Thanks.

#3

Hi @MarekBelisko, thanks for your response.

I compile it with a script:

LIBLZMA_INSTALL_PATH="$(pwd)/install"

cd $GOPATH
if [ cpu == "armv8" ]; then GOARCH="arm64" CGO_CFLAGS="-mtune=cortex-a53 -I{LIBLZMA_INSTALL_PATH}/include"
CGO_LDFLAGS="-L${LIBLZMA_INSTALL_PATH}/lib"
else
echo “Error: unsupported processor type: $cpu”
exit 1
fi

printf -v ARCH “%sv%s” $GOARCH
echo “Building binary for $ARCH architecture…”

go clean $package
env CGO_ENABLED=1 CC=$CC GOOS=$GOOS GOARCH=$GOARCH CGO_CFLAGS="$CGO_CFLAGS" CGO_LDFLAGS="$CGO_LDFLAGS" go build -o $output_file $package

#4

Thanks.Looks like yo want to crossompile it so in this case pls use info (scripts) from this repo

#5

@MarekBelisko I based my script on https://github.com/mendersoftware/mender-crossbuild/blob/master/go-executable-build.sh , but the version in the bianry is missing. Nevertheless the binary is well compiled and works fine in my board.

#6

The version is set if you use the Makefile in mendersoftware/mender, and specifically these lines,

#7

Thanks a lot @mirzak

#8

@mirzak how can I open a pull request to add the needed changes to add the version when compiling with go-executable-build.sh?

I have tried with my github user but (as expected) I do not have permission for that.

#9

@mirzak I have created ticket:

https://tracker.mender.io/browse/MEN-2576

Where i have added a possible solution for showing the version when compiling with go-executable-build.sh

#10

You first need to fork the repository on github, make the necessary changes, push to your fork and then create the pull-request

#11