[zmq] Unable to package pyzmq via pyoxidizer

pyzmq has native dependency of libzmq.
I tried couple of things
i ) installing pyzmq via
pip install pyzmq --install-option="--zmq=bundled"

added these lines to pyoxidizer.toml file
[[packaging_rule]]
type = "setup-py-install"
package_path = "/path/to/pyzmq/"

fetching https://github.com/zeromq/libzmq/releases/download/v4.3.2/zeromq-4.3.2.tar.gz into bundled
attempting ./configure to generate platform.hpp
Warning: failed to configure libzmq:
b'configure: error: Unable to find a working C++ compiler\n'
staging platform.hpp from: /home/ubuntu/Goutham/fh_streaming/pyapp/pyzmq/buildutils/include_linux
checking for timer_create
************************************************
************************************************
creating build/temp.linux-x86_64-3.7/tmp
clang -pthread -Wno-unused-result -Wsign-compare -Wunreachable-code -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/tools/deps/include -I/tools/deps/include/ncurses -fPIC -c /tmp/timer_create4jgfmydq.c -o build/temp.linux-x86_64-3.7/tmp/timer_create4jgfmydq.o
unable to execute 'clang': No such file or directory
no timer_create, linking librt
Fatal: Cython-generated file 'zmq/backend/cython/_device.c' not found.
Cython >= 0.20 is required to compile pyzmq from a development branch.
Please install Cython or download a release package of pyzmq.

************************************************
thread 'main' panicked at 'error running setup.py', /home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/pyoxidizer-0.2.0/src/pyrepackager/packaging_rule.rs:1061:9
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

ii) also tried installing via source (pyoxidizer setup.py route)
https://github.com/zeromq/pyzmq/wiki/Building-and-Installing-PyZMQ
but wasn't successful

I am trying this on intel x86 with ubuntu.

Any solution/workaround much appreciated. Thanks

Reproduce the pyzmq packaging attempt on Ubuntu x86 using the shown pyoxidizer.toml setup-py-install rule and the setup.py route. Start by reading packaging_rule.rs around the reported error location and compare the native dependency and generated-file failures. Done means documenting or validating a working packaging path or a confirmed workaround.

Written by the indexing model from the issue text.