[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: possible configure bug

From: Aidan Gauland
Subject: Re: possible configure bug
Date: Mon, 24 Jun 2013 08:29:39 +1200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

address@hidden (Ludovic Courtès) writes:

> 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.

It got stuck on libunistring.

The previous missing dependencies that it *did* detect after I installed
them were libffi, libgc (the Debian package name for bdw-gc), and
libgmp (in that order).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]