Re: possible configure bug

[Daniel Hartwig]

On 23 June 2013 21:47, Ludovic Courtès <address@hidden> wrote:
> Aidan Gauland <address@hidden> skribis:
>
>> I'm not sure whether this is a bug, but it's inconsistent behaviour.  I
>> ran (in the guile-2.0.9 directory)
>>
>>  $ ./configure -C
>>
>> and got an error about a missing dependency, which I installed, and then
>> and re-ran "./configure -C", which detected the newly installed
>> dependency and reported a *different* missing dependency.  I repeated
>> this a few times until it got to unistring, which it did not detect
>> after I installed it until I re-ran ./configure *without* -C.
>
> Which dependency exactly?
>
> Normally info related to dependencies whose unavailability leads to an
> error (such as libunistring and bdw-gc) is *not* cached.
>

Perhaps, though in general if anything has changed in the dependencies
I would not be using ‘-C’ for cached responses.  Run all tests fresh
as there can be effects from inter-related dependencies that change.