-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LNK1104 (caused by path length) when building on Windows #14
Comments
* https://github.com/pypa/setuptools/blob/v69.0.3/setuptools/_distutils/_msvccompiler.py#L491 * James-E-A/pypqc#14 * https://discuss.python.org/t/pip-install-working-on-sdist-but-not-from-pypi/44077 * https://developercommunity.visualstudio.com/t/clexe-compiler-driver-cannot-handle-long-file-path/975889
#14 https://discuss.python.org/t/pip-install-working-on-sdist-but-not-from-pypi/44077 https://developercommunity.visualstudio.com/t/clexe-compiler-driver-cannot-handle-long-file-path/975889 https://github.com/pypa/setuptools/blob/v69.0.3/setuptools/_distutils/_msvccompiler.py#L491 https://github.com/pypa/setuptools/blob/v69.0.3/setuptools/command/build_clib.py#L37
Problem is that MSVC doesn't support long filepaths. (Like, totally doesn't support them, even with a registry entry.)
|
Other than better error messages, there's basically nothing we can do about this. Gonna go ahead and close this issue as Unfixable on account of:
|
Technically, I guess we could fix this ourselves by rolling our own implementation of I'm not up for figuring out how to do that at the moment, though; just tracing the tangled mess of codepaths to diagnose the issue in the first place was a big enough task. (Open to PRs, just not planning to do it myself in the forseeable future.) |
Quick fix:
More information:
#issuecomment-1943083629
https://discuss.python.org/t/inconsistently-getting-error-1104-while-building-a-clib-cffi-extension-on-windows/44077/5
Original issue:
If I *manually download the sdist from pypy*, then run
pip install pypqc-0.0.6.post1.tar.gz
on the downloaded tarball itself, this error does not arise; for some reason beyond my comprehension, it only arises when you runpip install pypqc
💢The text was updated successfully, but these errors were encountered: