-
Notifications
You must be signed in to change notification settings - Fork 6.4k
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
[readline-unix] no absolute paths #22421
[readline-unix] no absolute paths #22421
Conversation
Yeah, and before this one, readline-osx was rushed in with a custom build system, instead of simply using the original build system... |
From INSTALL:
Seems that readline-unix should depend on libtermcap or curses |
Yes. It depends on system curses on osx and linux. |
Hm but the |
Upstream bug? |
Looks like below codes not working correctly, causing the default lib: ltermcap is used instead of lcurses.
|
@autoantwort Could you please help solve this issue? |
I also have read through the configure files and do not really understand why libcurses is not selected, but I don't want to debug it :D |
vcpkg_configure_make( Should be: vcpkg_configure_make( |
After modified the OPTIONS keyword, --with-curses option could be passed successfully, but the installation still failed with following error:
|
That should be an error. At least a warning. |
e4ffb4e
to
e1a258a
Compare
Yes, we will improve the check function for these keywords later. |
Is btw ready |
Thanks! |
For #20469
This port is 4 days old