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

[Werner LEMBERG]

> I have no beef with deprecating it.

What about the following route?  For guile, I would add support for
`guile-config`, using the following algorithm (with item 1 already
implemented).

 1. Search for a guile `.pc` file, checking whether version 1.8.x,
    2.2.x, or 2.0.x is present (in this order).

    If a specific guile version is needed, set the `GUILE_FLAVOR`
    environment variable, for example

      ./configure GUILE_FLAVOR="guile-2.2"

    (possible values for `GUILE_FLAVOR` are `guile-1.8`, `guile-2.0`,
    `guile-2.2`, and `guile-3.0`).  If you want to use guile-3.0, you
    currently *must* use `GUILE_FLAVOR`.

 2. If nothing is found, try to execute `guile-config` (which must be
    in the path) to get the necessary compilation and linking flags.

 3. Abort if this fails, too.


    Werner