On Jun 20, 2024, at 4:35 PM, Alexis
<flexibeast(a)gmail.com> wrote:
If i compile something on one of my OpenBSD boxen in the morning, and then compile some
other thing in the afternoon, without an OS upgrade in-between, autoconf isn't going
to find that libc.so has changed in-between. If i did the same thing on my Gentoo box,
it's theoretically possible that e.g. i've moved from glibc to musl in-between,
but in that case, precomputation could be done in postinst (i.e. as part of the
post-installation-of-musl process).
But the overlap between two different programs or their assumptions will be
only partial (except for some very basic things) which likely means the cache
won't quite work. For example, you may find that program A and B depend on different
versions of some library C. And how does the configure or whatever
tool find out that no dependency has changed? I don't think you can factor
out a cache of such data to a global place that will work for every ported
program.