-
Notifications
You must be signed in to change notification settings - Fork 504
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
Fix eCAP header includes #1753
Fix eCAP header includes #1753
Conversation
Squid style guidelines require .h files to be wrapped with HAVE_*_H protection. Add the missing ./configure header checks to generate the needed wrappers and refactor the include sequences to meet current guidelines.
/* libecap-1.0.1 headers do not build without autoconf.h magic */ | ||
#define HAVE_CONFIG_H |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
libecap apparently lacks basic self-consistency checks for its installed headers.
AC_CHECK_HEADERS
exposes
/usr/include/libecap/common/registry.h:15:75: error: 'LIBECAP_VERSION' was not declared in this scope
15 | extern bool RegisterVersionedService(adapter::Service *s, const char *v = LIBECAP_VERSION);
],,,[ | ||
/* libecap-1.0.1 headers do not build without autoconf.h magic */ | ||
#define HAVE_CONFIG_H | ||
/* libecap/common/delay.h fails to include <string> */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
libecap apparently lacks basic self-consistency checks for its installed headers.
AC_CHECK_HEADERS exposes a number of identical std::string
errors, one example:
/usr/include/libecap/common/delay.h:15:43: error: 'string' in namespace 'std' does not name a type
15 | explicit Delay(const std::string &state_):
| ^~~~~~
/usr/include/libecap/common/delay.h:7:1: note: 'std::string' is defined in header '<string>'; this is probably fixable by adding '#include <string>'
May I assume that after this PR, build issues are solved? |
Yes the commented lines are all that is necessary. These issues do no appear during the main build because we are an autoconf project and other files include |
What build issues? PR description does not mention any fixed build issues, and the PR has only one commit. What am I missing? |
The code comments documenting why the |
I was aware of those comments when I asked the question. I am interpreting your response as "The 'build issues' Francesco is talking about are not present in master/v7 code". Please correct me if I am wrong. |
Squid style guidelines require .h files to be wrapped with HAVE_*_H protection and placed after all Squid internal file includes. Add the missing ./configure header checks to generate the needed wrappers and refactor the include sequences to meet current guidelines.
Squid style guidelines require .h files to be wrapped with HAVE_*_H protection and placed after all Squid internal file includes. Add the missing ./configure header checks to generate the needed wrappers and refactor the include sequences to meet current guidelines.
Squid style guidelines require .h files to be wrapped with HAVE_*_H protection and placed after all Squid internal file includes. Add the missing ./configure header checks to generate the needed wrappers and refactor the include sequences to meet current guidelines.
Squid style guidelines require .h files to be wrapped with HAVE_*_H protection and placed after all Squid internal file includes. Add the missing ./configure header checks to generate the needed wrappers and refactor the include sequences to meet current guidelines.
Marking for merge under the 10+ day criteria. |
Squid style guidelines require .h files to be wrapped with HAVE_*_H protection and placed after all Squid internal file includes. Add the missing ./configure header checks to generate the needed wrappers and refactor the include sequences to meet current guidelines.
Squid style guidelines require .h files to be wrapped with HAVE_*_H protection and placed after all Squid internal file includes. Add the missing ./configure header checks to generate the needed wrappers and refactor the include sequences to meet current guidelines.
Squid style guidelines require .h files to be wrapped with HAVE_*_H protection and placed after all Squid internal file includes. Add the missing ./configure header checks to generate the needed wrappers and refactor the include sequences to meet current guidelines.
Squid style guidelines require .h files to be wrapped with HAVE_*_H protection and placed after all Squid internal file includes. Add the missing ./configure header checks to generate the needed wrappers and refactor the include sequences to meet current guidelines.
Squid style guidelines require .h files to be wrapped with
HAVE_*_H protection and placed after all Squid internal file
includes.
Add the missing ./configure header checks to generate the
needed wrappers and refactor the include sequences to meet
current guidelines.