-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Curl tries to generate shell completions even when --without-*-functions-dir is given #13027
Comments
The --without-* flags still generate the completion files, but they're simply not installed in that case. curl is run using the normal libtool wrapper in src/curl so I don't know why it's not finding these libs. Are you able to run the test suite in this build configuration? Maybe it's broken all around. It's probably safest to simply skip altogether the completion generation script step if the scripts have been disabled instead. |
With the recent changes to completion file building, the files were built always and only installation was selectively disabled. Now, when they are disabled they aren't even built, avoiding a build-time error in environments where it's not possible to run the curl binary that was just created (e.g. if library paths were not set up correctly). Follow-up to 0f7aba8 Reported-by: av223119 on github Fixes #13027 Closes #13030
Thanks.
So it does work when deployed from the package built, and does not work when invoked from the build location. |
Build no longer seems to default to build shell completions but requires explicit --with-fish-functions-dir and --with-zsh-functions-dir configure options specified! |
The old code didn't build shell completions by default, either, at least with configure;make;make install. What were you running that caused them to be built? |
The previous maintainer started installing shell completions in 2016-01 curl 7.47.0 without any config changes: |
I did this
After the commit 89733e2, curl tries to generate completions even when --without-*-functions-dir. This is bad when curl is built against the libraries residing in non-standard places:
after the successful build, completion generation fails, as the linker couldn't find the libraries
I expected the following
No response
curl/libcurl version
Curl 8.6.0 - 89733e2
operating system
Ubuntu Linux
The text was updated successfully, but these errors were encountered: