-
Notifications
You must be signed in to change notification settings - Fork 578
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
Error building from source #1996
Comments
Support for globbing was added to setuptools in the same version of setuptools that is pinned as a build requirement in setup.cfg. You may need to update that first. According to https://repology.org/project/python:setuptools/versions the version of setuptools packaged in fedora 35 is too old. But, setuptools is supposed to inject newer versions of itself and run using that instead, just like it installs local versions of any other unsatisfied build requirement. Using python-build and
|
It does seem to be working now:
That version must be 57.5.0; not sure how to use 2712 =/. I probably had these issues without updated system versions because those commits were very new, although it does specify the requirement in the file, so not sure, but glad it's resolved now. |
Describe the bug
Error during building/compilation.
Expected behavior
Compiles successfully. Binary installed in system directories.
Actual behavior
Make error.
To Reproduce
https://guake.readthedocs.io/en/latest/user/installing.html#install-from-source
It says error is in
Makefile:93
, but better seems to be with 95 having the python setup, sincesetup.cfg:35
, under[options.data_files]
,share/guake/po
contains the stringpo/*.mo
that is probably causing the issue, since other Makefile lines usefind
in afor
loop that should avoid this error.https://setuptools.pypa.io/en/latest/deprecated/distutils/setupscript.html?highlight=data_files#installing-additional-files
I only found this relevant doc for that setuptools configuration key, recommending path relative syntax. The top of that document section under
2. Writing the Setup Script
mentions some formatting.I don't have a lot of experience with Python, especially with the packaging engine. Would a solution be to set this line to functional code instead of string literals, or did something not install correctly in my system?
Found a different error, but may help explain why there is an error in the setuptools config file, since it was recently created.
The text was updated successfully, but these errors were encountered: