error: failed to run custom build command for maplibre_native v0.4.5

[kakadevices]

Hi,
I am very new to this martin. So I am trying to run on alma linux 9 here is and follow this step to install it.
cargo install cargo-binstall
cargo binstall martin
martin --help

All works till step 812 and here I get this errors. How can I solve this issue ?

warning: maplibre_native@0.4.5: Cloning maplibre-native.
error: failed to run custom build command for `maplibre_native v0.4.5`

Caused by:
  process didn't exit successfully: `/tmp/cargo-installEgcA1t/release/build/maplibre_native-3a21a7069bd68e4b/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=DOCS_RS
  cargo:rerun-if-env-changed=MLN_SYSTEM
  cargo:rerun-if-env-changed=MLN_PRECOMPILE
  cargo:rerun-if-env-changed=MLN_CORE_LIBRARY_USE_AMALGAM
  cargo:warning=Cloning maplibre-native.

  --- stderr
  error: unknown option `revision'
  usage: git clone [<options>] [--] <repo> [<dir>]

      -v, --[no-]verbose    be more verbose
      -q, --[no-]quiet      be more quiet
      --[no-]progress       force progress reporting
      --[no-]reject-shallow don't clone shallow repository
      -n, --no-checkout     don't create a checkout
      --checkout            opposite of --no-checkout
      --[no-]bare           create a bare repository
      --[no-]mirror         create a mirror repository (implies --bare)
      -l, --[no-]local      to clone from a local repository
      --no-hardlinks        don't use local hardlinks, always copy
      --hardlinks           opposite of --no-hardlinks
      -s, --[no-]shared     setup as shared repository
      --[no-]recurse-submodules[=<pathspec>]
                            initialize submodules in the clone
      --[no-]recursive[=<pathspec>]
                            alias of --recurse-submodules
      -j, --[no-]jobs <n>   number of submodules cloned in parallel
      --[no-]template <template-directory>
                            directory from which templates will be used
      --[no-]reference <repo>
                            reference repository
      --[no-]reference-if-able <repo>
                            reference repository
      --[no-]dissociate     use --reference only while cloning
      -o, --[no-]origin <name>
                            use <name> instead of 'origin' to track upstream
      -b, --[no-]branch <branch>
                            checkout <branch> instead of the remote's HEAD
      -u, --[no-]upload-pack <path>
                            path to git-upload-pack on the remote
      --[no-]depth <depth>  create a shallow clone of that depth
      --[no-]shallow-since <time>
                            create a shallow clone since a specific time
      --[no-]shallow-exclude <revision>
                            deepen history of shallow clone, excluding rev
      --[no-]single-branch  clone only one branch, HEAD or --branch
      --no-tags             don't clone any tags, and make later fetches not to follow them
      --tags                opposite of --no-tags
      --[no-]shallow-submodules
                            any cloned submodules will be shallow
      --[no-]separate-git-dir <gitdir>
                            separate git dir from working tree
      --[no-]ref-format <format>
                            specify the reference format to use
      -c, --[no-]config <key=value>
                            set config inside the new repository
      --[no-]server-option <server-specific>
                            option to transmit
      -4, --ipv4            use IPv4 addresses only
      -6, --ipv6            use IPv6 addresses only
      --[no-]filter <args>  object filtering
      --[no-]also-filter-submodules
                            apply partial clone filters to submodules
      --[no-]remote-submodules
                            any cloned submodules will use their remote-tracking branch
      --[no-]sparse         initialize sparse-checkout file to include only files at root
      --[no-]bundle-uri <uri>
                            a URI for downloading bundles before fetching from origin remote


  thread 'main' (17263) panicked at /root/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/maplibre_native-0.4.5/build.rs:491:17:
  Failed to build maplibre native: Failed to clone maplibre-native repository: exit status: 129
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

[CommanderStorm]

Hmm..
Not sure why this does not work for you..

error: unknown option `revision'

Can you report git --version?
Would be interesting if a different usage of git might make us able to support older linux versions.

cargo install martin

You should not need to compile martin.
Apparently, this was a bit broken for a while and we did not notice.
We have a pre-compiled version, that should be downloaded instead.
I just pushed a change that I wanted to release a bit ago, lets see if this enables that.
Docker defintively includes all the dependencys that we need.

If you don't care about some parts (you are having issues with the new server side rendering feature), you can also opt just into the features you need via cargo install martin --no-default-features --features mbtiles -> https://docs.rs/crate/martin/latest/features

Our release engineeering is a bit work intensive on my side, since publishing one release requires 2 steps one hour away from each other, otherwise docker works but the assets are not attached to the release.

[kakadevices]

Hi Commander,
My git --version is git version 2.47.3. So what best solution do you suggest ? If I do this cargo install martin --no-default-features --features mbtiles then I will miss out a lot of the features right only left with mbtiles ? I wont be able to connect postgres etc ? Thank you.

[CommanderStorm]

Yes, Git 2.47 is below 2.49, which explains the git clone --revision failure.
That option was added relatively recently, and maplibre_native currently assumes a newer Git version.

Since this only affects building from source, the easiest solution is to re-run:

cargo binstall martin

I just fixed an issue with our prebuilt binaries, so this should now download the binary instead of compiling locally.

If you instead run:

cargo install martin --no-default-features --features mbtiles

then yes - only the mbtiles feature will be enabled, and features like PostgreSQL support will not be included.
If you instead run the following, the postgres and mbtiles feature are active and so forth..

cargo install martin --no-default-features --features mbtiles,postgres

We could improve compatibility with older Git versions in the future, and I’d likely accept a PR for that, but for now using the prebuilt binaries is the recommended approach since that does not take a coffe break worth of time ^^

[kakadevices]

Hi Commander,
What I did now is a fresh folder and did the following step

wget https://github.com/maplibre/martin/releases/latest/download/martin-x86_64-unknown-linux-gnu.tar.gz
tar -xf martin-x86_64-unknown-linux-gnu.tar.gz
cargo install cargo-binstall
cargo binstall martin

Then I had this

cargo binstall --force  martin
 INFO resolve: Resolving package: 'martin'
 WARN resolve: When resolving martin bin gen-schemas is not found. But since it requires features unstable-schemas, this bin is ignored.
 WARN The package martin v1.9.1 (x86_64-unknown-linux-gnu) has been downloaded from github.com
 INFO This will install the following binaries:
 INFO   - martin => /root/.cargo/bin/martin
 INFO   - martin-cp => /root/.cargo/bin/martin-cp

I pressed yes then I tried to run martin --help I get this issue now

martin: error while loading shared libraries: libicuuc.so.74: cannot open shared object file: No such file or directory

I am a bit confuse what steps did I do wrong ?

[CommanderStorm]

I guess I should drop the new rendering feature from the default set and enable it only in the docker build or as a separate binary.
Seems more problematic in environments where I cannot controll the actual environment.

We need a few native dependencys for the server-rendering to work.
In your case libicuuc seems to not be installed.

martin/.github/files/multi-platform.Dockerfile

Lines 12 to 26 in f4a9335

	# Install runtime dependencies for the rendering feature (maplibre_native needs Vulkan/Mesa, libcurl, libuv,
	# plus image codec and ICU shared libraries that the maplibre_native pre-built shared object links against).
	# wget is needed for the healthcheck
	RUN apt-get update \
	&& apt-get install -y --no-install-recommends \
	mesa-vulkan-drivers \
	libcurl4 \
	libglfw3 \
	libicu74 \
	libjpeg-turbo8 \
	libpng16-16t64 \
	libuv1 \
	libwebp7 \
	wget \
	ca-certificates \

I honestly have no clue what the equivalents are for alma linux, so to unblock you you can install us without this feature (unless you need it, then you will need to figure out what the alma equivalents are to the ubuntu packages).

This is roughly the feature set that I think will be relevant for you if you don't need the rendering feature

cargo install martin --no-default-features --features fonts,mbtiles,metrics,mlt,pmtiles,postgres,sprites,styles,webui

[kakadevices]

Hi Commander,
Ok let me try and then feedback so some one else on Alama Linux can benefit it too. Thank you will feedback asap here soon.