Just to be clear: The backport is already in 1.6.x as

https://github.com/apache/apr-util/commit/e1bda0e77196de34ac08bdf446a6522a2f6c7ca7
or r1937013. It is not yet part of a released version of apr-util 1.6.x.

Regards

Rüdiger

On 10/1/26 6:48 PM, Jerry Martinez via dev wrote:
> Yes! Sorry for not being explicit in that regard.
> 
> *Jerry Martinez*
> Owner & Lead Developer
> 
> *JM Web Services, Inc*
> (786) 412-1660 | www.jmweb.net <https://www.jmweb.net/>
> 
> ----------------------------------------------------------------------------------------------------------------------------------
> *From:* Eric Covener <[email protected]>
> *Sent:* Thursday, October 1, 2026 12:45 PM
> *To:* [email protected] <[email protected]>
> *Cc:* Jerry Martinez <[email protected]>
> *Subject:* Re: Request to backport b19cf07e to apr-util 1.6.x
>  
> On Thu, Oct 1, 2026 at 12:35 PM Jerry Martinez via dev
> <[email protected]> wrote:
>>
>> Hello,
>>
>> Would it be possible to backport commit 
>> b19cf07e6474686fcff663e314ce4fa373299b0d to the apr-util 1.6.x branch?
>>
>> Starting with apr-util 1.6.4, my httpd build fails on an older GCC version 
>> at:
>>
>> crypto/apr_passwd.c:73:20: error: missing binary operator before token "("
>>  #if __has_attribute(always_inline)
>>
>> apr-util 1.6.3 builds successfully in the same environment.
>>
>> The change in b19cf07e appears to address this exact portability issue by 
>> providing the __has_attribute fallback unconditionally
> when it is not defined.
>>
>> Since 1.6.x is still the current release line, I wanted to ask whether this 
>> fix is appropriate for backporting rather than
> waiting for a future 1.7 release.
>>
> 
> Just to be clear, I guess you would also need a 1.6.x release?

Reply via email to