glibc 中的预配置和配置有什么区别？
What is the difference between preconfigure and configure in glibc?
glibc源文件中相应的sysdeps/"architecture"目录下有preconfigure(.in)和configure(.in)脚本。
那么有谁知道他们的区别吗！？
preconfigure 文件被附加机制用来覆盖 configure 脚本使用的信息：
The real source code for any ports is found in the sysdeps/ subdirectories. These should be exactly what would go into the main libc source tree if you were to incorporate it directly. The only exceptions are the files sysdeps/*/preconfigure and sysdeps/*/preconfigure.in; these are fragments used by this add-on's configure fragment. The purpose of these is to set $base_machine et al when the main libc configure's defaults are not right for some machine. Everything else can and should be done from a normal sysdeps/.../configure fragment that is used only when the configuration selects that sysdeps subdirectory. Each port that requires some special treatment before the sysdeps directory list is calculated, should add a sysdeps/CPU/preconfigure file; this can either be written by hand or generated by Autoconf from sysdeps/CPU/preconfigure.in, and follow the rules for glibc add-on configure fragments. No preconfigure file should do anything on an unrelated configuration, so that disparate ports can be put into a single add-on without interfering with each other.
（来自 README 文件的旧版本。）
当 ports 子目录被删除后，对它的需求就消失了，今天几乎完全没有使用附加机制。
glibc源文件中相应的sysdeps/"architecture"目录下有preconfigure(.in)和configure(.in)脚本。 那么有谁知道他们的区别吗！？
preconfigure 文件被附加机制用来覆盖 configure 脚本使用的信息：
The real source code for any ports is found in the sysdeps/ subdirectories. These should be exactly what would go into the main libc source tree if you were to incorporate it directly. The only exceptions are the files sysdeps/*/preconfigure and sysdeps/*/preconfigure.in; these are fragments used by this add-on's configure fragment. The purpose of these is to set $base_machine et al when the main libc configure's defaults are not right for some machine. Everything else can and should be done from a normal sysdeps/.../configure fragment that is used only when the configuration selects that sysdeps subdirectory. Each port that requires some special treatment before the sysdeps directory list is calculated, should add a sysdeps/CPU/preconfigure file; this can either be written by hand or generated by Autoconf from sysdeps/CPU/preconfigure.in, and follow the rules for glibc add-on configure fragments. No preconfigure file should do anything on an unrelated configuration, so that disparate ports can be put into a single add-on without interfering with each other.
（来自 README 文件的旧版本。）
当 ports 子目录被删除后，对它的需求就消失了，今天几乎完全没有使用附加机制。