I've submitted PRs to resolve both build issues.  

Unfortunately, fixing that has uncovered a test failure in the newly-merged 
CacheShm code on the ppc64le architecture.  I've opened an issue (#13534) on 
this as I think it needs the original author's eyes.

--Jered


----- On Aug 11, 2026, at 8:22 AM, Jered Floyd [email protected] wrote:

> I have two build issues, both of which seem likely to be pretty trivial:
> 
> 
> 1) On Fedora 45, a libswoc test fails which seems to be due to a newly
> introduced error code message (glibc update?) conflicting with a hardcoded
> value in libswoc:
> 
> /builddir/build/BUILD/trafficserver-10.2.0-build/trafficserver-10.2.0/lib/swoc/unit_tests/test_bw_format.cc:529:
> FAILED:
>  REQUIRE( w.view().substr(0, 22) == "Unknown: Unknown error"sv )
> with expansion:
>  Unknown: Inappropriate
>  ==
>  "Unknown: Unknown error"
> 
> 
> 
> 2) On arch ppc64le, there is an invalid type coercion which does not occur on
> the 10.1.x branch.  This is related to #13230 which updated the upstream
> library to a newer codepoint:
> 
> /builddir/build/BUILD/trafficserver-10.2.0/lib/fastlz/fastlz.cc: In function
> ‘void flz_maxcopy(void*, const void*)’:
> /builddir/build/BUILD/trafficserver-10.2.0/lib/fastlz/fastlz.cc:178:17: error:
> invalid conversion from ‘void*’ to ‘uint8_t*’ {aka ‘unsigned char*’}
> [-fpermissive]
>  178 |   fastlz_memcpy(dest, src, MAX_COPY);
>      |                 ^~~~
>      |                 |
>      |                 void*
> /builddir/build/BUILD/trafficserver-10.2.0/lib/fastlz/fastlz.cc:94:36: note:
> initializing argument 1 of ‘void fastlz_memcpy(uint8_t*, const uint8_t*,
> uint32_t)’
>   94 | static void fastlz_memcpy(uint8_t* dest, const uint8_t* src, uint32_t
>   count) { memcpy(dest, src, count); }
>      |                           ~~~~~~~~~^~~~
> /builddir/build/BUILD/trafficserver-10.2.0/lib/fastlz/fastlz.cc:178:23: error:
> invalid conversion from ‘const void*’ to ‘const uint8_t*’ {aka ‘const unsigned
> char*’} [-fpermissive]
>  178 |   fastlz_memcpy(dest, src, MAX_COPY);
>      |                       ^~~
>      |                       |
>      |                       const void*
> /builddir/build/BUILD/trafficserver-10.2.0/lib/fastlz/fastlz.cc:94:57: note:
> initializing argument 2 of ‘void fastlz_memcpy(uint8_t*, const uint8_t*,
> uint32_t)’
>   94 | static void fastlz_memcpy(uint8_t* dest, const uint8_t* src, uint32_t
>   count) { memcpy(dest, src, count); }
>      |                                          ~~~~~~~~~~~~~~~^~~
> 
> 
> I'll look at these as I have time (which probably means one of you or
> Copilot/Claude will get to it first).
> 
> --Jered
> 
> ----- On Aug 10, 2026, at 4:18 PM, Chris McFarlen [email protected] wrote:
> 
>> I've prepared a release for 10.2.0.
>> 
>> ChangeLog:
>> 
>> https://github.com/apache/trafficserver/blob/10.2.x/CHANGELOG-10.2.0
>> 
>> The artifacts are available for download at:
>> 
>> https://dist.apache.org/repos/dist/dev/trafficserver/10.2.0
>> 
>> SHA512 checksum:
>> 
>> f952f98c74cdbb065640d6b3a3b8adf83f6afb19a1571f323742f286af4d200dd56303d87c56d34ab0b98631e0a3f50af151df8164f50ac9535a8ca6d4246f09
>> 
>> This corresponds to git refs:
>> 
>> Hash: 418a13d96b8c4b3c7444ceec482603b36a535cab
>> Tag: 10.2.0-rc0
>> 
>> Which can be verified with the following command:
>> 
>> $ git tag -v 10.2.0-rc0
>> 
>> All code signing keys are available here:
>> 
>> https://downloads.apache.org/trafficserver/KEYS
>> 
>> Make sure you refresh from a key server to get all relevant signatures
>> 
>> Please test and cast your votes as early as possible.
>> 
>> -Chris
>> 
> > Sent with [Proton Mail](https://proton.me/mail/home) secure email.

Reply via email to