Open f3flight opened 2 years ago
Installing prophet from sdist bears the same result (as expected, because that also builds the wheel and installs it)
pip install prophet-1.1.1 --no-binary prophet
This command also builds the wheel under the hood, successfully, and installs it, but library is not functional.
Pre-built manylinux wheels published on pypi.org are functional.
The wheels built in this repo use cibuildwheel, which on Linux uses auditwheel repair
to de-locate the built wheel. This is necessary to update the library lookup path of the built model.
Can I ask why you are building your own wheels from the sdist? If your goal is to install the package from source, your best bet is to first install CmdStan on your machine and then set the environment variable PROPHET_REPACKAGE_CMDSTAN=false
Hi @WardBrian!
Can I ask why you are building your own wheels from the sdist?
Company security policy is to build artifacts from source whenever possible.
Thanks for the suggestion with CmdStan
, I cannot use this route in my environment unfortunately.
I understand that auditwheel
is used to create manylinux wheels, which is standard. However, auditwheel
is meant to unlink/copy system-specific libraries into the wheel, to make the wheel portable/usable on other systems. The wheel should be usable on the host where it was built out-of-the-box, without auditwheel
. The fact that it is not means that something in the build process is not set up correctly, and auditwheel repair
is just masking this problem, a workaround essentially.
Please can you help me understand this as well as give me a directive on how and where to start?
Hello all,
I've been testing prophet-1.1.1 while building from sdist, and I ran into a problem - the resulting wheel is not functional, as embedded libraries are not properly linked in the stan model blob:
Steps I use to reproduce this are: