Re: GUILE_CONFIG

[Jonas Hahnfeld]

Am Dienstag, dem 08.06.2021 um 11:08 +0200 schrieb David Kastrup:
> Jonas Hahnfeld <hahnjo@hahnjo.de> writes:
> 
> > Am Montag, dem 07.06.2021 um 16:03 +0200 schrieb David Kastrup:
> > 
> > > The options correspond in non-obvious ways to calls of guile-config, and
> > > there is no obvious or documented way to adjust pkgconfig paths in a
> > > manner where it would detect a local guile installation without breaking
> > > all other package configuration on the way.
> > 
> > From ./configure --help:
> >   GUILE_FLAVOR
> >               pkgconfig name for Guile, like guile-1.8 or guile-2.2 . If the
> >               respective .pc file cannot be found by pkgconfig, add its path
> >               to PKG_CONFIG_PATH
> >   PKG_CONFIG  path to pkg-config utility
> >   PKG_CONFIG_PATH
> >               directories to add to pkg-config's search path
> >   PKG_CONFIG_LIBDIR
> >               path overriding pkg-config's built-in search path
> > 
> > That's as obvious as it can get, and any search on the internet should
> > have pointed you to these variables. (GUILE_FLAVOR defaults to guile-
> > 1.8 so you don't need to specify it; I'm just including its output
> > above to show that it already points to PKG_CONFIG_PATH)
> 
> You did get the part about "where it would detect a local guile
> installation without breaking all other package configuration on the way"?

PKG_CONFIG_PATH *adds* to the path (while _LIBDIR overrides), so if you
set PKG_CONFIG_PATH=/usr/local/tmp/guile-1.8/lib/pkgconfig/ how does
this break other package configuration?

Jonas

signature.asc
Description: This is a digitally signed message part