Re: g-wrap - fresh git clone - can't find libguile.h:

[Andreas Rottmann <a.rottmann@gmx.at>]

Andreas Rottmann <a.rottmann@gmx.at> writes:

> David Pirotte <david@altosw.be> writes:
>
>> Le Tue, 03 May 2011 12:43:07 +0200,
>> Andy Wingo <wingo@pobox.com> a écrit :
>>
>>> On Mon 02 May 2011 20:57, David Pirotte <david@altosw.be> writes:
>>> 
>>> > After having just installed a guile fresh git clone, g-wrap [fresh git clone
>>> > too] won't make.
>>> 
>>> What platform are you on?  GNU/Linux?  From which distributor?
>>> 
>>> Andy
>>
>> Hello Andy,
>>
>> 	x86_64 GNU/Linux
>> 	Debian testing/unstable
>> 
> Im on the same platform (current Debian sid, amd64) as well.  I just
> added a workaround for a (probably unrelated) issue in g-wrap.  Could you
> update your checkout, and try again?  Also make sure ACLOCAL_FLAGS is
> set in a way so that the matching guile.m4 gets picked up; if you have
> installed Guile into /usr/local, that would be:
>
> export ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
> ./autogen.sh && make
>
We have finally figured it out after some debugging via IRC:  David has
had set PKG_CONFIG=true when configuring Guile, which lead to an
installation with a (silently) broken guile-config script;
meta/guile-config.in contains:

(define %pkg-config-program "@PKG_CONFIG@")

The mayhem that resulted is left to the (hopefully vivid) imagination of
the reader ;-).

IMO, the following advice given in Guile's README is quite dangerous, as
can be seen from David's issue:

  - pkg-config

    Guile's ./configure script uses pkg-config to discover the correct
    compile and link options for libgc and libffi.  If you don't have
    pkg-config installed, or you have a version of libgc that doesn't
    provide a .pc file, you can work around this by setting some
    variables as part of the configure command-line:

    - PKG_CONFIG=true

    - BDW_GC_CFLAGS=<compile flags for picking up libgc headers>

    - BDW_GC_LIBS=<linker flags for picking up the libgc library>

    Note that because you're bypassing all pkg-config checks, you will
    also have to specify libffi flags as well:

    - LIBFFI_CFLAGS=<compile flags for picking up libffi headers>

    - LIBFFI_LIBS=<linker flags for picking up the libffi library>

Note the PKG_CONFIG=true setting.  This should at least come with a big
fat warning that the resulting installation of Guile will be broken
wrt. to building any software depending on Guile (unless the software in
question bypasses guile-config).  Alternatively, we could scrap that
section altogether and just say that pkg-config is required (which is in
fact true, with the current state of afairs).

Regards, Rotty
-- 
Andreas Rottmann -- <http://rotty.yi.org/>