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

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

[David Pirotte]

Hello,

After having just installed a guile fresh git clone, g-wrap [fresh git clone
too] won't make.

Any idea?
Cheers,
David

;; --

	uname -r:	2.6.38-2-amd64
	guile:		guile (GNU Guile) 2.0.1.17-f3c6

	'Related' variables defined:

		LD_LIBRARY_PATH=/usr/local/lib

	%load-path
	$1 = ("/usr/local/share/guile/2.0" "/usr/local/share/guile/site/2.0"
	"/usr/local/share/guile/site" "/usr/local/share/guile")

[getting a fresh git clone of g-wrap]
./autogen.sh --prefix=/usr/local
make
... ...
make[4]: Entering directory `/usr/local/src/g-wrap/git-clone/guile/g-wrap'
/bin/bash ../../libtool --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I../..
-I../../g-wrap  -I../.. -I../../lib -I../../guile    -g -O2 -Wall
-Wmissing-prototypes -Werror -std=gnu99 -MT guile-runtime.lo -MD -MP
-MF .deps/guile-runtime.Tpo -c -o guile-runtime.lo guile-runtime.c libtool:
compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -I../../g-wrap -I../.. -I../../lib
-I../../guile -g -O2 -Wall -Wmissing-prototypes -Werror -std=gnu99 -MT
guile-runtime.lo -MD -MP -MF .deps/guile-runtime.Tpo -c guile-runtime.c  -fPIC -DPIC
-o .libs/guile-runtime.o In file included from
guile-runtime.c:32:0: ../../guile/g-wrap/guile-compatibility.h:25:22: fatal error:
libguile.h: No such file or directory compilation terminated. make[4]: ***
[guile-runtime.lo] Error 1 make[4]: Leaving directory
`/usr/local/src/g-wrap/git-clone/guile/g-wrap' make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/usr/local/src/g-wrap/git-clone/guile/g-wrap' make[2]:
*** [all-recursive] Error 1 make[2]: Leaving directory
`/usr/local/src/g-wrap/git-clone/guile' make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/g-wrap/git-clone' make: *** [all] Error 2
david@idefix:/usr/local/src/g-wrap/git-clone 10 $ 

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

[Andy Wingo]

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
-- 
http://wingolog.org/

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

[David Pirotte]

[-- Attachment #1: Type: text/plain, Size: 420 bytes --]

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
	
Thanks,
David

[-- Attachment #2: config.log.gz --]
[-- Type: application/x-gzip, Size: 10200 bytes --]

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

[Andreas Rottmann]

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

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

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

[Andreas Rottmann]

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

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

[Mike Gran]

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

IIRC, the PKG_CONFIG=true hack was because of a bug in pkg.m4 that wouldn't let
you bypass pkg-config using the XXX_CFLAGS and XXX_LIBS if you didn't have
pkg-config installed.  Newer versions of pkg.m4 have fixed this.
 
-Mike