22 Jun
2024
22 Jun
'24
11:53 p.m.
On 6/21/24 5:04 PM, Alexis wrote:
Chet Ramey via TUHS <tuhs(a)tuhs.org> writes:
Sorry, i'm not sure i understand your question, particularly given that i
was writing about the situation where a fundamental part of the build
environment _hasn't_ changed .... Could you please elaborate or rephrase?
I think we're kind of saying the same thing. The autotools can't update
dependencies if something in the environment changes, regardless of whether
an OS update has occurred or not. That responsibility has to fall on the
admin or other tools.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet(a)case.edu http://tiswww.cwru.edu/~chet/
On 6/20/24 7:35 PM, Alexis 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.
configure and config.cache compute the results for a given build
environment. If you change that, whose responsibility is it to update
the
dependencies?