-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
Configure UX #115806
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
Comments
- make sure LDLIBRARY and HOSTRUNNER checks don't overlap - make the ipv6 library check less subtle
Ah, our PR gh-116016 mangled the output again: checking ipv6 stack type... checking for IPV6_INRIA_VERSION defined in netinet/in.h... no
checking for __KAME__ defined in netinet/in.h... yes
kame With #116165 applied, we get this: checking for IPV6_INRIA_VERSION defined in netinet/in.h... no
checking for __KAME__ defined in netinet/in.h... yes
checking ipv6 stack type... kame
checking ipv6 library... libc |
- make sure LDLIBRARY and HOSTRUNNER checks don't overlap - make the ipv6 library check less subtle
|
- make sure LDLIBRARY and HOSTRUNNER checks don't overlap - make the ipv6 library check less subtle
Triage: the linked PRs are merged, can this be closed? |
- make sure LDLIBRARY and HOSTRUNNER checks don't overlap - make the ipv6 library check less subtle
I'll close it now. If there are more improvements to do, please re-open or open a new issue. Thank you for the improvements! |
#115806 (comment) is still not fixed. The problem is that we're using Lines 4431 to 4454 in 8e57877
I wonder if we're better off by using |
Replace AC_CACHE_VAL/AC_CHECK_HEADER with a cleaner variant using AC_CACHE_CHECK/AC_PREPROC_IFELSE. The former would produce garbled output when config.cache was reused. It also required directly manipulating GNU Autoconf cache variables.
Feature or enhancement
The LDLIBRARY and HOSTRUNNER checks overlap; this results in garbled output:
The IPv6 library check is very subtle:
Suggesting to clean this up, for improved
configure
user experience:Linked PRs
The text was updated successfully, but these errors were encountered: