jerpelea opened a new pull request, #3775:
URL: https://github.com/apache/nuttx-apps/pull/3775

   ## Summary
   
   The bundled encoder was checked out from lame's trunk with no revision, so 
every build took whatever trunk happened to be at that moment.  lame's trunk 
grows vector tiers over time, and each one adds sources that the two build 
files have to name:  r6655 offered AVX2 to the vector routines on 2026-07-25, 
and r6718 and r6720 added an AVX-512 tier on 2026-07-30.  The AVX-512 sources 
were never listed, so sim:alsa stopped linking on x86 hosts:
   
     takehiro.c:332:    undefined reference to `quantize_lines_xrpow_avx512'
     takehiro.c:533:    undefined reference to `ix_max_avx512'
     takehiro.c:569:    undefined reference to `count_bit_esc_avx512'
     vbrquantize.c:261: undefined reference to `calc_sfb_noise_x34_avx512'
   
   Pin the checkout to r6720 through a LAME_VERSION variable, as the rest of 
apps/ pins its third-party sources, and list the three AVX-512 files that 
revision provides.  The pin is what keeps the two in step:  the source list is 
maintained by hand, so it can only be correct for a known revision.
   
   The checkout is also only performed when lame/configure is absent and is 
never updated afterwards, so before this an unpinned tree was frozen at 
whatever trunk was on the day it was first built.  Anyone who checked out 
before 2026-07-30 still links and cannot reproduce the failure, which is why 
this surfaced only in CI.
   
   Makefile named just vector/xmm_quantize_sub.c and none of the other vector 
sources, so a Make build on an x86 host fails the same way with a longer list 
of symbols, from SSE2 upwards.  CI builds sim:alsa through CMake only, so that 
half was latent rather than visible.  Both files now list the same nine sources 
under the same host condition.
   
   ## Impact
   
   RELEASE
   
   ## Testing
   
   CI


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to