[Top][All Lists]

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

Re: config.status has been broken by issue 5780 "Accept GUILE 2 without

From: David Kastrup
Subject: Re: config.status has been broken by issue 5780 "Accept GUILE 2 without extra configure options"
Date: Sat, 07 Mar 2020 08:54:59 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

David Kastrup <address@hidden> writes:

> If I previously did
> GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config ./configure
> ./config.status --recheck
> then the Guile configuration was reused.  If I now do
> PKG_CONFIG_PATH=/usr/local/tmp/guile-1.8/lib/pkgconfig ./configure
> ./config.status --recheck
> the configuration information is lost and configure reverts to the
> system configuration.
> In addition, PKG_CONFIG_PATH is not documented in our configuration or
> with ./configure --help.
> How to fix?
> A documented option --with-guile-prefix or --with-libguile-prefix that
> puts up a working configuration might be a reasonably transparent and
> future-safe option.
> Also now I don't think it made sense to _remove_ the GUILE_CONFIG
> variable: if it's set, it seems worth heeding.  If it's unset, going via
> pkgconfig may be the right way.  --with-libguile-prefix could pick the
> right option underneath, checking that it is viable, and prefer using

To put this into perspective: this definitely is a showstopper for
2.21.0.  A quick fix would be reverting the whole patch for issue 5780
in order to get back to a compatible state to what we had previously.  A
minimum fix would be recovering use of GUILE_CONFIG (when it is being
specified) in order to get back to the previous state of usability.
Given that I had several segfaults with GUILE-2.2 in recent days, I also
strongly lean towards continuing to require --enable-guile2 for getting
Guile2+.  We can reword the "highly experimental" bit.

At any rate, INSTALL.txt does not reflect _any_ of these changes.  It

   • Guile ( Use version
     1.8.8.  Version 2.x of Guile is not currently supported.

David Kastrup

reply via email to

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