[v2,0/4] Avoid relying on autoconf internals in `preconfigure' scripts

Message ID alpine.DEB.2.20.2205122234010.10833@tpp.orcam.me.uk


Maciej W. Rozycki May 12, 2022, 10:28 p.m. UTC

 I have discovered that we have two kinds of `preconfigure' scripts, 
handwritten ones and autoconf-generated ones.  While it seems perfectly 
fine to have these scripts handwritten, some of them wire into autoconf 
internals or use an ad-hoc way to report errors.  The scripts for the 
C-SKY, m68k, MIPS and RISC-V targets fall into this category.

 This small patch series addresses this problem by converting these 
scripts to autoconf templates with suitable adjustments, then processed 
with autoconf to re-create functionally equivalent almost identical 

 The RISC-V script has been verified to still correctly build the library.  
All have been visually inspected to ensure functional equivalence; changes 
are so minimal for this to be straightforward.  There's some noise though 
from a formatting fix to replace octets of spaces with tabs in the new 

 OK to apply?