.whl for Linux ARM64 error

[bllmo]

I have some trouble to install python datasketches==4.0.0 on Linux ARM64, I receive the following error when I run pip3 install datasketches==4.0.0

Building wheels for collected packages: datasketches
  Building wheel for datasketches (PEP 517) ... error
  ERROR: Command errored out with exit status 1:
   command: /usr/bin/python3 /usr/lib/python3.7/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmpr2gn81le
       cwd: /tmp/pip-install-r9ab7pna/datasketches
  Complete output (68 lines):
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-aarch64-cpython-37
  creating build/lib.linux-aarch64-cpython-37/datasketches
  copying python/datasketches/PySerDe.py -> build/lib.linux-aarch64-cpython-37/datasketches
  copying python/datasketches/__init__.py -> build/lib.linux-aarch64-cpython-37/datasketches
  running build_ext
  -- The CXX compiler identification is unknown
  CMake Error at CMakeLists.txt:25 (project):
    No CMAKE_CXX_COMPILER could be found.
  
    Tell CMake where to find the compiler by setting either the environment
    variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
    to the compiler, or to the compiler name if it is in the PATH.
  
  
  -- Configuring incomplete, errors occurred!
  See also "/tmp/pip-install-r9ab7pna/datasketches/build/temp.linux-aarch64-cpython-37/CMakeFiles/CMakeOutput.log".
  See also "/tmp/pip-install-r9ab7pna/datasketches/build/temp.linux-aarch64-cpython-37/CMakeFiles/CMakeError.log".
  Traceback (most recent call last):
    File "/usr/lib/python3.7/site-packages/pip/_vendor/pep517/_in_process.py", line 280, in <module>
      main()
    File "/usr/lib/python3.7/site-packages/pip/_vendor/pep517/_in_process.py", line 263, in main
      json_out['return_val'] = hook(**hook_input['kwargs'])
    File "/usr/lib/python3.7/site-packages/pip/_vendor/pep517/_in_process.py", line 205, in build_wheel
      metadata_directory)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/build_meta.py", line 414, in build_wheel
      wheel_directory, config_settings)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/build_meta.py", line 398, in _build_with_temp_dir
      self.run_setup()
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/build_meta.py", line 335, in run_setup
      exec(code, locals())
    File "<string>", line 109, in <module>
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/__init__.py", line 87, in setup
      return distutils.core.setup(**attrs)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 185, in setup
      return run_commands(dist)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
      dist.run_commands()
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
      self.run_command(cmd)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/dist.py", line 1208, in run_command
      super().run_command(command)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/wheel/bdist_wheel.py", line 325, in run
      self.run_command("build")
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
      self.distribution.run_command(command)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/dist.py", line 1208, in run_command
      super().run_command(command)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/_distutils/command/build.py", line 132, in run
      self.run_command(cmd_name)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
      self.distribution.run_command(command)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/dist.py", line 1208, in run_command
      super().run_command(command)
    File "/tmp/pip-build-env-_wmx9kjy/overlay/lib/python3.7/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "<string>", line 46, in run
    File "<string>", line 78, in build_extension
    File "/usr/lib64/python3.7/subprocess.py", line 363, in check_call
      raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['cmake', '/tmp/pip-install-r9ab7pna/datasketches', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/tmp/pip-install-r9ab7pna/datasketches/build/lib.linux-aarch64-cpython-37', '-DWITH_PYTHON=True', '-DCMAKE_CXX_STANDARD=11', '-DPython3_EXECUTABLE=/usr/bin/python3', '-DCMAKE_BUILD_TYPE=Release']' returned non-zero exit status 1.
  ----------------------------------------
  ERROR: Failed building wheel for datasketches
Failed to build datasketches
ERROR: Could not build wheels for datasketches which use PEP 517 and cannot be installed directly

how can i generate a whl that will work on Linux ARM64 of datasketches==4.0.0?

[jmalkin]

It looks like we don't have ARM64 on linux as part of the cibuildwheel configuration. I'll fix that going forward.

In the meantime, pip is falling back to building from source since there isn't a pre-built wheel it can use. The specific error is that it's not finding a compiler. Either g++ or clang++ will work. Does your container include one of those? And if no, can you try an image that does?

[bllmo]

thanks for the reply, I need a whl to use on aws glue job that accepts libraries with Python/C only a whl format (aarch64manylinux) doc

Ray jobs do not support compiling native code in the job environment. This can be a limitation if Python dependencies transiently depend on compiled native code. Ray jobs can run the binaries provided, but they must be compiled for Linux on ARM64. This means that you can use the contents of the aarch64manylinux wheels. You can provide your own native dependencies in compiled form by repackaging a wheel according to Ray standards. Typically, this means removing the dist-info folders so that there is only one folder at the root of the archive.

I use an EC2 with Amazon Linux AMI on arm64.

[jmalkin]

I don't have an immediate fix, unfortunately. I'm running the change to the build workflow, although I don't think I have a way to test it beyond trying to trigger a "wrong architecture" error locally.

If it does seem to work, we can start a release process. There's at least a 3 working day delay baked into that, assuming we can get enough release votes within that window. With luck I'll manage to start that (it'd be 4.0.0.1, I think; this wouldn't even be a patch release) today or tomorrow.

[jmalkin]

Ok, the first quick attempts did not work. This might take longer than I'd expected.

[jmalkin]

Thanks for that.

I managed to get it "working" last night via emulation. The job took >2hrs to complete, so about 10x slower than the normal wheel generation. But at least it worked, so forward progress.

Trying to test is a challenge currently. I was able to check that the generated .so artifact does appear to be for the right architecture. Interestingly, swapping in that one for the working x86_64 library on my linux desktop produced the same error you got. That makes me suspect there's some sort of mismatch, but also has me a little bit optimistic that the build tool's generic approach might let it auto-select the correct one.

I'm going to make an attempt at cross-compiling since that'd be vastly faster if it works. But since I (might) have a working solution I won't let that be a long blocker in favor of having something to test.

[bllmo]

@jmalkin I can help you test whl directly from my AWS account

[jmalkin]

@bllmo It's very much not an official release -- I'm not sure off-hand what changes we've merged since the 4.0.0 release even. But I'm testing in my personal fork just so I don't spam everyone with push and error messages while testing.

The archive with an aarch64 wheel is here: https://github.com/jmalkin/datasketches-cpp/actions/runs/3964659089. There's an "archive.zip" at the bottom. Trying to show my work so you know what you're testing.

It seems to be using python 3.7 based on your previous error messages so I think you'll want datasketches-4.1.20230120.dev425-cp37-cp37m-manylinux_2_17_aarch64.manylinux2014_aarch64.whl

[jmalkin]

@bllmo Please let me know if you get a chance to test it. Hoping we can try for a release and get it into pypi later this week (which will depend on how fast we get votes on the release -- there's a process for Apache releases).

[jmalkin]

@will-lauer helped me test this on an AWS instance. Did a quick test of importing and feeding data into a theta sketch, which ensured it both loaded the .so and successfully farmed out calls it out.

[jmalkin]

Closed this as an issue in that we are now able to generate ARM64 wheels, but it won't be available on pypi until we can run a release cycle.

[jmalkin]

This should now be live in pypi with as v4.0.1