On Wed, 19 Aug 2009, Peter Seebach wrote:It turns out to be worse than I thought! If we touch those files, theexisting configure scripts produce slightly different output, in particular,the libc.info files go in the wrong place.I am not aware of any problems if you touch the correct set of files. (In addition to configure scripts, files *-kw.h generated by gperf should be touched.) What is the "wrong place" here? Unlike FSF glibc, the EGLIBC configure scripts should currently (trunk) all be generated with the same autoconf version (2.63).
Interesting.What happens (and this is pretty far outside eglibc's territory) is that the libc.info and friends don't end up where we expect them, such that a later phase of our installation blows up because it can't find them.
So it appears that we've actually been unintentionally RELYING on the regeneration of the top-level configure file...
I'm gonna look into this more. I think mostly this is purely an artefact of our particular build system, but there might be an underlying issue.
-s -- Listen, get this. Nobody, with a good compiler, needs to be justified.