Summary:	ASTERISK-27585: [patch] BuildSystem: Resolve resolv.h not via Generic but Particular Header-Check.
Reporter:	Alexander Traud (traud)	Labels:	patch
Date Opened:	2018-01-15 10:44:38.000-0600	Date Closed:	2018-01-16 09:53:59.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Core/BuildSystem
Versions:	15.2.0	Frequency of Occurrence
Related Issues:
Environment:	OpenBSD 6.2	Attachments:	( 0) resolv_header.patch
Description:	[Gerrit 5375|http://gerrit.asterisk.org/5375] changed the script ./configure how to look for required headers. In that change, the generic AC_CHECK_HEADERS is used. Currently, ./configure checks each header in that list individually, and tries to compile it via a small app. If a header is incomplete, the test fails. Therefore, the whole ./configure fails. However in that list of headers, {{resolv.h}} needs prerequisites—another header—because it is incomplete. Currently OpenBSD (tested latest; 6.2) is affected by this. Tested myself and confirmed by <https://stackoverflow.com/q/35359456>. I reported that issue to OpenBSD. For Asterisk, the workaround is to go for [particular header checks|http://www.gnu.org/software/autoconf/manual/autoconf.html#Particular-Headers] which leverage the long-term knowledge of the GNU autoconf team. Because Gerrit 5375 has no issue report attached, I have to invite [~coreyfarrell] manually.
Comments:	By: Asterisk Team (asteriskteam) 2018-01-15 10:44:39.022-0600 The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process. By: Asterisk Team (asteriskteam) 2018-01-15 10:44:39.269-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Friendly Automation (friendly-automation) 2018-01-16 09:54:01.928-0600 Change 7963 merged by Jenkins2: BuildSystem: Resolve resolv.h not via Generic but Particular Header-Check. [https://gerrit.asterisk.org/7963|https://gerrit.asterisk.org/7963] By: Friendly Automation (friendly-automation) 2018-01-16 09:56:38.347-0600 Change 7964 merged by Jenkins2: BuildSystem: Resolve resolv.h not via Generic but Particular Header-Check. [https://gerrit.asterisk.org/7964|https://gerrit.asterisk.org/7964]